Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sZe3l-002Qyw-1T for pgsql-general@arkaria.postgresql.org; Thu, 01 Aug 2024 22:14:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sZe3i-00DjJY-D0 for pgsql-general@arkaria.postgresql.org; Thu, 01 Aug 2024 22:14:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sZe3i-00DjJQ-03 for pgsql-general@lists.postgresql.org; Thu, 01 Aug 2024 22:14:06 +0000 Received: from mail-io1-xd30.google.com ([2607:f8b0:4864:20::d30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sZe3X-002c58-GO for pgsql-general@postgresql.org; Thu, 01 Aug 2024 22:14:04 +0000 Received: by mail-io1-xd30.google.com with SMTP id ca18e2360f4ac-81f921c40a0so298090939f.0 for ; Thu, 01 Aug 2024 15:13:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ilm.com; s=google; t=1722550434; x=1723155234; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/ezzYENJtrRPpGeYpI3xT41lfZZ5e21ss24Dr7lp9jw=; b=YCIY3jL5aVUhzYQgLZczmpTCUAl1lXvvtDiEnCtQ5GzSvnjMLgMXc4pCcGGcazfFY3 pNuLmCLfNu4niWOOv2bON9wqI1K9K1fMgzHLYiYtR6sAYkdROhQFBE3XDX1MvL88ZmmS 2dHOrI4M9juwm7FiM7iaIA7c8US51Nc/5lDg0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722550434; x=1723155234; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/ezzYENJtrRPpGeYpI3xT41lfZZ5e21ss24Dr7lp9jw=; b=o4RCkVzlZdGJIKE15RZulsyZ3/vyHpD3+0Ix+qZUjTBcna6eVw/6WVxv/pXvUjzjYZ Y/CpTtDUU2npvNDMEugNrxU/6+mwQ9lo12APOys4KN85mGYOcwjHyWrU7Gt1ePe8iXau iSHcPJs6uvcLB4FZKlRI/GZsL17sIGd6Jd18f4DNje/5WopLflqVORj5HX/oaqpcP9Og puur48/tXgxs5baU42pv63y4IbvwodSEQyYB3989ZqA3oKpTQ1G2JhmbeA4Rr8iPuhP1 FjWoPPbn6uKslXXEqwA8MuuIKABzhxc+jOCiccxriR7ojuF37esdcCbKh3my8aRLeoEv Pzvw== X-Gm-Message-State: AOJu0YyQDtUUjSLh6HoaQ3pY0McT1sMjajakmUtEyhqd4FhZS+Yg2zp/ K0aO/XoKwwaSM9KboBI+ppklHrc+eTPjrey0jzg+dAr2RV8qLAigweGqNcEmJeTFUtpxdWhg2th ukdq+0+Kgxw7U8WgbPP+CrOul89I4SuAw4yHQQr3XNYtgloPB X-Google-Smtp-Source: AGHT+IFxmxQakAAS8WphriceIGiEiINAvYFHl4xtUX9pB8+OzaU/EcSVDT1sMA/9DTIRzlM9Xl176NSzSxmXUQsqlRk= X-Received: by 2002:a05:6602:1512:b0:7f8:c0eb:7adf with SMTP id ca18e2360f4ac-81fd42bd0ebmr262587139f.0.1722550434107; Thu, 01 Aug 2024 15:13:54 -0700 (PDT) MIME-Version: 1.0 References: <3780009.1722539561@sss.pgh.pa.us> <2583d693-f728-46d6-af57-5012cb223b28@aklaver.com> In-Reply-To: From: Jim Vanns Date: Thu, 1 Aug 2024 23:13:43 +0100 Message-ID: Subject: Re: VACUUM on temp table blocks VACUUM on another... To: Ron Johnson Cc: pgsql-general Content-Type: multipart/alternative; boundary="000000000000bba975061ea68605" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000bba975061ea68605 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable PG 15.4 On Thu, 1 Aug 2024 at 22:27, Ron Johnson wrote: > PG 15.0 or 15.7? > > On Thu, Aug 1, 2024 at 3:58=E2=80=AFPM Jim Vanns wrote: > >> Sorry, PG15. >> >> Jim >> >> On Thu, 1 Aug 2024 at 20:25, Adrian Klaver >> wrote: >> >>> On 8/1/24 12:12, Tom Lane wrote: >>> > Jim Vanns writes: >>> >> I have two sessions, each creating a temporary table of the same nam= e >>> - >>> >> '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? >>> >>> Would also be nice to know what version of Postgres and where you are >>> running the server? >>> >>> > >>> > regards, tom lane >>> > >>> > >>> >>> -- >>> Adrian Klaver >>> adrian.klaver@aklaver.com >>> >>> >> >> -- >> Jim Vanns >> Principal Production Engineer >> Industrial Light & Magic, London >> > --=20 Jim Vanns Principal Production Engineer Industrial Light & Magic, London --000000000000bba975061ea68605 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
PG 15.4

On Thu, 1 Aug 2024 at 22:27, Ron Johnson <ronljohnsonjr@gmail.com> wrote:=
PG 15.0 or 15.7?

On Thu, Aug 1, 2024 at 3:58=E2=80=AFPM Jim Vanns <= ;jvanns@ilm.com>= wrote:
Sorry, PG15.

Jim

On Thu, 1 Aug 2024 at 20:= 25, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 8/1/24 12:12, Tom Lane wrote:
> Jim Vanns <jvan= ns@ilm.com> writes:
>> I have two sessions, each creating a temporary table of the same n= ame -
>> '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.=C2=A0 Can you provide a self-contai= ned test
> case?

Would also be nice to know what version of Postgres and where you are
running the server?

>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0regards, tom lane
>
>

--
Adrian Klaver
adrian.klave= r@aklaver.com



--
Jim Vanns
Principal Production Engineer
Industrial Lig= ht & Magic, London


--
Jim Vanns
Principal Production Engineer
Industrial Lig= ht & Magic, London
--000000000000bba975061ea68605--