MIME-Version: 1.0
From: Jim Vanns <jvanns@ilm.com>
Date: Thu, 1 Aug 2024 16:54:49 +0100
Message-ID: <CAH7vdhOhEb4H7UFD+JpOBrS-mOXAtR+vWP4TWD9xk20qHtgV8Q@mail.gmail.com>
Subject: VACUUM on temp table blocks VACUUM on another...
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000b0dfbb061ea13bf8"
Archived-At: <https://www.postgresql.org/message-id/CAH7vdhOhEb4H7UFD%2BJpOBrS-mOXAtR%2BvWP4TWD9xk20qHtgV8Q%40mail.gmail.com>
Precedence: bulk

--000000000000b0dfbb061ea13bf8
Content-Type: text/plain; charset="UTF-8"

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

--000000000000b0dfbb061ea13bf8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I have two sessions, each creating a temporary table of th=
e same name - &#39;foobar&#39;. Why would a vacuum of &#39;foobar&#39; from=
 one session block the vacuum of &#39;foobar&#39; in the other session? The=
y&#39;re in separate tablespaces (pg_temp_NN) and effectively distinct with=
 respect to the sessions.<div><br></div><div>Cheers,</div><div><br></div><d=
iv>Jim<br><div><div><br></div><span class=3D"gmail_signature_prefix">-- </s=
pan><br><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_=
signature"><div dir=3D"ltr">Jim Vanns<br>Principal Production Engineer<br>I=
ndustrial Light &amp; Magic, London</div></div></div></div></div>

--000000000000b0dfbb061ea13bf8--