Thank you for the response.
"Tom Lane" <tgl@sss.pgh.pa.us> wrote:
> I'm not convinced this is really a bug, because pg_index.indexprs is not
> an expression (it's a list of expressions) and so it's not clear that
> pg_get_expr should be expected to work on it. What result were you
> expecting to get?
Yes, probably it is not a bug, but only a difference in behavior of function
pg_get_expr in versions 7.4 and 8.0.
Server 7.4 returns readable representation of index expressions that are
combined by 'AND'.
Isn't it planned to implement the same behavior of the function in 8.0?
Alexander
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Alexander Zhiltsov" <ayz@ems.ru>
Cc: <pgsql-bugs@postgresql.org>
Sent: Friday, October 01, 2004 9:20 PM
Subject: Re: [BUGS] Bug in PostrgeSQL 8.0beta
> "Alexander Zhiltsov" <ayz@ems.ru> writes:
> > Executing the following query return an error 'ERROR: unrecognized node
ty=
> > pe: 656'.
> > SELECT pg_get_expr(i.indexprs, i.indrelid) AS expr
> > FROM pg_index i
> > INNER JOIN pg_class c ON i.indrelid =3D c.oid
> > WHERE c.relname =3D 'art'
>
> I'm not convinced this is really a bug, because pg_index.indexprs is not
> an expression (it's a list of expressions) and so it's not clear that
> pg_get_expr should be expected to work on it. What result were you
> expecting to get?
>
> regards, tom lane
