Re: VACUUM on temp table blocks VACUUM on another... - Mailing list pgsql-general

From Jim Vanns
Subject Re: VACUUM on temp table blocks VACUUM on another...
Date
Msg-id CAH7vdhNsEpRAhSEa4-KbLoRyjecixbnOqZa0_+yqR_t-oXKa1Q@mail.gmail.com
Whole thread Raw
In response to Re: VACUUM on temp table blocks VACUUM on another...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I don't at hand, but the query I used to identify this was;

SELECT state, pid, pg_blocking_pids(pid), query
FROM pg_stat_activity
WHERE backend_type='client backend';

On Thu, 1 Aug 2024 at 20:12, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Jim Vanns <jvanns@ilm.com> writes:
> I have two sessions, each creating a temporary table of the same name -
> 'foobar'. Why would a vacuum of 'foobar' from one session block the vacuum
> of 'foobar' in the other session?

That's fairly hard to believe.  Can you provide a self-contained test
case?

                        regards, tom lane


--
Jim Vanns
Principal Production Engineer
Industrial Light & Magic, London

pgsql-general by date:

Previous
From: Jim Vanns
Date:
Subject: Re: VACUUM on temp table blocks VACUUM on another...
Next
From: Ron Johnson
Date:
Subject: Re: VACUUM on temp table blocks VACUUM on another...