Skip site navigation (1) Skip section navigation (2)

Re: Bug in PostrgeSQL 8.0beta

From: "Alexander Zhiltsov" <ayz(at)ems(dot)ru>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Bug in PostrgeSQL 8.0beta
Date: 2004-10-08 05:35:57
Message-ID: 016301c4acf8$afa94730$2742a8c0@office.ems.chel.su (view raw or flat)
Thread:
Lists: pgsql-bugs
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I've fixed it so that 8.0 will return the expressions comma-separated,
> which seems a reasonably sane behavior.

Thank you.


Alexander

----- Original Message -----
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>
Sent: Friday, October 08, 2004 2:39 AM
Subject: Re: [BUGS] Bug in PostrgeSQL 8.0beta


> "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


In response to

pgsql-bugs by date

Next:From: MasonDate: 2004-10-08 08:45:29
Subject: COPY bug on 7.3.4 whe copying lots of data
Previous:From: ffffceffffac ffffbdffffaaDate: 2004-10-08 04:45:10
Subject: PANIC: ERRORDATA_STACK_SIZE exceeded

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group