docs: add note about schema cache queries
This commit is contained in:
committed by
Steve Chavez
parent
f939a81ad6
commit
6af77360d3
@@ -3,10 +3,15 @@
|
|||||||
Schema Cache
|
Schema Cache
|
||||||
============
|
============
|
||||||
|
|
||||||
PostgREST requires metadata from the database schema to provide a REST API that abstracts SQL details. One example of this is the interface for :ref:`resource_embedding`.
|
PostgREST requires metadata from the database to provide a REST API that abstracts SQL details. One example of this is the interface for :ref:`resource_embedding`.
|
||||||
|
|
||||||
Getting this metadata requires expensive queries. To avoid repeating this work, PostgREST uses a schema cache.
|
Getting this metadata requires expensive queries. To avoid repeating this work, PostgREST uses a schema cache.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
- Schema cache queries have been optimized over time to stay fast, even on complex databases. You can see a summary of their execution time in :ref:`pgrst_logging` and :ref:`metrics`.
|
||||||
|
- If the schema cache queries are slow, the most likely cause is *system catalog bloat*, see `issue#3212 <https://github.com/PostgREST/postgrest/issues/3212>`_ for more details.
|
||||||
|
|
||||||
.. _schema_reloading:
|
.. _schema_reloading:
|
||||||
|
|
||||||
Schema Cache Reloading
|
Schema Cache Reloading
|
||||||
|
|||||||
Reference in New Issue
Block a user