PostgREST/postgrest v9.0.0.20220531

on GitHub

Added

• #1933, #2109, Add a minimal health check endpoint - @steve-chavez
  • For enabling this, the admin-server-port config must be set explictly
  • A <host>:<admin_server_port>/live endpoint is available for checking if postgrest is running on its port/socket. 200 OK = alive, 503 = dead.
  • A <host>:<admin_server_port>/ready endpoint is available for checking a correct internal state(the database connection plus the schema cache). 200 OK = ready, 503 = not ready.
• #1988, Add the current user to the request log on stdout - @DavidLindbom, @wolfgangwalther
• #1823, Add the ability to run postgrest without any configuration. - @wolfgangwalther
  • #1991, Add the ability to run without db-uri using libpq's PG environment variables to connect. - @wolfgangwalther
  • #1769, Add the ability to run without db-schemas, defaulting to db-schemas=public. - @wolfgangwalther
  • #1689, Add the ability to run without db-anon-role disabling anonymous access. - @wolfgangwalther
• #1543, Allow access to fields of composite types in select=, order= and filters through JSON operators -> and ->>. - @wolfgangwalther
• #2075, Allow access to array items in ?select=, ?order= and filters through JSON operators -> and ->>. - @wolfgangwalther
• #2156, #2211, Allow applying limit/offset to UPDATE/DELETE to only affect a subset of rows - @steve-chavez
  • It requires an explicit order on a unique column(s)
• #1917, Add error codes with the "PGRST" prefix to the error response body to differentiate PostgREST errors from PostgreSQL errors - @laurenceisla
• #1917, Normalize the error response body by always having the detail and hint error fields with a null value if they are empty - @laurenceisla
• #2176, Errors raised with SQLSTATE now include the message and the code in the response body - @laurenceisla
• #2236, Support POSIX regular expression operators for row filtering - @enote-kane
• #2202, Allow returning XML from RPCs - @fjf2002
• #2269, Allow limit=0 in the request query to return an empty array - @gautam1168, @laurenceisla
• #2268, Allow returning XML from single-column queries #2268 - @fjf2002

Fixed

• #2165, Fix json/jsonb columns should not have type in OpenAPI spec
• #2020, Execute deferred constraint triggers when using Prefer: tx=rollback - @wolfgangwalther
• #2058, Return 204 No Content without Content-Type for PUT - @wolfgangwalther
• #2077, Fix is not working with upper or mixed case values like NULL, TrUe, FaLsE - @steve-chavez
• #2024, Fix schema cache loading when views with XMLTABLE and DEFAULT are present - @wolfgangwalther
• #1724, Fix wrong CORS header Authentication -> Authorization - @wolfgangwalther
• #2107, Clarify error for failed schema cache load. - @steve-chavez
  • From Database connection lost. Retrying the connection to Could not query the database for the schema cache. Retrying.
• #2120, Fix reading database configuration properly when = is present in value - @wolfgangwalther
• #1771, Fix silently ignoring filter on a non-existent embedded resource - @steve-chavez
• #2135, Remove trigger functions from schema cache and OpenAPI output, because they can't be called directly anyway. - @wolfgangwalther
• #2101, Remove aggregates, procedures and window functions from the schema cache and OpenAPI output. - @wolfgangwalther
• #2152, Remove functions, which are uncallable because of unnamend arguments from schema cache and OpenAPI output. - @wolfgangwalther
• #2145, Fix accessing json array fields with -> and ->> in ?select= and ?order=. - @wolfgangwalther
• #2153, Fix --dump-schema running with a wrong PG version. - @wolfgangwalther
• #2042, Keep working when EMFILE(Too many open files) is reached. - @steve-chavez
• #2147, Ignore Content-Type headers for GET requests when calling RPCs. Previously, GET without parameters, but with Content-Type: text/plain or Content-Type: application/octet-stream would fail with 404 Not Found, even if a function without arguments was available.
• #2155, Ignore max-rows on POST, PATCH, PUT and DELETE - @steve-chavez
• #2239, Fix misleading disambiguation error where the content of the relationship key looks like valid syntax - @laurenceisla
• #2254, Fix inferring a foreign key column as a primary key column on views - @steve-chavez
• #2070, Restrict generated many-to-many relationships - @steve-chavez
  • Only adds many-to-many relationships when: a table has FKs to two other tables and these FK columns are part of the table's PK columns.
• #2278, Allow casting to types with underscores and numbers(e.g. select=oid_array::_int4) - @steve-chavez
• #2277, #2238, #1643, Prevent views from breaking one-to-many/many-to-one embeds when using column or FK as target - @steve-chavez
  • When using a column or FK as target for embedding(/tbl?select=*,col-or-fk(*)), only tables are now detected and views are not.
  • You can still use a column or an inferred FK on a view to embed a table(/view?select=*,col-or-fk(*))
• #2294, Disable parallel GC for better performance on higher core CPUs - @steve-chavez
• #1076, Fix using CPU while idle - @steve-chavez

Changed

• #2001, Return 204 No Content without Content-Type for RPCs returning VOID - @wolfgangwalther
  • Previously, those RPCs would return "null" as a body with Content-Type: application/json.
• #2156, limit/offset now limits the affected rows on UPDATE/DELETE - @steve-chavez
  • Previously, limit/offset only limited the returned rows but not the actual updated rows
• #2156, using PATCH/DELETE with limit/offset throws an error on views - @steve-chavez
• #2155, max-rows is no longer applied on POST/PATCH/PUT/DELETE returned rows - @steve-chavez
  • This was misleading because the affected rows were not really affected by max-rows, only the returned rows were limited
• #2070, Restrict generated many-to-many relationships - @steve-chavez
  • A primary key that contains the foreign key columns is now needed for generating many-to-many relationships.
• #2277, Views now are not detected when embedding using the column or FK as target (/view?select=*,column(*)) - @steve-chavez
  • This embedding form was easily made ambiguous whenever a new view was added.
  • For migrating, clients must be updated to the embedding form of /view?select=*,other_view!column(*).