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 1sZbz5-002Chb-AT for pgsql-general@arkaria.postgresql.org; Thu, 01 Aug 2024 20:01:11 +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 1sZbz3-00D9TY-Sy for pgsql-general@arkaria.postgresql.org; Thu, 01 Aug 2024 20:01:09 +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 1sZbz3-00D9TP-Hc for pgsql-general@lists.postgresql.org; Thu, 01 Aug 2024 20:01:09 +0000 Received: from mail-io1-xd35.google.com ([2607:f8b0:4864:20::d35]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sZbz1-002b9I-6P for pgsql-general@lists.postgresql.org; Thu, 01 Aug 2024 20:01:08 +0000 Received: by mail-io1-xd35.google.com with SMTP id ca18e2360f4ac-81f921c40a0so293203539f.0 for ; Thu, 01 Aug 2024 13:01:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ilm.com; s=google; t=1722542466; x=1723147266; darn=lists.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=G2CAWyB9aP8yyVUNC2BJuVUfPET6msOeu1g1ruR4vlw=; b=AvRLRRpb7jugVyFDZb7og3bBkDrtonlntp/Jn4XlfqKtzvVp1rTNw47qMfwohwgKeo ii0F/D8RlMpP6jMiztekXFMv80mXUXXhDmR4ZQdyG3VNlqivs6LsFPrw8LMqRWVPqd88 Z7HJtq1jik9O4GxZ/wYQInZ6SaECJOfwPFw7Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722542466; x=1723147266; 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=G2CAWyB9aP8yyVUNC2BJuVUfPET6msOeu1g1ruR4vlw=; b=AZnkF6S9cX17n5InkkOUsmqNCMTSz7ho3CcbEF6B5yZp7FjTeu3/O7a3jy02PiVq2y ORWCoVdcw0vEiCHYlDBEllM24iGqvyarH+9piAJK5y8VZv24f3JG3fFfKCVKSSNkGKDu yaykSnNS4mfvfNOoNd9kvdxrRO3kgJRLc/6rEaSQDpOAu36sU9q+WTmd4XohYXju2DBo ifvQHPkdOLv25o3XCX/F2YlcoutAizTm3zf8HEFAKLOBMs+Sh9F3g4QAiYCa9RpPNYQN GG5GkOQPtMdpDn1fetYvOma7rSebVeqBinNg49NjbfsKIrKwS5w97PoeaWQQQ1yS9bih SHoQ== X-Gm-Message-State: AOJu0YxORJ1ckCAAG+TWv+a6E0LbiJB3JBxjOvjA4Mdh+H31PU82eq7K SYI6I+1LgEUnlfDHOLeJqKiMUcZI9WT6HdfwLBD+WSWSjePmXxcbqIuRiU726fdqwq+sDVsmdHb Odfl41touZ7X21nYYjfc7rYaJXSIo9quyhr/3wIM0P9zDl2jfP9Q= X-Google-Smtp-Source: AGHT+IHf2Yr9fy3+sXSPsQXlNXsv6OWrZIDL1nPnsjIokvEfwtQTqDzFROTl5lcHDGqwWmWNbFFhgUgPvQgPMiBk+Pk= X-Received: by 2002:a05:6602:26cf:b0:81f:b38c:3537 with SMTP id ca18e2360f4ac-81fd437abd6mr229773339f.10.1722542466386; Thu, 01 Aug 2024 13:01:06 -0700 (PDT) MIME-Version: 1.0 References: <3780009.1722539561@sss.pgh.pa.us> In-Reply-To: <3780009.1722539561@sss.pgh.pa.us> From: Jim Vanns Date: Thu, 1 Aug 2024 21:00:54 +0100 Message-ID: Subject: Re: VACUUM on temp table blocks VACUUM on another... To: Tom Lane Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000d1ec14061ea4abb8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d1ec14061ea4abb8 Content-Type: text/plain; charset="UTF-8" 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 wrote: > Jim Vanns 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 --000000000000d1ec14061ea4abb8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I don't at hand, but the query I used to identify this= was;

SELECT state, pid, pg_blocking_pids(pid), queryFROM pg_stat_activity
WHERE backend_type=3D'client backend';

On Thu, 1 Aug 2024 at 20:12, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Jim Vanns <jvanns@ilm.com> writes:
> I have two sessions, each creating a temporary table of the same name = -
> 'foobar'. Why would a vacuum of 'foobar' from one sess= ion block the vacuum
> of 'foobar' in the other session?

That's fairly hard to believe.=C2=A0 Can you provide a self-contained t= est
case?

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 regards, tom lane


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