Re: Bug in pg_dump/restore -o - Mailing list pgsql-hackers

From Philip Warner
Subject Re: Bug in pg_dump/restore -o
Date
Msg-id 3.0.5.32.20020118172821.02015a90@mail.rhyme.com.au
Whole thread Raw
In response to Re: Bug in pg_dump/restore -o  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
At 23:36 17/01/02 -0500, Bruce Momjian wrote:
>
>Yes, that was my proposal.  I was consindering a case where the load the
>schema just to populate a fresh database that is to be used by the
>application.  In such cases, setting the oid makes little sense.
>

Here's a patch that seems to do the trick. It may seem large, but it is
primarily a reorganization of existing code in pg_backup_db.c to make the
code a little clearer and to facilitate the swapping around of some loops.

Let me know how you go...

Bye for now,

Philip.


----------------------------------------------------------------
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   |/
Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Bug in pg_dump/restore -o
Next
From: Joe Conway
Date:
Subject: Re: tuptoaster.c must *not* use SnapshotAny