| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: USING INDEX TABLESPACE |
| Date: | 2004-08-02 04:21:20 |
| Message-ID: | 699.1091420480@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> The attached patch allows the specification of the tablespace the index
> is to be created in for unique and pk constraints. It also fixes the
> dumping of such constraints so that they are restored into the correct
> tablespace, after they have been moved with SET TABLESPACE. This is
> currently an outstanding pg_dump bug.
Applied. I also added some code to ruleutils.c to make
pg_get_constraintdef output the USING INDEX TABLESPACE clause at need.
We might want to think about getting pg_dump to rely more on
pg_get_constraintdef and friends, instead of native wit ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-08-02 04:33:37 | Re: USING INDEX TABLESPACE |
| Previous Message | Zhenbang Wei | 2004-08-02 03:54:40 | Traditional Chinese postgres-zh_TW.po for 7.5 |