From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Denis Perchine <dyp(at)perchine(dot)com> |
Subject: | Re: Last builtin OID? |
Date: | 2000-10-22 01:52:11 |
Message-ID: | 3.0.5.32.20001022115211.025b4100@mail.rhyme.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 16:00 21/10/00 +0200, Peter Eisentraut wrote:
>
>Perhaps you could move the CREATE TRIGGER pg_sync_pg_pwd (or something
>else) to the very end to get a more predictable starting point.
>
Unfortunately, this is the sort of thing that caused the current problem
(ie. assuming that a certain item of metadata will remain 'at the end').
What pg_dump needs is 'the oid of that the first thing created in a new DB
will have'. Would there be a simple way of adding a
variable/attribute/whatever to template1? Or adding something to the code
for 'Create Database' that sets a global variable that pg_dump can retreieve?
----------------------------------------------------------------
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 |/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-10-22 01:56:53 | Re: Last builtin OID? |
Previous Message | Tom Lane | 2000-10-22 01:40:56 | Re: Last builtin OID? |