Re: Details for planned template0/template1 change - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Details for planned template0/template1 change
Date
Msg-id 11807.974262034@sss.pgh.pa.us
Whole thread Raw
In response to Re: Details for planned template0/template1 change  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: Details for planned template0/template1 change  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
Philip Warner <pjw@rhyme.com.au> writes:
> I still think that pg_dump needs to use the lastoid in template0 - did you
> fail to implement this because you disagree, or because you think it should
> use the current db lastsysoid?

I think it should use the current DB's lastsysoid, which is how I
left the code.

Given the present backend coding, all the DBs in an installation will
have the same lastsysoid as template0 anyway, barring manual
intervention.  The only reason they'd be different is if the dbadmin
deliberately changed one in order to prevent pg_dump from dumping part
of that database.  Now offhand I don't see a good *reason* for someone
to do that, but I don't see any reason to make it impossible to do it,
either.
        regards, tom lane


pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: IRC?
Next
From: Tom Lane
Date:
Subject: Re: Re: UUNET socket-file-location patch