Re: Replacing pg_depend PIN entries with a fixed range check

I wrote:
> In view of the discussion at [1], there's more pressure on the OID supply
> above 10K than I'd realized. While I don't have any good ideas about
> eliminating the problem altogether, I did have a thought that would remove
> the extra buffer zone created by my first-draft patch in this thread.
> Namely, let's have genbki.pl write out its final OID assignment counter
> value in a command in the postgres.bki file, say "set_next_oid 12036".
> This would cause the bootstrap backend to set the server's OID counter to
> that value. Then the initial part of initdb's post-bootstrap processing
> could assign pinned OIDs working forward from there, with no gap. We'd
> still need a gap before FirstBootstrapObjectId (which we might as well
> rename to FirstUnpinnedObjectId), but we don't need two gaps, and so this
> patch wouldn't make things any worse than they are today.

Here's a v2 that does things that way (and is rebased up to HEAD).
I did some more documentation cleanup, too.

regards, tom lane