| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Giorgio Saviane <gsaviane(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 10:59:05 |
| Message-ID: | CA+bJJbyw8ZNzZRD33VvP7FZho5QpBWy4GXXR1g6iZA9Xm61xAA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, Sep 12, 2020 at 10:59 AM Giorgio Saviane <gsaviane(at)gmail(dot)com> wrote:
....
> The question is: can you implement some warning thrown by vacuum/autovacuum in case orphaned temporary tables are in the way?
> The connection pooler we are using is the one provided by Tomcat 7. I'm gonna check if it supports DISCARD ALL on close.
From what I've read the thing is, if the pooler does not work
correctly ( by issuing discard all or otherwise taking care of
temporary tables ), there are few things as the tables are not
orphaned on the server side.
What the server sees is someone connects, creates the temporary
tables, issues a lot of other commands but does not disconnect, so
the tables must be kept alive in case the the session wants to use
them again. DISCARD ALL will make them orphans.
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Giorgio Saviane | 2020-09-12 11:57:23 | Re: BUG #16614: Stale temporary objects makes vacuum ineffective when 1 million transactions remain |
| Previous Message | Giorgio Saviane | 2020-09-12 08:18:54 | Re: BUG #16614: Stale temporary objects makes vacuum ineffective when 1 million transactions remain |