155 lines
6.7 KiB
ReStructuredText
155 lines
6.7 KiB
ReStructuredText
.. _schema_cache:
|
|
|
|
Schema Cache
|
|
============
|
|
|
|
Certain PostgREST features require metadata from the database schema. Getting this metadata requires executing expensive queries, so
|
|
in order to avoid repeating this work, PostgREST uses a schema cache.
|
|
|
|
The following features are the ones that require metadata from the schema cache.
|
|
|
|
+--------------------------------------------+-------------------------------------------------------------------------------+
|
|
| Feature | Required Metadata |
|
|
+============================================+===============================================================================+
|
|
| :ref:`resource_embedding` | Foreign key constraints |
|
|
+--------------------------------------------+-------------------------------------------------------------------------------+
|
|
| :ref:`Stored Functions <s_procs>` | Function signature (parameters, return type, volatility and |
|
|
| | `overloading <https://www.postgresql.org/docs/current/xfunc-overload.html>`_) |
|
|
+--------------------------------------------+-------------------------------------------------------------------------------+
|
|
| :ref:`Upserts <upsert>` | Primary keys |
|
|
+--------------------------------------------+-------------------------------------------------------------------------------+
|
|
| :ref:`Insertions <insert_update>` | Primary keys (optional: only if the Location header is requested) |
|
|
+--------------------------------------------+-------------------------------------------------------------------------------+
|
|
| :ref:`OPTIONS requests <options_requests>` | View INSTEAD OF TRIGGERS and primary keys |
|
|
+--------------------------------------------+-------------------------------------------------------------------------------+
|
|
| :ref:`open-api` | Table columns, primary keys and foreign keys |
|
|
+ +-------------------------------------------------------------------------------+
|
|
| | View columns and INSTEAD OF TRIGGERS |
|
|
+ +-------------------------------------------------------------------------------+
|
|
| | Function signature |
|
|
+--------------------------------------------+-------------------------------------------------------------------------------+
|
|
|
|
The Stale Schema Cache
|
|
----------------------
|
|
|
|
When you make changes on the metadata mentioned above, the schema cache will turn stale on a running PostgREST. Future requests that use the above features will need the :ref:`schema cache to be reloaded <schema_reloading>`; otherwise, you'll get an error instead of the expected result.
|
|
|
|
For instance, let's see what would happen if you have a stale schema for foreign key relationships and function signature:
|
|
|
|
Stale Foreign Key Relationships
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Suppose you add a ``cities`` table to your database. This table has a foreign key referencing an existing ``countries`` table. Then, you make a request to get the ``cities`` and their belonging ``countries``:
|
|
|
|
.. code-block:: http
|
|
|
|
GET /cities?select=name,country:countries(id,name) HTTP/1.1
|
|
|
|
But instead, you get an error message that looks like this:
|
|
|
|
.. code-block:: json
|
|
|
|
{
|
|
"hint": "If a new foreign key between these entities was created in the database, try reloading the schema cache.",
|
|
"message": "Could not find a relationship between cities and countries in the schema cache"
|
|
}
|
|
|
|
As you can see, PostgREST couldn't find the newly created foreign key in the schema cache. See the section :ref:`schema_reloading` to solve this issue.
|
|
|
|
.. _stale_function_signature:
|
|
|
|
Stale Function Signature
|
|
~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Suppose you create the following function while PostgREST is running:
|
|
|
|
.. code-block:: plpgsql
|
|
|
|
CREATE FUNCTION plus_one(num integer)
|
|
RETURNS integer AS $$
|
|
SELECT num + 1;
|
|
$$ LANGUAGE SQL IMMUTABLE;
|
|
|
|
Then, you make this request:
|
|
|
|
.. code-block:: http
|
|
|
|
GET /rpc/plus_one?num=1 HTTP/1.1
|
|
|
|
Next, PostgREST tries to find the function on the stale schema to no avail:
|
|
|
|
.. code-block:: json
|
|
|
|
{
|
|
"hint": "If a new function was created in the database with this name and arguments, try reloading the schema cache.",
|
|
"message": "Could not find the api.plus_one(num) function in the schema cache"
|
|
}
|
|
|
|
See the section :ref:`schema_reloading` to solve this issue.
|
|
|
|
.. _schema_reloading:
|
|
|
|
Schema Cache Reloading
|
|
----------------------
|
|
|
|
To refresh the cache without restarting the PostgREST server, send a SIGUSR1 signal to the server process.
|
|
|
|
.. code:: bash
|
|
|
|
killall -SIGUSR1 postgrest
|
|
|
|
|
|
For docker you can do:
|
|
|
|
.. code:: bash
|
|
|
|
docker kill -s SIGUSR1 <container>
|
|
|
|
# or in docker-compose
|
|
docker-compose kill -s SIGUSR1 <service>
|
|
|
|
.. note::
|
|
|
|
There's no downtime when reloading the schema cache. The reloading will happen on a background thread while requests keep being served.
|
|
|
|
.. _schema_reloading_notify:
|
|
|
|
Reloading with NOTIFY
|
|
~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
There are environments where you can't send the SIGUSR1 Unix Signal (like on managed containers in cloud services or on Windows systems). For this reason, PostgREST also allows you to reload its schema cache through PostgreSQL `NOTIFY <https://www.postgresql.org/docs/current/sql-notify.html>`_ as follows:
|
|
|
|
.. code-block:: postgresql
|
|
|
|
NOTIFY pgrst, 'reload schema'
|
|
|
|
The ``"pgrst"`` notification channel is enabled by default. For configuring the channel, see :ref:`db-channel` and :ref:`db-channel-enabled`.
|
|
|
|
Automatic schema cache reloading
|
|
********************************
|
|
|
|
You can do automatic schema cache reloading in a pure SQL way with an `event trigger <https://www.postgresql.org/docs/current/event-trigger-definition.html>`_ and ``NOTIFY``.
|
|
|
|
.. code-block:: postgresql
|
|
|
|
-- Create an event trigger function
|
|
CREATE OR REPLACE FUNCTION public.pgrst_watch() RETURNS event_trigger
|
|
LANGUAGE plpgsql
|
|
AS $$
|
|
BEGIN
|
|
NOTIFY pgrst;
|
|
END;
|
|
$$;
|
|
|
|
-- This event trigger will fire after every ddl_command_end event
|
|
CREATE EVENT TRIGGER pgrst_watch
|
|
ON ddl_command_end
|
|
EXECUTE PROCEDURE public.pgrst_watch();
|
|
|
|
Now, whenever the ``pgrst_watch`` trigger is fired in the database, PostgREST will automatically reload the schema cache.
|
|
|
|
To disable auto reloading, drop the trigger:
|
|
|
|
.. code-block:: postgresql
|
|
|
|
DROP EVENT TRIGGER pgrst_watch |