| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump bug fixing |
| Date: | 2004-07-20 01:20:35 |
| Message-ID: | 40FC7363.2090905@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> We already are to some extent, since pg_dump will dump its comment and
> privileges, which it would not do for any other predefined object.
> I think this is actually an implementation artifact rather than
> something that was explicitly intended at the time, but since no one
> has complained about it, it's probably a good thing ;-)
Does that mean your in favour of dumping a DROP SCHEMA public; command
if they have dropped their public schema? It's definitely not worth
doing it for any other "system" object due to upwards compatibility of
the dump files...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-07-20 01:22:42 | Re: [HACKERS] Point in Time Recovery |
| Previous Message | Mark Kirkwood | 2004-07-20 00:48:50 | Re: PITR COPY Failure (was Point in Time Recovery) |