| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Giorgio Saviane <gsaviane(at)gmail(dot)com> |
| Cc: | Francisco Olarte <folarte(at)peoplecall(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL mailing lists <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 18:18:04 |
| Message-ID: | 653162.1599934684@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Giorgio Saviane <gsaviane(at)gmail(dot)com> writes:
> Ok, let me add one more step in that sequence.
> Before shutting down Postgres and going down to single mode we stopped the
> application server and other services around it. I'm pretty sure that there
> was a reasonable window of time before we went to single mode.
Hmm, but did you stop the connection pooler? That's what was holding
the database session open, if I'm understanding things correctly.
Unless you've changed the default autovacuum settings (particularly
autovacuum_naptime), I'd have expected autovacuum to start zapping
temp tables within a minute or so after they become orphaned.
Even more to the point, if the database session was allowed to stop
normally, it should've cleaned them up itself.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Giorgio Saviane | 2020-09-12 18:38:29 | Re: BUG #16614: Stale temporary objects makes vacuum ineffective when 1 million transactions remain |
| Previous Message | Giorgio Saviane | 2020-09-12 16:06:10 | Re: BUG #16614: Stale temporary objects makes vacuum ineffective when 1 million transactions remain |