| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk>, hackers(at)postgresql(dot)org |
| Subject: | Re: Current initdb broken. |
| Date: | 2000-06-11 03:41:51 |
| Message-ID: | 7953.960694911@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Um, excuse me. Any changes to the format of pg_shadow will break
> pg_dumpall, therefore this needs to be hold back until next release.
We are going to have to improve pg_dumpall sooner or later, aren't we?
Loading pg_shadow and pg_group by direct COPY just won't do.
But you're right, this patch will have to be reversed out until a
more robust pg_dumpall has been out there for at least one release.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-06-11 11:41:09 | Re: Current initdb broken. |
| Previous Message | Denis Perchine | 2000-06-10 22:59:41 | Patch for 'Not to stuff everything as files in a single directory, hash dirs' |