| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Jerry Sievers <gsievers19(at)comcast(dot)net>, Mark Dilger <hornschnorter(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Use of non-restart-safe storage by temp_tablespaces |
| Date: | 2017-06-06 12:59:58 |
| Message-ID: | 055f8637-10e0-3a8e-8e6c-b03bbfe6cd2b@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/6/17 03:39, Alvaro Herrera wrote:
> FWIW I don't think calling these tablespaces "temporary" is the right
> word. It's not the tablespaces that are temporary.
The SQL standard meaning of temporary is that the content goes away. It
is only in PostgreSQL that it also means that the object goes away. I
think it's OK that it can encompass both meanings.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-06-06 13:05:03 | Re: Challenges preventing us moving to 64 bit transaction id (XID)? |
| Previous Message | Bruce Momjian | 2017-06-06 12:31:26 | Re: Use of non-restart-safe storage by temp_tablespaces |