From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Bug in pg_dump/restore -o |
Date: | 2002-01-18 06:28:21 |
Message-ID: | 3.0.5.32.20020118172821.02015a90@mail.rhyme.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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.
Attachment | Content-Type | Size |
---|---|---|
pg_dump_maxoid_diff.gz | application/octet-stream | 3.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-01-18 06:31:42 | Geometric types (was Re: [PATCHES] guc) |
Previous Message | Joe Conway | 2002-01-18 06:16:34 | Re: tuptoaster.c must *not* use SnapshotAny |