Re: Bug in pg_dump/restore -o

At 23:08 17/01/02 -0500, Tom Lane wrote:
>AFAICS, the only way to work around this is to be certain that no other
>archive TOC entries will be emitted between the schema and data for
>pgdump_oids (if these are separate TOC entries).  I'd prefer a solution
>in which they are only one TOC entry, since that seems less likely to
>break in the future...

A sigle TOC entry, with both CREATE and COPY run at the start no matter
what kind of dump/restore, seems like the solution. I'll look into it.

----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 0500 83 82 82         |                 ___________ |
Http://www.rhyme.com.au          |                /           \|                                |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/