From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: How about a proper TEMPORARY TABLESPACE? |
Date: | 2014-06-23 23:12:53 |
Message-ID: | CAFcNs+pXpgyUFfGHmHHpqw6JZRhCVN-0BEayWjfeKqPCEBWPCg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 23, 2014 at 1:17 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Wed, Jun 18, 2014 at 9:39 PM, Matheus de Oliveira
> <matioli(dot)matheus(at)gmail(dot)com> wrote:
> >> Then, to summarize Matheus must do:
> >> * use an option instead of change the syntax and catalog to indicate
that
> >> a tablespace is used to store temp objects
> >
> > Yes. I myself wasn't sure TEMPORARY syntax would be good, but I would
just
> > like to hear more about. Storing as an options seems nice to me.
>
> I kind of like the TEMPORARY syntax, by analogy with what we do for
> tables. On the other hand, this situation isn't quite analogous: the
> tablespace itself is permanent; it's only the objects inside the
> tablespace that are temporary. Hmm.
>
The suggested syntax is about "TEMP LOCATION" and not "TEMP TABLESPACE"...
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-06-23 23:19:01 | Re: autovacuum scheduling starvation and frenzy |
Previous Message | Dave McGuire | 2014-06-23 23:08:36 | Re: PostgreSQL for VAX on NetBSD/OpenBSD |