| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| 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-11 14:21:21 |
| Message-ID: | 371035.1599834081@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Paquier <michael(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tushar Takate | 2020-09-11 16:48:27 | Re: BUG #16605: PostgreSQL recovery startup process waiting and blocking to application queries |
| Previous Message | Jehan-Guillaume de Rorthais | 2020-09-11 08:09:00 | Re: [BUG v13] Crash with event trigger in extension |