Re: Global temporary tables
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Dean Rasheed <dean.a.rasheed@gmail.com>
Cc: Kirk Wolak <wolakk@gmail.com>, Andrew Dunstan <andrew@dunslane.net>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-06-30T20:32:19Z
Lists: pgsql-hackers
út 30. 6. 2026 v 22:21 odesílatel Dean Rasheed <dean.a.rasheed@gmail.com> napsal: > On Tue, 30 Jun 2026 at 20:29, Pavel Stehule <pavel.stehule@gmail.com> > wrote: > > > > I am testing this patchset. Generally, it looks very well. I didn't see > any bloat on catalog > > > > I found an issue - TRUNCATE waits when gtt is used by different > transactions, and TRUNCATE removes content in all sessions. > > > > Is it expected? > > Thanks for testing! > > The waiting issue for TRUNCATE is interesting. I hadn't considered > that at all, so TRUNCATE on a global temporary table still takes an > access exclusive lock, like any other table, but I guess that's not > necessary. I wonder what lock level we could reduce it to. > > I can't reproduce TRUNCATE removing content in all sessions, but > that's definitely not supposed to happen. Can you share what you did > to cause that? > > I cannot reproduce it now. I was confused. I am sorry for the noise. Regards Pavel > Regards, > Dean >
Commits
-
doc: clarify MERGE PARTITIONS adjacency requirement
- 57f19774d6c8 master cited