Re: Unhappy thoughts about pg_dump and objects inherited from template1

At 22:24 9/11/00 -0500, Mark Hollomon wrote:
>On Wednesday 08 November 2000 10:15, Tom Lane wrote:
>> > At 14:04 7/11/00 -0500, Jan Wieck wrote:
>> >> FWIW,  what  about having another "template0" database, where
>> >> nobody can add user data. Initially, template0 and  template1
>> >> are identically.  CREATE DATABASE get's a new switch (used by
>> >> the pg_dump output) that tells to create it from the  vanilla
>> >> template0  DB  (generalized, so someone can setup a couple of
>> >> template<n>'s)  and  all  objects  inherited  from  template1
>> >> (those not in template0) are regularly dumped per database.
>>
>> I like that a lot.  Solves the whole problem at a stroke, and even
>> adds some extra functionality (alternate templates).
>>
>
>How does this solve the 'ALTER FUNCTION' problem?
>

I think both this and the OID-wrap problem will be permanent features until
we have a non-oid-based dump procedure. Pretty much every piece of metadata
needs some kind of 'I am a system object, don't dump me' flag. 

Relying of values of numeric OIDs is definitely clunky, but it's all we can
do at the moment.


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