| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(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-07 16:22:42 |
| Message-ID: | CA+Tgmoax9FtOfJtjkyWqqhKY=_v1qYTLs3TGn_GNVwp0tmLbnw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 6, 2018 at 6:03 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> 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.
You can't actually do that from SQL, because as soon as you try to
access your pg_temp schema, it'll be cleared out. All this changes
does is move that forward from time-of-first-access to session start.
That's a significant change that needs discussion, but I don't think
it has the effect you are supposing.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arthur Zakirov | 2018-02-07 16:28:29 | Re: [PROPOSAL] Shared Ispell dictionaries |
| Previous Message | Robert Haas | 2018-02-07 16:17:43 | Re: [HACKERS] PATCH: enabling parallel execution for cursors explicitly (experimental) |