| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Temporary tables prevent autovacuum, leading to XID wraparound |
| Date: | 2018-02-06 23:03:26 |
| Message-ID: | 20180206230326.GA16659@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 06, 2018 at 11:33:59AM -0500, Robert Haas wrote:
> This is really two separate changes:
>
> 1. Teach backends to remove any leftover pg_temp_%d schema on
> startup.
I am not sure that we would like to give up that easily the property
that we have now to clean up past temporary files only at postmaster
startup and only when not in recovery. If you implement that, there is
a risk that the backend you are starting is eating the connection slot
and by consequence its temporary schema and its set of temporary tables
on which one may want to look into after a crash.
> 2. Teach autovacuum to remove any leftover tables in a pg_temp_%d
> schema if the backend is active but in some other database (rather
> than only when the backend is not active at all).
Yeah. Here we can do something. This does not sound much difficult to
me.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tsunakawa, Takayuki | 2018-02-07 00:37:50 | RE: Temporary tables prevent autovacuum, leading to XID wraparound |
| Previous Message | Peter Geoghegan | 2018-02-06 22:27:47 | Re: PostgreSQL crashes with SIGSEGV |