Re: VACUUM on temp table blocks VACUUM on another...

From: Jim Vanns <jvanns(at)ilm(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: VACUUM on temp table blocks VACUUM on another...
Date: 2024-08-01 20:00:54
Message-ID: CAH7vdhNsEpRAhSEa4-KbLoRyjecixbnOqZa0_+yqR_t-oXKa1Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Jim Vanns <jvanns(at)ilm(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2024-08-01 21:26:40 Re: VACUUM on temp table blocks VACUUM on another...
Previous Message Jim Vanns 2024-08-01 19:58:06 Re: VACUUM on temp table blocks VACUUM on another...