palbase 0.41.3 → 0.42.0

package/types/internal/src/modules/machines.d.ts

@@ -160,9 +160,9 @@ export type Machine = {
      */
     running_version: number;
     /**
-     * The machine's size. shared-256 has a fraction of a CPU as its ceiling and is put to sleep when it is idle; a standard size never sleeps — its CPUs are its ceiling, a quarter of them reserved for it, the rest its node's when the other machines there leave them; a dedicated size has whole CPUs of its own and never sleeps. shared-256: 0.2 vCPU, 256 MiB (free); starter: 0.5 vCPU, 512 MiB; standard-1x: 1 vCPU, 2048 MiB; standard-2x: 2 vCPU, 4096 MiB; standard-4x: 4 vCPU, 8192 MiB; dedicated-1x: 1 vCPU of its own, 2048 MiB; dedicated-2x: 2 vCPU of its own, 4096 MiB. GET /machines/sizes lists each with its price. shared-512 and shared-1024 are retired: a machine that has one keeps it until it is moved to another size; none is opened at or moved to one.
+     * The machine's size. shared-256 has a fraction of a CPU as its ceiling and is put to sleep when it is idle; a standard size never sleeps — its CPUs are its ceiling, a quarter of them reserved for it, the rest its node's when the other machines there leave them; a dedicated size has whole CPUs of its own and never sleeps. shared-256: 0.2 vCPU, 256 MiB (free); starter: 0.5 vCPU, 512 MiB; standard-1x: 1 vCPU, 2048 MiB; standard-2x: 2 vCPU, 4096 MiB; standard-4x: 4 vCPU, 8192 MiB; standard-8x: 8 vCPU, 16384 MiB; highmem-4x: 4 vCPU, 16384 MiB; highmem-8x: 8 vCPU, 32768 MiB; dedicated-1x: 1 vCPU of its own, 2048 MiB; dedicated-2x: 2 vCPU of its own, 4096 MiB. GET /machines/sizes lists each with its price. shared-512 and shared-1024 are retired: a machine that has one keeps it until it is moved to another size; none is opened at or moved to one.
      */
-    size: "dedicated-1x" | "dedicated-2x" | "shared-1024" | "shared-256" | "shared-512" | "standard-1x" | "standard-2x" | "standard-4x" | "starter";
+    size: "dedicated-1x" | "dedicated-2x" | "highmem-4x" | "highmem-8x" | "shared-1024" | "shared-256" | "shared-512" | "standard-1x" | "standard-2x" | "standard-4x" | "standard-8x" | "starter";
     /**
      * building: no build of it runs yet (its first is on its way — waiting for its commit's checks too — or failed: `state_reason`); starting: on its way up; awake: answering; asleep: idle, and woken by the next request to its address; failed: it cannot start, or its first build failed or was skipped (`state_reason` says why).
      */
@@ -172,9 +172,9 @@ export type Machine = {
      */
     state_reason?: string;
     /**
-     * What kind of thing `state_reason` says: waiting — the version asked for waits before it takes traffic (on its commit's checks, its configuration, its tests, its contract, its database or its migration) and rolls out once that is done; not_up — it does not start or answer, or a copy of the one before it stays; given_up — it did not come up, and the one before it serves until the machine's next change; migration — its database migration failed (to start, and the version does not roll out; or to close); stopped — it was put to sleep for a reason; failed — it cannot run. Absent with no `state_reason`.
+     * What kind of thing `state_reason` says: waiting — the version asked for waits before it takes traffic (on its commit's checks, its configuration, its tests, its contract, its database or its migration) and rolls out once that is done; not_up — it does not start or answer, or a copy of the one before it stays; given_up — it did not come up, and the one before it serves until the machine's next change; migration — its database migration failed (to start, and the version does not roll out; or to close); stopped — it was put to sleep for a reason; failed — it cannot run; no_room — copies of it wait for room in the cluster: a node is being brought up (a few minutes), and the platform's operators are told if none can be. Absent with no `state_reason`.
      */
-    state_reason_kind?: "failed" | "given_up" | "migration" | "not_up" | "stopped" | "waiting";
+    state_reason_kind?: "failed" | "given_up" | "migration" | "no_room" | "not_up" | "stopped" | "waiting";
     updated_at: string;
     /**
      * Where the machine answers: the project's own address for `backend`, <name>-<ref> under the app domain for any other.
@@ -206,7 +206,7 @@ export type Machine = {
      */
     health_path?: string;
     /**
-     * How many copies of the machine run while it is awake, each on a node of its own: a request is sent to one of them, a copy or a node that goes leaves the others serving, and the cluster takes one of them away at a time at most. Every copy is of the machine's size and counts as such against the project's limits and its machine time (a minute in which the number changed is counted at the most it was). What a copy keeps in its own memory or on its own disk the others do not see — a session, a counter, a cache, a timer: a machine with more than one keeps those where every copy reaches them. The machine finds the number in PALBASE_REPLICAS. A long-lived connection (a WebSocket) stays with the copy that took it.
+     * How many copies of the machine run while it is awake, up to 100 (one on Free), over two nodes at least and no node holding more than half of them: a request is sent to one of them, a copy or a node that goes leaves the others serving, and the cluster takes one of them away at a time at most. Every copy is of the machine's size and counts as such against the project's limits and its machine time (a minute in which the number changed is counted at the most it was). What a copy keeps in its own memory or on its own disk the others do not see — a session, a counter, a cache, a timer: a machine with more than one keeps those where every copy reaches them. The machine finds the number in PALBASE_REPLICAS. A long-lived connection (a WebSocket) stays with the copy that took it.
      */
     replicas: number;
     /**
@@ -287,9 +287,9 @@ export type MachineCreate = {
      */
     port?: number;
     /**
-     * The machine's size. shared-256 has a fraction of a CPU as its ceiling and is put to sleep when it is idle; a standard size never sleeps — its CPUs are its ceiling, a quarter of them reserved for it, the rest its node's when the other machines there leave them; a dedicated size has whole CPUs of its own and never sleeps. shared-256: 0.2 vCPU, 256 MiB (free); starter: 0.5 vCPU, 512 MiB; standard-1x: 1 vCPU, 2048 MiB; standard-2x: 2 vCPU, 4096 MiB; standard-4x: 4 vCPU, 8192 MiB; dedicated-1x: 1 vCPU of its own, 2048 MiB; dedicated-2x: 2 vCPU of its own, 4096 MiB. GET /machines/sizes lists each with its price.
+     * The machine's size. shared-256 has a fraction of a CPU as its ceiling and is put to sleep when it is idle; a standard size never sleeps — its CPUs are its ceiling, a quarter of them reserved for it, the rest its node's when the other machines there leave them; a dedicated size has whole CPUs of its own and never sleeps. shared-256: 0.2 vCPU, 256 MiB (free); starter: 0.5 vCPU, 512 MiB; standard-1x: 1 vCPU, 2048 MiB; standard-2x: 2 vCPU, 4096 MiB; standard-4x: 4 vCPU, 8192 MiB; standard-8x: 8 vCPU, 16384 MiB; highmem-4x: 4 vCPU, 16384 MiB; highmem-8x: 8 vCPU, 32768 MiB; dedicated-1x: 1 vCPU of its own, 2048 MiB; dedicated-2x: 2 vCPU of its own, 4096 MiB. GET /machines/sizes lists each with its price.
      */
-    size: "dedicated-1x" | "dedicated-2x" | "shared-256" | "standard-1x" | "standard-2x" | "standard-4x" | "starter";
+    size: "dedicated-1x" | "dedicated-2x" | "highmem-4x" | "highmem-8x" | "shared-256" | "standard-1x" | "standard-2x" | "standard-4x" | "standard-8x" | "starter";
     /**
      * What the machine is started with in its environment, besides what the platform sets: PORT (where it listens), PALBASE_URL (its project's address, https://<ref>.<domain>), PALBASE_PROJECT_ID, PALBASE_REPLICAS (how many copies of it run) and, given a database, PALBASE_DB_URL and PALBASE_DB_CONNECTIONS (how many connections to it a copy may hold). PORT is refused here; the others, given here or among the machine's secrets, give way to the platform's. Names are environment variable names; 100 variables and 64 KiB at most. Keep secrets in the project's secrets and start the machine with them (`secrets`).
      */
@@ -306,7 +306,7 @@ export type MachineCreate = {
      */
     health_path?: string;
     /**
-     * How many copies of the machine run while it is awake, each on a node of its own: a request is sent to one of them, a copy or a node that goes leaves the others serving, and the cluster takes one of them away at a time at most. Every copy is of the machine's size and counts as such against the project's limits and its machine time (a minute in which the number changed is counted at the most it was). What a copy keeps in its own memory or on its own disk the others do not see — a session, a counter, a cache, a timer: a machine with more than one keeps those where every copy reaches them. The machine finds the number in PALBASE_REPLICAS. A long-lived connection (a WebSocket) stays with the copy that took it. One when left out.
+     * How many copies of the machine run while it is awake, up to 100 (one on Free), over two nodes at least and no node holding more than half of them: a request is sent to one of them, a copy or a node that goes leaves the others serving, and the cluster takes one of them away at a time at most. Every copy is of the machine's size and counts as such against the project's limits and its machine time (a minute in which the number changed is counted at the most it was). What a copy keeps in its own memory or on its own disk the others do not see — a session, a counter, a cache, a timer: a machine with more than one keeps those where every copy reaches them. The machine finds the number in PALBASE_REPLICAS. A long-lived connection (a WebSocket) stays with the copy that took it. One when left out.
      */
     replicas?: number;
     /**
@@ -384,9 +384,9 @@ export type MachineUpdate = {
      */
     port?: number;
     /**
-     * The machine's size. shared-256 has a fraction of a CPU as its ceiling and is put to sleep when it is idle; a standard size never sleeps — its CPUs are its ceiling, a quarter of them reserved for it, the rest its node's when the other machines there leave them; a dedicated size has whole CPUs of its own and never sleeps. shared-256: 0.2 vCPU, 256 MiB (free); starter: 0.5 vCPU, 512 MiB; standard-1x: 1 vCPU, 2048 MiB; standard-2x: 2 vCPU, 4096 MiB; standard-4x: 4 vCPU, 8192 MiB; dedicated-1x: 1 vCPU of its own, 2048 MiB; dedicated-2x: 2 vCPU of its own, 4096 MiB. GET /machines/sizes lists each with its price.
+     * The machine's size. shared-256 has a fraction of a CPU as its ceiling and is put to sleep when it is idle; a standard size never sleeps — its CPUs are its ceiling, a quarter of them reserved for it, the rest its node's when the other machines there leave them; a dedicated size has whole CPUs of its own and never sleeps. shared-256: 0.2 vCPU, 256 MiB (free); starter: 0.5 vCPU, 512 MiB; standard-1x: 1 vCPU, 2048 MiB; standard-2x: 2 vCPU, 4096 MiB; standard-4x: 4 vCPU, 8192 MiB; standard-8x: 8 vCPU, 16384 MiB; highmem-4x: 4 vCPU, 16384 MiB; highmem-8x: 8 vCPU, 32768 MiB; dedicated-1x: 1 vCPU of its own, 2048 MiB; dedicated-2x: 2 vCPU of its own, 4096 MiB. GET /machines/sizes lists each with its price.
      */
-    size?: "dedicated-1x" | "dedicated-2x" | "shared-256" | "standard-1x" | "standard-2x" | "standard-4x" | "starter";
+    size?: "dedicated-1x" | "dedicated-2x" | "highmem-4x" | "highmem-8x" | "shared-256" | "standard-1x" | "standard-2x" | "standard-4x" | "standard-8x" | "starter";
     /**
      * Replaces the machine's environment whole, besides PORT. Names are environment variable names; 100 variables and 64 KiB at most. Keep secrets in the project's secrets and start the machine with them (`secrets`).
      */
@@ -511,9 +511,9 @@ export type Database = {
      */
     pooled_port: number;
     /**
-     * The database's size. free: 0.25 vCPU, 512 MiB, 1 GB, put to sleep when idle (woken by the next connection in about 10 s), awake 400 hours a month at most, archived after a week asleep (its next connection brings it back from its backup); hobby: 0.25 vCPU, 512 MiB, 5 GB, put to sleep when idle, no monthly limit; starter: 1 GiB, up to 0.5 vCPU, 10 GB; standard-1x: 2 GiB, up to 1 vCPU, 25 GB; standard-2x: 4 GiB, up to 2 vCPU, 50 GB (a quarter of their CPU reserved for them); dedicated-1x: 1 vCPU of its own, 4 GiB, 25 GB; dedicated-2x: 2 vCPU of its own, 8 GiB, 50 GB. The standard and dedicated sizes never sleep and live on a Premium SSD v2 disk of their own; free and hobby on the platform's SAN. A database past its size's storage turns read-only. What a project's machines and databases reserve between them is held to its limit: a size that does not fit is refused (409 `machines_over_limit`). preview: a machine's pull request preview's own database — 0.25 vCPU, 512 MiB, 500 MB, put to sleep when idle — opened with its preview and deleted with it; no database is opened at or moved to it. shared-1g, shared-2g and shared-4g are retired: a database that has one keeps it until it moves to another size; none is opened at or moved to one.
+     * The database's size. free: 0.25 vCPU, 512 MiB, 1 GB, put to sleep when idle (woken by the next connection in about 10 s), awake 400 hours a month at most, archived after a week asleep (its next connection brings it back from its backup); hobby: 0.25 vCPU, 512 MiB, 5 GB, put to sleep when idle, no monthly limit; starter: 1 GiB, up to 0.5 vCPU, 10 GB; standard-1x: 2 GiB, up to 1 vCPU, 25 GB; standard-2x: 4 GiB, up to 2 vCPU, 50 GB; standard-4x: 16 GiB, up to 4 vCPU; standard-8x: 32 GiB, up to 8 vCPU; standard-16x: 64 GiB, up to 16 vCPU; standard-32x: 128 GiB, up to 32 vCPU, 100 GB each (a quarter of their CPU reserved for them); dedicated-1x: 1 vCPU of its own, 4 GiB, 25 GB; dedicated-2x: 2 vCPU of its own, 8 GiB, 50 GB. The standard and dedicated sizes never sleep and live on a Premium SSD v2 disk of their own; free and hobby on the platform's SAN. The GB of a size that never sleeps are its storage unless `storage_gb` says otherwise (1 or a multiple of 5, up to 4,000), billed by the GB past its first; its size's hours are its CPU and memory. A database past its storage turns read-only — or, `storage_autoscaling` on, grows by half when 90% full. What a project's machines and databases reserve between them is held to its limit: a size that does not fit is refused (409 `machines_over_limit`). preview: a machine's pull request preview's own database — 0.25 vCPU, 512 MiB, 500 MB, put to sleep when idle — opened with its preview and deleted with it; no database is opened at or moved to it. shared-1g, shared-2g and shared-4g are retired: a database that has one keeps it until it moves to another size; none is opened at or moved to one.
      */
-    size: "dedicated-1x" | "dedicated-2x" | "free" | "hobby" | "preview" | "shared-1g" | "shared-2g" | "shared-4g" | "standard-1x" | "standard-2x" | "starter";
+    size: "dedicated-1x" | "dedicated-2x" | "free" | "hobby" | "preview" | "shared-1g" | "shared-2g" | "shared-4g" | "standard-16x" | "standard-1x" | "standard-2x" | "standard-32x" | "standard-4x" | "standard-8x" | "starter";
     /**
      * Where its data lives, as its size says: san, the platform's SAN; premium, a Premium SSD v2 disk of its own.
      */
@@ -534,6 +534,10 @@ export type Database = {
      * Why it is in its state, when that needs saying.
      */
     state_reason?: string;
+    /**
+     * What `state_reason` says, when a client tells it from the words: no_room — it waits for room in the cluster: a node is being brought up for it (a few minutes), and the platform's operators are told if none can be. Absent otherwise.
+     */
+    state_reason_kind?: "no_room";
     /**
      * When it was deleted; it may be taken back until `purge_after`.
      */
@@ -561,13 +565,21 @@ export type Database = {
      */
     used_bytes?: number;
     /**
-     * The most its size holds. Past it, it is read-only.
+     * The most it holds — its size's, or its storage (`storage_gb`). Past it, it is read-only.
      */
     quota_bytes: number;
     /**
      * It holds its quota: a transaction takes no writes unless it asks to — BEGIN READ WRITE, to make room with DROP, TRUNCATE, or DELETE and then VACUUM FULL (a DELETE alone frees no room) — and it reads on. Once it holds less than 95% of its quota it takes writes again, within a minute.
      */
     read_only: boolean;
+    /**
+     * What a database of a size on a disk of its own holds, in GB — its `quota_bytes` — as said when it was opened or grown (`DatabaseUpdate.storage_gb`), or its size's. It grows, never shrinks. Absent for a size on the platform's SAN (free, hobby), which holds its size's.
+     */
+    storage_gb?: number;
+    /**
+     * Whether it grows by itself: 90% full, its storage grows by half, up to the next multiple of 5 GB (10 to 15, 25 to 40), six hours at least after it last grew, to 4,000 GB. Off, a database past its storage turns read-only, and its organization's owners are told at 90% and when it is full. Absent for a size on the platform's SAN.
+     */
+    storage_autoscaling?: boolean;
     /**
      * A change of its passwords (POST …/password) has not reached the database yet: the new password works once this is false, a few seconds after. A client that hands the new password on waits for it.
      */
@@ -610,9 +622,9 @@ export type DatabaseCreate = {
      */
     name?: string;
     /**
-     * The database's size; `free` when left out. free: 0.25 vCPU, 512 MiB, 1 GB, put to sleep when idle (woken by the next connection in about 10 s), awake 400 hours a month at most, archived after a week asleep (its next connection brings it back from its backup); hobby: 0.25 vCPU, 512 MiB, 5 GB, put to sleep when idle, no monthly limit; starter: 1 GiB, up to 0.5 vCPU, 10 GB; standard-1x: 2 GiB, up to 1 vCPU, 25 GB; standard-2x: 4 GiB, up to 2 vCPU, 50 GB (a quarter of their CPU reserved for them); dedicated-1x: 1 vCPU of its own, 4 GiB, 25 GB; dedicated-2x: 2 vCPU of its own, 8 GiB, 50 GB. The standard and dedicated sizes never sleep and live on a Premium SSD v2 disk of their own; free and hobby on the platform's SAN. A database past its size's storage turns read-only. What a project's machines and databases reserve between them is held to its limit: a size that does not fit is refused (409 `machines_over_limit`).
+     * The database's size; `free` when left out. free: 0.25 vCPU, 512 MiB, 1 GB, put to sleep when idle (woken by the next connection in about 10 s), awake 400 hours a month at most, archived after a week asleep (its next connection brings it back from its backup); hobby: 0.25 vCPU, 512 MiB, 5 GB, put to sleep when idle, no monthly limit; starter: 1 GiB, up to 0.5 vCPU, 10 GB; standard-1x: 2 GiB, up to 1 vCPU, 25 GB; standard-2x: 4 GiB, up to 2 vCPU, 50 GB; standard-4x: 16 GiB, up to 4 vCPU; standard-8x: 32 GiB, up to 8 vCPU; standard-16x: 64 GiB, up to 16 vCPU; standard-32x: 128 GiB, up to 32 vCPU, 100 GB each (a quarter of their CPU reserved for them); dedicated-1x: 1 vCPU of its own, 4 GiB, 25 GB; dedicated-2x: 2 vCPU of its own, 8 GiB, 50 GB. The standard and dedicated sizes never sleep and live on a Premium SSD v2 disk of their own; free and hobby on the platform's SAN. The GB of a size that never sleeps are its storage unless `storage_gb` says otherwise (1 or a multiple of 5, up to 4,000), billed by the GB past its first; its size's hours are its CPU and memory. A database past its storage turns read-only — or, `storage_autoscaling` on, grows by half when 90% full. What a project's machines and databases reserve between them is held to its limit: a size that does not fit is refused (409 `machines_over_limit`).
      */
-    size?: "dedicated-1x" | "dedicated-2x" | "free" | "hobby" | "standard-1x" | "standard-2x" | "starter";
+    size?: "dedicated-1x" | "dedicated-2x" | "free" | "hobby" | "standard-16x" | "standard-1x" | "standard-2x" | "standard-32x" | "standard-4x" | "standard-8x" | "starter";
     /**
      * Who may connect, as addresses or CIDRs (203.0.113.7, 203.0.113.0/24), 50 at most; anyone with the password when empty.
      */
@@ -625,6 +637,14 @@ export type DatabaseCreate = {
      * The ref of the environment called, when given: a new database is bound to the environment whose address it is made at (409 bound_to_environment for another — make it at that environment's address). Its name is the project's one: name_taken when another environment holds a database of that name.
      */
     environment?: string;
+    /**
+     * What it holds, in GB: 1 or a multiple of 5, up to 4,000 — of a size on a disk of its own (400 `storage_not_adjustable` for free and hobby; 400 `invalid_storage` for another number). Its size's (`DatabaseSize.storage_bytes`) when left out. Billed by the GB-month past its first (`DatabaseSize.storage_price_micros_per_gb_month`).
+     */
+    storage_gb?: number;
+    /**
+     * Whether it grows by itself: 90% full, by half, to the next multiple of 5 GB, six hours at least after it last grew; off when left out. Of a size on a disk of its own.
+     */
+    storage_autoscaling?: boolean;
 };
 /**
  * A change to a database; a field left out stays as it is.
@@ -639,9 +659,17 @@ export type DatabaseUpdate = {
      */
     backup_days?: number;
     /**
-     * The database's size (see `Database.size`); one that is paid for is open to the platform's own project and those named for it alone, as it is opened (403 `size_not_available`). One of the same machine and disk and no larger volume — hobby to free — changes in place. Any other moves through an instance of the new size beside the one that serves, made where the new size lives (a disk of its own, or a SAN volume of its own), which then takes over: the database serves on meanwhile (`state` resizing); its sessions on the direct port end once, when its primary moves, and new logins and transactions wait a few seconds for it. One asleep is woken for its move — its awake hours or disk traffic spent or not, when the size it moves to has no such limit; to one whose it has spent, it sleeps — and the move's time counts against none of them. One down for want of room, moved to a size of a larger volume, is given that room first, in place, and moves once it serves. A move that has not come to its switchover within two hours, and a second for every 10 MB the database holds, is let go: the database stays its size, and `state_reason` says why until its size is changed again — as is one whose primary went down three times before it came to its switchover. One whose primary moves where the move did not ask is stopped, both its instances kept (`state_reason`); onto its instance of the new size, ready — as a node drained moves it — it has come to its switchover. One whose instance of the new size does not take over within five minutes of its switchover says so in `state_reason`, and moves on once it does. Its disk never shrinks. While it moves it serves with the connections of the one of the two sizes that takes fewer; the machines given it are rolled out to their share of the new size's — at once when it takes fewer, once it has moved when it takes more. A size smaller than what it holds is refused (409 `database_too_large`), as is one of a smaller quota while what it holds is not measured yet (409 `database_not_measured`, Retry-After), and so is one the project's limit has no room for (409 `machines_over_limit`), a second free database (409 `free_database_taken`), or one whose connections are too few for the copies the machines given it run (409 `database_connections_short`).
+     * The database's size (see `Database.size`); one that is paid for is open to the platform's own project and those named for it alone, as it is opened (403 `size_not_available`). One of the same machine and disk and no larger volume — hobby to free — changes in place. Any other moves through an instance of the new size beside the one that serves, made where the new size lives (a disk of its own, or a SAN volume of its own), which then takes over: the database serves on meanwhile (`state` resizing); its sessions on the direct port end once, when its primary moves, and new logins and transactions wait a few seconds for it. One asleep is woken for its move — its awake hours or disk traffic spent or not, when the size it moves to has no such limit; to one whose it has spent, it sleeps — and the move's time counts against none of them. One down for want of room, moved to a size of a larger volume, is given that room first, in place, and moves once it serves. A move that has not come to its switchover within two hours, and a second for every 10 MB the database holds, is let go: the database stays its size, and `state_reason` says why until its size is changed again — as is one whose primary went down three times before it came to its switchover. One whose primary moves where the move did not ask is stopped, both its instances kept (`state_reason`); onto its instance of the new size, ready — as a node drained moves it — it has come to its switchover. One whose instance of the new size does not take over within five minutes of its switchover says so in `state_reason`, and moves on once it does. Its disk never shrinks, and a database on a disk of its own keeps its storage (`storage_gb`) through the change. While it moves it serves with the connections of the one of the two sizes that takes fewer; the machines given it are rolled out to their share of the new size's — at once when it takes fewer, once it has moved when it takes more. A size smaller than what it holds is refused (409 `database_too_large`), as is one of a smaller quota while what it holds is not measured yet (409 `database_not_measured`, Retry-After), and so is one the project's limit has no room for (409 `machines_over_limit`), a second free database (409 `free_database_taken`), or one whose connections are too few for the copies the machines given it run (409 `database_connections_short`).
+     */
+    size?: "dedicated-1x" | "dedicated-2x" | "free" | "hobby" | "standard-16x" | "standard-1x" | "standard-2x" | "standard-32x" | "standard-4x" | "standard-8x" | "starter";
+    /**
+     * What it holds, grown, in GB: more than it holds, 1 or a multiple of 5, up to 4,000 — never less (409 `storage_shrinks`), and six hours at least after it last grew (409 `storage_grew_recently`, Retry-After). It grows where it is, serving on; it holds the same through a change of size.
+     */
+    storage_gb?: number;
+    /**
+     * Whether it grows by itself: 90% full, by half, to the next multiple of 5 GB, six hours at least after it last grew; off when left out. Of a size on a disk of its own.
      */
-    size?: "dedicated-1x" | "dedicated-2x" | "free" | "hobby" | "standard-1x" | "standard-2x" | "starter";
+    storage_autoscaling?: boolean;
 };
 /**
  * Whose password is made new.
@@ -965,9 +993,9 @@ export type DatabaseCreated = {
      */
     pooled_port: number;
     /**
-     * The database's size. free: 0.25 vCPU, 512 MiB, 1 GB, put to sleep when idle (woken by the next connection in about 10 s), awake 400 hours a month at most, archived after a week asleep (its next connection brings it back from its backup); hobby: 0.25 vCPU, 512 MiB, 5 GB, put to sleep when idle, no monthly limit; starter: 1 GiB, up to 0.5 vCPU, 10 GB; standard-1x: 2 GiB, up to 1 vCPU, 25 GB; standard-2x: 4 GiB, up to 2 vCPU, 50 GB (a quarter of their CPU reserved for them); dedicated-1x: 1 vCPU of its own, 4 GiB, 25 GB; dedicated-2x: 2 vCPU of its own, 8 GiB, 50 GB. The standard and dedicated sizes never sleep and live on a Premium SSD v2 disk of their own; free and hobby on the platform's SAN. A database past its size's storage turns read-only. What a project's machines and databases reserve between them is held to its limit: a size that does not fit is refused (409 `machines_over_limit`).
+     * The database's size. free: 0.25 vCPU, 512 MiB, 1 GB, put to sleep when idle (woken by the next connection in about 10 s), awake 400 hours a month at most, archived after a week asleep (its next connection brings it back from its backup); hobby: 0.25 vCPU, 512 MiB, 5 GB, put to sleep when idle, no monthly limit; starter: 1 GiB, up to 0.5 vCPU, 10 GB; standard-1x: 2 GiB, up to 1 vCPU, 25 GB; standard-2x: 4 GiB, up to 2 vCPU, 50 GB; standard-4x: 16 GiB, up to 4 vCPU; standard-8x: 32 GiB, up to 8 vCPU; standard-16x: 64 GiB, up to 16 vCPU; standard-32x: 128 GiB, up to 32 vCPU, 100 GB each (a quarter of their CPU reserved for them); dedicated-1x: 1 vCPU of its own, 4 GiB, 25 GB; dedicated-2x: 2 vCPU of its own, 8 GiB, 50 GB. The standard and dedicated sizes never sleep and live on a Premium SSD v2 disk of their own; free and hobby on the platform's SAN. The GB of a size that never sleeps are its storage unless `storage_gb` says otherwise (1 or a multiple of 5, up to 4,000), billed by the GB past its first; its size's hours are its CPU and memory. A database past its storage turns read-only — or, `storage_autoscaling` on, grows by half when 90% full. What a project's machines and databases reserve between them is held to its limit: a size that does not fit is refused (409 `machines_over_limit`).
      */
-    size: "dedicated-1x" | "dedicated-2x" | "free" | "hobby" | "standard-1x" | "standard-2x" | "starter";
+    size: "dedicated-1x" | "dedicated-2x" | "free" | "hobby" | "standard-16x" | "standard-1x" | "standard-2x" | "standard-32x" | "standard-4x" | "standard-8x" | "starter";
     /**
      * Where its data lives, as its size says: san, the platform's SAN; premium, a Premium SSD v2 disk of its own.
      */
@@ -988,6 +1016,10 @@ export type DatabaseCreated = {
      * Why it is in its state, when that needs saying.
      */
     state_reason?: string;
+    /**
+     * What `state_reason` says, when a client tells it from the words: no_room — it waits for room in the cluster: a node is being brought up for it (a few minutes), and the platform's operators are told if none can be. Absent otherwise.
+     */
+    state_reason_kind?: "no_room";
     /**
      * When it was deleted; it may be taken back until `purge_after`.
      */
@@ -1015,13 +1047,21 @@ export type DatabaseCreated = {
      */
     used_bytes?: number;
     /**
-     * The most its size holds. Past it, it is read-only.
+     * The most it holds — its size's, or its storage (`storage_gb`). Past it, it is read-only.
      */
     quota_bytes: number;
     /**
      * It holds its quota: a transaction takes no writes unless it asks to — BEGIN READ WRITE, to make room with DROP, TRUNCATE, or DELETE and then VACUUM FULL (a DELETE alone frees no room) — and it reads on. Once it holds less than 95% of its quota it takes writes again, within a minute.
      */
     read_only: boolean;
+    /**
+     * What a database of a size on a disk of its own holds, in GB — its `quota_bytes` — as said when it was opened or grown (`DatabaseUpdate.storage_gb`), or its size's. It grows, never shrinks. Absent for a size on the platform's SAN (free, hobby), which holds its size's.
+     */
+    storage_gb?: number;
+    /**
+     * Whether it grows by itself: 90% full, its storage grows by half, up to the next multiple of 5 GB (10 to 15, 25 to 40), six hours at least after it last grew, to 4,000 GB. Off, a database past its storage turns read-only, and its organization's owners are told at 90% and when it is full. Absent for a size on the platform's SAN.
+     */
+    storage_autoscaling?: boolean;
     /**
      * A change of its passwords (POST …/password) has not reached the database yet: the new password works once this is false, a few seconds after. A client that hands the new password on waits for it.
      */
@@ -1224,7 +1264,7 @@ export type DatabaseSize = {
      */
     memory_mib: number;
     /**
-     * The most it may hold; past it it turns read-only.
+     * What it holds unless said otherwise: its size's; past it it turns read-only. A size that is `storage_adjustable` holds what its database says (`storage_gb`).
      */
     storage_bytes: number;
     /**
@@ -1252,9 +1292,21 @@ export type DatabaseSize = {
      */
     pooled_connections: number;
     /**
-     * What an hour of a database of this size awake costs on Pay as you go, in micro-USD (the price table's; a free size's past its free hours).
+     * What an hour of a database of this size awake costs on Pay as you go, in micro-USD (the price table's; a free size's past its free hours) — of a size on a disk of its own, its CPU and memory alone: its storage is billed by the GB (`storage_price_micros_per_gb_month`).
      */
     price_micros_per_hour: number;
+    /**
+     * A database of this size holds the storage it says (`storage_gb`), up to `max_storage_gb`, and grows; one of another (free, hobby) holds its size's.
+     */
+    storage_adjustable: boolean;
+    /**
+     * The most a database of this size may hold, in GB: 4,000. Absent when it is not `storage_adjustable`.
+     */
+    max_storage_gb?: number;
+    /**
+     * What a GB of its storage costs a month past its first GB, awake, in micro-USD: Render's 0.30 USD. Absent when it is not `storage_adjustable`.
+     */
+    storage_price_micros_per_gb_month?: number;
     /**
      * A size counted against the project's free databases; the others are paid for.
      */