Re: oids vs composite types, in cvs head

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: andrew(at)supernews(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: oids vs composite types, in cvs head
Date: 2005-07-06 02:55:38
Message-ID: 21067.1120618538@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew - Supernews <andrew+nonews(at)supernews(dot)com> writes:
> This works on 7.4 and 8.0 but not in cvs head:
> create function foo(pg_type) returns oid as 'select $1.oid' language sql;
> ERROR: column "oid" not found in data type pg_type
> CONTEXT: SQL function "foo"

> Is this intentional, or did the no-oids-by-default changes cut too deep?

Hmm ... offhand, I'd say that if it worked in 8.0 it was only by chance.
In general a tuple that matches the signature of a pg_type row need not
contain an OID. Still it does seem that we have broken some specific
cases that used to work. Anyone want to dig into the details?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-07-06 03:07:42 Re: timezone changes break windows and cygwin
Previous Message Tom Lane 2005-07-06 02:38:36 Re: [HACKERS] Dbsize backend integration