From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
---|---|
To: | 'Michael Paquier' <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "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-07 00:37:50 |
Message-ID: | 0A3221C70F24FB45833433255569204D1F8B14C4@G01JPEXMBYT05 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: Michael Paquier [mailto:michael(dot)paquier(at)gmail(dot)com]
> 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.
postmaster deletes temporary relation files at startup by calling RemovePgTempFiles() regardless of whether it's in recovery. It doesn't call that function during auto restart after a crash when restart_after_crash is on.
> > 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.
I did that in my patch.
Regards
Takayuki Tsunakawa
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2018-02-07 00:43:40 | Re: Temporary tables prevent autovacuum, leading to XID wraparound |
Previous Message | Michael Paquier | 2018-02-06 23:03:26 | Re: Temporary tables prevent autovacuum, leading to XID wraparound |