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

Re: Possible SELECT bug in 7.0.2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jean-Louis Leroy <jll(at)tangram-persistence(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Possible SELECT bug in 7.0.2
Date: 2000-12-30 05:33:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Jean-Louis Leroy <jll(at)tangram-persistence(dot)org> writes:
> Both result sets seem wrong; even more bizarre, adding a column in the
> projection affects the result set.
> In addition, Tangram's test suite runs flawlessly against Sybase,
> Mysql, Oracle and Postgres 6.4.2.

Seems fishy, but there's not enough info here to diagnose the problem.

Does EXPLAIN show nested mergejoin plans for the failing queries?
If so, that's a known bug that is fixed in 7.0.3.  If not, I'd like
to see enough info to reproduce the problem --- a pg_dump database
dump and a procedure for reproducing the error after reload would
do nicely ...

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tatsuo IshiiDate: 2000-12-30 07:41:11
Subject: Re: Beta1 starting date?
Previous:From: Tatsuo IshiiDate: 2000-12-30 03:07:59
Subject: Re: [HACKERS] About PQsetClientEncoding(),"SET NAMES",and "SET CLIENT_ENCODING"

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