Re: How about a proper TEMPORARY TABLESPACE? - Mailing list pgsql-hackers

From Matheus de Oliveira
Subject Re: How about a proper TEMPORARY TABLESPACE?
Date
Msg-id CAJghg4KEawjrsOim34gA0xScjj2etrhDSP=rU1phKQNWgowdhQ@mail.gmail.com
Whole thread Raw
In response to Re: How about a proper TEMPORARY TABLESPACE?  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
Responses Re: How about a proper TEMPORARY TABLESPACE?  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
Re: How about a proper TEMPORARY TABLESPACE?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
I was going to answer each message, but Fabrízio summarized everything so far really nicely. Thanks Fabrízio.

On Wed, Jun 18, 2014 at 5:25 PM, Fabrízio de Royes Mello <fabriziomello@gmail.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.
 
* throw an exception if we try ALTER the option "only_temp_relations"

I think we should postpone the ALTER option, perhaps as another patch. Wasn't that what was decided?

I'll investigate the options better before going this route. Let me work on CREATE first.

 
* add regression tests
* add documentation

And, of course, register to the next open commitfest [1] to get detailed feedback and review.

Noted. It will be on the next commitfest. Just knowing some people do want this make me more comfortable on working better.

Best regards,
--
Matheus de Oliveira
Analista de Banco de Dados
Dextra Sistemas - MPS.Br nível F!
www.dextra.com.br/postgres

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: How to change the pgsql source code and build it??
Next
From: Ian Barwick
Date:
Subject: Possible index issue on 9.5 slave