| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Gavin M(dot) Roy" <gavinmroy(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_dump ignore tablespaces |
| Date: | 2007-07-15 02:56:33 |
| Message-ID: | 806.1184468193@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Gavin M. Roy" <gavinmroy(at)gmail(dot)com> writes:
> Recently I ran into an issue where restoring from pg_dump from one machine
> to another with non-matching tablespaces. The primary issue is that index
> creation will fail if the tablespace does not exist from the dump. I was
> thinking to best solution for this would be a pg_dump option such as
> --ignore-tablespaces which would not dump any tablespace related data.
We have --no-owner, so --no-tablespace doesn't seem out of line.
It's a bit late for 8.3 but no objection to adding such a feature
for 8.4.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2007-07-15 04:53:30 | Re: plpgsql and qualified variable names |
| Previous Message | Gavin M. Roy | 2007-07-15 02:30:18 | pg_dump ignore tablespaces |