Re: BUG #16614: Stale temporary objects makes vacuum ineffective when 1 million transactions remain

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: gsaviane(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16614: Stale temporary objects makes vacuum ineffective when 1 million transactions remain
Date: 2020-09-12 01:48:52
Message-ID: 20200912014852.GM2743@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Sep 11, 2020 at 10:21:21AM -0400, Tom Lane wrote:
> 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.

Oh, OK, thanks! That was not mentioned originally so I got confused.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Giorgio Saviane 2020-09-12 08:18:54 Re: BUG #16614: Stale temporary objects makes vacuum ineffective when 1 million transactions remain
Previous Message Alvaro Herrera 2020-09-12 00:22:58 Re: [BUG v13] Crash with event trigger in extension