| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Philip Warner <pjw(at)rhyme(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tablespace and sequences? |
| Date: | 2004-08-20 04:27:04 |
| Message-ID: | 16167.1092976024@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-cygwin pgsql-hackers pgsql-hackers-win32 |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
>> One point here is the handling of index tablespaces. I added TABLESPACE
>> as part of "pg_get_indexdef" output, but we'd need a different solution
>> if we want to go down this path.
> Another parameter to pg_get_indexdef() :(
Actually I think we'd just revert the ruleutils.c change that showed
TABLESPACE in pg_get_indexdef. The real question is to be sure that
pg_dump could get along without it. If Philip wants to fix pg_dump,
I'm content to just stay out of his way ;-)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2004-08-20 04:37:24 | Re: tablespace and sequences? |
| Previous Message | Christopher Kings-Lynne | 2004-08-20 04:24:18 | Re: tablespace and sequences? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2004-08-20 04:29:14 | Re: postgres uptime |
| Previous Message | Marc G. Fournier | 2004-08-20 04:25:59 | Re: postgres uptime |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2004-08-20 04:37:24 | Re: tablespace and sequences? |
| Previous Message | Christopher Kings-Lynne | 2004-08-20 04:24:18 | Re: tablespace and sequences? |