Re: WITH RECURSIVE ... CYCLE in vanilla SQL: issues with arrays of rows

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WITH RECURSIVE ... CYCLE in vanilla SQL: issues with arrays of rows
Date: 2008-10-13 13:10:25
Message-ID: 9941.1223903425@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:
> The record ops work as promised. IMO this patch stands in its own
> merits with or without the CTE changes. I played around with it and
> noticed a couple of oddities:

> select foo = foo from foo; --works
> but

> select distinct foo from foo; --yields
> ERROR: could not identify an equality operator for type foo
> also,

> select foo from foo order by foo;
> ERROR: could not identify an ordering operator for type foo

Yeah, these are because of the incomplete handling of named record
types. I'm not sure how far we want to go in that direction.

> postgres=# create index foo_idx on foo((foo));
> ERROR: cache lookup failed for type 0

Hm, that's not good ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zdenek Kotala 2008-10-13 13:39:58 Re: [PATCH] Extending pg_class info + more flexible TOAST chunk size
Previous Message Tom Lane 2008-10-13 13:06:03 Re: out-of-date comment in auto-generated oidjoins.sql