Philip Warner <pjw@rhyme.com.au> writes:
> I am wondering if anyone can see an immediate problem in creating a function:
> heap_create_oid
> which is just like heap_create, but takes an oid arg. This oid (assuming
> it's free) would be used to create the object.
How exactly do you propose to determine that the OID is free?
If the requested OID is greater than the current OID counter, how
will you prevent a future conflict?
There's no inherent problem in forcing a particular choice of OID;
initdb does it on every run. The trick is to avoid a conflict of
OID assignments.
My own feeling is that the current LO setup is fundamentally flawed
by its reliance on specific OID values, and that the right answer is
to find a way to avoid that. contrib/lo might provide some food for
thought here (although it's clearly not the whole answer either).
regards, tom lane
