David Johnston wrote
> Or feel free to peruse the release notes for 9.2, this behavior change
> should be documented if intentional.
Reading said notes it appears that the "returns NULL" behavior compensates
for a concurrent DROP of an existing/known OID. Since your issue is that
the object was never physically present, and thus did not have an OID, so
the attempt to obtain an OID failed and resulted in an error.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Seems-like-bug-in-9-1-3-need-to-confirm-tp5784296p5784304.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.