| From: | Junior Longtom <longtomjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Update documentation to note that REFRESH MATERIALIZED VIEW CONCURRENTLY uses the pg_temp tablespace |
| Date: | 2026-02-10 12:36:43 |
| Message-ID: | CAH6w847gyfxK7pamDutZCoW5n7DAdwo8LnHZSDTMMFhSU8i41g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Good day,
Currently the documentation for REFRESH MATERIALIZED VIEW does not contain
a note that the temporary tablespace is used. It is an implementation
detail, but using the temporary tablespace will block PREPARE TRANSACTION
with an error. I think it would be useful to note that on the docs:
ERROR: cannot PREPARE a transaction that has operated on temporary objects
I think it is worth adding a note to the CONCURRENTLY section on the docs
to state that it will use the temporary tablespace and prevent using
PREPARE TRANSACTION.
It might make sense to update the error message as well. Let me know and I
will raise it on another mailing list as well.
The code that shows the use of the temp tablespace (it was a quick check
from my end, so my conclusion might be wrong):
https://github.com/postgres/postgres/blob/f33c585774223757b01c8eddd134d364492ed94c/src/backend/commands/matview.c#L301-L306
Let me know if you need more information.
Kind Regards
Herman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2026-02-12 11:48:11 | "Disadvantages of increasing autovacuum_freeze_max_age" paragraph to be modified |
| Previous Message | Laurenz Albe | 2026-02-06 13:25:48 | Re: Problem with example numeric value |