From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Alexander Zhiltsov" <ayz(at)ems(dot)ru> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug in PostrgeSQL 8.0beta |
Date: | 2004-10-07 20:39:23 |
Message-ID: | 23564.1097181563@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Alexander Zhiltsov" <ayz(at)ems(dot)ru> writes:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)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'.
Hmm, well that wasn't really the desired behavior either, since the index
expressions certainly aren't combined as though by AND.
I've fixed it so that 8.0 will return the expressions comma-separated,
which seems a reasonably sane behavior.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-10-07 20:47:15 | Re: BUG #1283: Queries slow down after restoring big db |
Previous Message | Tom Lane | 2004-10-07 20:29:44 | Re: BUG #1238: postgres option -Q used in src/test/bench |