From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Amos Bird <amosbird(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: make default TABLESPACE belong to target table. |
Date: | 2016-11-29 11:19:55 |
Message-ID: | CAA4eK1LA11p+bew7H1geWtPHCmAz8=7YGXQRpQ6wLJHRVv+Nzg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Nov 28, 2016 at 6:19 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Sat, Nov 26, 2016 at 9:46 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>
>> If we just did points 1 and 2 then a bool GUC would suffice. I'm
>> not sure how to handle all three cases cleanly. We could define
>> default_index_tablespace as empty to get point 1 or a tablespace
>> name to get point 3, but that leaves us having to use some magic
>> string for point 2, which would be messy --- what if it conflicts
>> with someone's choice of a tablespace name?
>>
>
> Yeah, I think coming with a clean way to handle all three might be
> messy. How about if just handle 2 and 3?
>
Or maybe just 1 and 2 with a bool GUC. Another point to think in this
regard is what if tomorrow somebody requests something similar for
Create Materialized View? Isn't it better to introduce a GUC
default_tablespace_parent or default_parent_tablespace?
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2016-11-29 11:24:27 | Re: Declarative partitioning - another take |
Previous Message | Albe Laurenz | 2016-11-29 11:10:25 | Re: Parallel execution and prepared statements |