| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Jan Wieck <janwieck(at)Yahoo(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jan Wieck <janwieck(at)Yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Unhappy thoughts about pg_dump and objects inherited from template1 |
| Date: | 2000-11-09 14:36:46 |
| Message-ID: | 3.0.5.32.20001110013646.03414100@mail.rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 09:47 9/11/00 -0500, Jan Wieck wrote:
>
> To make pg_dump failsafe, we'd IMHO need to freeze all
> objects that come with template0 copying.
>
> For now we have oid's 1-16383 hardwired from the bki files.
> Some 16384-xxxxx get allocated by initdb after bootstrap, so
> we just need to bump the oid counter at the end of initdb (by
> some bootstrap interface command) to lets say 32768 and
> reject any attempt to touch an object with a lower oid.
>
I'd still like to see this number stored in the pgsql catalog somewhere
(not just header files).
----------------------------------------------------------------
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 | Jan Wieck | 2000-11-09 14:47:29 | Re: Unhappy thoughts about pg_dump and objects inherited from template1 |
| Previous Message | Jan Wieck | 2000-11-09 14:36:20 | Re: Unhappy thoughts about pg_dump and objects inherited from template1 |