From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: How about a proper TEMPORARY TABLESPACE? |
Date: | 2014-06-22 14:40:17 |
Message-ID: | 20140622144017.GC16098@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Craig Ringer (craig(at)2ndquadrant(dot)com) wrote:
> 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.
Interesting idea.
> Not necessarily in the same patch, I'd just rather keep it in mind so
> any chosen design doesn't preclude adding that later.
Perhaps we need a more complex definition than just "temporary
tablespace", as in, we should have a way for users to say "this
tablespace is allowed to have objects of type X, Y, Z"? I can see a
couple of ways to do that and I don't think it'd require much in the way
of changes to the current patch...
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2014-06-22 14:55:28 | Re: review: Built-in binning functions |
Previous Message | Ali Akbar | 2014-06-22 14:32:00 | Re: [REVIEW] Re: Fix xpath() to return namespace definitions |