public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jim Vanns <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: VACUUM on temp table blocks VACUUM on another...
Date: Thu, 1 Aug 2024 21:00:54 +0100
Message-ID: <CAH7vdhNsEpRAhSEa4-KbLoRyjecixbnOqZa0_+yqR_t-oXKa1Q@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAH7vdhOhEb4H7UFD+JpOBrS-mOXAtR+vWP4TWD9xk20qHtgV8Q@mail.gmail.com>
<[email protected]>
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 <[email protected]> wrote:
> Jim Vanns <[email protected]> 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
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: VACUUM on temp table blocks VACUUM on another...
In-Reply-To: <CAH7vdhNsEpRAhSEa4-KbLoRyjecixbnOqZa0_+yqR_t-oXKa1Q@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox