> If we do want to try to maintain the original concept, it seems that the
> OID-setting code needs to be emitted in a way that would cause it to be
> executed *first* and in *all* restore modes: schema only, data only, or
> schema+data. Not sure if that's even possible given the current design
> of the archiver, but you'd know better than I.
My only comment here is that I don't see a need to set the oid counter
for a schema-only restore because there are no oid's in the schema dump
anyway.
Now, if you then do a data-only restore, you would have a problem with
the oid counter but it seems counter-intuitive for the schema-only
restore to set the oid counter. Comments, Tom?
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026