| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How about a proper TEMPORARY TABLESPACE? |
| Date: | 2014-06-22 05:35:15 |
| Message-ID: | 53A66B13.2050903@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/18/2014 08:00 PM, Stephen Frost wrote:
> PG would need to enforce that it's only used for temporary objects
> as well, of course.. Or at least, that was my thinking on this.
A way to put UNLOGGED objects in such a space and have them recovered
if they vanish would also be valuable, IMO.
Not necessarily in the same patch, I'd just rather keep it in mind so
any chosen design doesn't preclude adding that later.
- --
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTpmsOAAoJELBXNkqjr+S2SNUH/A1zor2WUbQg3PTyD+6wyxlM
v6iMpH9zaeMWYyavIHM9N8a+h7hl9ajKDPMuK0vYLMs83W88LXI4T/t1iJlgZ3Po
WhyjjdNonChn5v1NEJncb4KgqmRQxyWY43rzgEgofSJQgjFbo8UAwoD8Xa32ghDu
4dx2ijYqYsx/hC1Gb1u/HbQ9rX+OkTA0DwljdUgPqPorW/mn5RVscz9Qo5p/W+XH
tdvpu9CKRi4AFPkshZOij+Mu3My863K1+k7sHUpRcsRGJT/AIO1V0wUQE2PuWTAV
5InU5vw/1C6CsYpH4v++XvpeTOnQ4QrMnllh99UTxV91UXN+jx/ENv1SYhBfYGE=
=JGYF
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2014-06-22 05:37:52 | Re: How about a proper TEMPORARY TABLESPACE? |
| Previous Message | Pavel Stehule | 2014-06-22 05:04:07 | Re: proposal: new long psql parameter --on-error-stop |