From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: gsaviane@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16614: Stale temporary objects makes vacuum ineffective when 1 million transactions remain
Date: Fri, 11 Sep 2020 10:21:21 -0400
Message-ID: <371035.1599834081@sss.pgh.pa.us> (raw)
In-Reply-To: <20200911063036.GH2743@paquier.xyz>
References: <16614-23e5c4c4567d1576@postgresql.org>
<182231.1599749034@sss.pgh.pa.us>
<20200911063036.GH2743@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> Yeah. 11 and newer versions have been made even more aggressive with
> the cleanup of orphaned tables in autovacuum, particularly the case
> where a backend reuses the ID of a past session that crashed, leaving
> behind some temporary tables. Perhaps that was the case here?
Off-list, the OP indicated that the problem is actually of the other
category, ie the problematic tables belong to extremely long-lived
sessions that are managed by a connection pooler. I don't quite
understand why the pooler isn't issuing DISCARD ALL between clients,
but anyway it seems that PG is operating as designed here.
regards, tom lane
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, gsaviane@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16614: Stale temporary objects makes vacuum ineffective when 1 million transactions remain
In-Reply-To: <371035.1599834081@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox