MIME-Version: 1.0
From: Junior Longtom <longtomjr@gmail.com>
Date: Tue, 10 Feb 2026 14:36:43 +0200
Message-ID: 
 <CAH6w847gyfxK7pamDutZCoW5n7DAdwo8LnHZSDTMMFhSU8i41g@mail.gmail.com>
Subject: Update documentation to note that REFRESH MATERIALIZED VIEW
 CONCURRENTLY uses the pg_temp tablespace
To: pgsql-docs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000af9a78064a778215"
Archived-At: 
 <https://www.postgresql.org/message-id/CAH6w847gyfxK7pamDutZCoW5n7DAdwo8LnHZSDTMMFhSU8i41g%40mail.gmail.com>
Precedence: bulk

--000000000000af9a78064a778215
Content-Type: text/plain; charset="UTF-8"

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

--000000000000af9a78064a778215
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Good day,</div><div><br></div><div>Currently the docu=
mentation for=C2=A0REFRESH MATERIALIZED VIEW does not contain a note that t=
he temporary tablespace is used. It is an implementation detail, but using =
the temporary tablespace will block PREPARE TRANSACTION with an error. I th=
ink it would be useful to note that on the docs:</div><div><br></div><div>E=
RROR: =C2=A0cannot PREPARE a transaction that has operated on temporary obj=
ects</div><div><br></div><div>I think it is worth adding a note to the CONC=
URRENTLY section on the docs to state that it will use the temporary tables=
pace and prevent using PREPARE TRANSACTION.</div><div><br></div><div>It mig=
ht make sense to update the error message as well. Let me know and I will r=
aise it on another mailing list as well.</div><div><br></div><div>The code =
that shows the use of the temp tablespace (it was a quick check from my end=
, so my conclusion might be wrong):=C2=A0<a href=3D"https://github.com/post=
gres/postgres/blob/f33c585774223757b01c8eddd134d364492ed94c/src/backend/com=
mands/matview.c#L301-L306">https://github.com/postgres/postgres/blob/f33c58=
5774223757b01c8eddd134d364492ed94c/src/backend/commands/matview.c#L301-L306=
</a></div><div><br></div><div>Let me know if you=C2=A0need more information=
.</div><div><br></div><div>Kind Regards</div><div>Herman</div></div>

--000000000000af9a78064a778215--