Matthew Kelly writes:
> I recently fell afoul of a weird edge case while writing an extension. It
> seems Postgres allows for an ambiguous column reference to oid in the where
> clause when joining to pg_roles. It just arbitrarily chooses pg_roles.oid
> and ignores the conflicting name. Exam
I recently fell afoul of a weird edge case while writing an extension. It
seems Postgres allows for an ambiguous column reference to oid in the where
clause when joining to pg_roles. It just arbitrarily chooses pg_roles.oid and
ignores the conflicting name. Example:
postgres=# CREATE TABLE