On Mon, Nov 28, 2016 at 6:19 PM, Amit Kapila <amit.kapil...@gmail.com> wrote: > On Sat, Nov 26, 2016 at 9:46 PM, Tom Lane <t...@sss.pgh.pa.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
