public inbox for [email protected]  
help / color / mirror / Atom feed
VACUUM on temp table blocks VACUUM on another...
3+ messages / 2 participants
[nested] [flat]

* VACUUM on temp table blocks VACUUM on another...
@ 2024-08-01 15:54  Jim Vanns <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: Jim Vanns @ 2024-08-01 15:54 UTC (permalink / raw)
  To: [email protected]

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? They're in separate tablespaces
(pg_temp_NN) and effectively distinct with respect to the sessions.

Cheers,

Jim

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


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: VACUUM on temp table blocks VACUUM on another...
@ 2024-08-01 19:12  Tom Lane <[email protected]>
  parent: Jim Vanns <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2024-08-01 19:12 UTC (permalink / raw)
  To: Jim Vanns <[email protected]>; +Cc: [email protected]

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






^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: VACUUM on temp table blocks VACUUM on another...
@ 2024-08-01 20:00  Jim Vanns <[email protected]>
  parent: Tom Lane <[email protected]>
  0 siblings, 0 replies; 3+ messages in thread

From: Jim Vanns @ 2024-08-01 20:00 UTC (permalink / raw)
  To: Tom Lane <[email protected]>; +Cc: [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


^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2024-08-01 20:00 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-08-01 15:54 VACUUM on temp table blocks VACUUM on another... Jim Vanns <[email protected]>
2024-08-01 19:12 ` Tom Lane <[email protected]>
2024-08-01 20:00   ` Jim Vanns <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox