Re: [BUGS] fix: plpgsql: return query and dropped columns problem

2009-07-20 Thread Pavel Stehule
2009/7/21 Jaime Casanova : > On Mon, Jul 20, 2009 at 11:34 AM, Jaime > Casanova wrote: >> On Mon, Jul 20, 2009 at 10:09 AM, Alvaro >>> >>> Getting rid of the check on natts was "ungood" ... it needs to compare >>> the number of undropped columns of both tupdescs. >>> >> >> ah! ok, i see... i will m

Re: [BUGS] Bug 4906 -- Left join of subselect incorrect

2009-07-20 Thread Tom Lane
Mathieu Fenniak writes: > After running the attached setup.sql.gz SQL script on a PostgreSQL > 8.4.0 database, the following two queries which should be logically > identical return different results. As far as I can tell from the > query analysis, the LEFT JOIN on query A is happening afte

Re: [BUGS] BUG #4929: Corrupted pg_class, possibly truncate/rollback related

2009-07-20 Thread Tom Lane
Andrew Gierth writes: > However I'm wondering if another 8.3.4 fix, the RecentGlobalXmin one, > could be relevant here? > http://archives.postgresql.org/pgsql-committers/2008-09/msg00105.php > (I'm not seeing how it would be, but... note that the xids have got > to the point that they'd appear to

Re: [BUGS] BUG #4929: Corrupted pg_class, possibly truncate/rollback related

2009-07-20 Thread Andrew Gierth
> "Tom" == Tom Lane writes: > "Robert Treat" writes: >> PostgreSQL version: 8.3.1 >> Description:Corrupted pg_class, possibly truncate/rollback related Tom> FWIW, there is a bug fix in 8.3.4 addressing possible HOT-chain Tom> corruption after a REINDEX of pg_class. Not sure if

Re: [BUGS] BUG #4929: Corrupted pg_class, possibly truncate/rollback related

2009-07-20 Thread Tom Lane
"Robert Treat" writes: > PostgreSQL version: 8.3.1 > Description:Corrupted pg_class, possibly truncate/rollback related FWIW, there is a bug fix in 8.3.4 addressing possible HOT-chain corruption after a REINDEX of pg_class. Not sure if that could've been the issue here.

Re: [BUGS] Bug 4906 -- Left join of subselect incorrect

2009-07-20 Thread Tom Lane
Mathieu Fenniak writes: > After running the attached setup.sql.gz SQL script on a PostgreSQL > 8.4.0 database, the following two queries which should be logically > identical return different results. As far as I can tell from the > query analysis, the LEFT JOIN on query A is happening afte

Re: [BUGS] BUG #4929: Corrupted pg_class, possibly truncate/rollback related

2009-07-20 Thread Andrew Gierth
> "Robert" == "Robert Treat" writes: Robert> Bug reference: 4929 Robert> Logged by: Robert Treat Robert> Email address: xzi...@users.sourceforge.net Robert> PostgreSQL version: 8.3.1 pe2=# select xmin, xmax, cmin, cmax, ctid, oid, relnamespace, relname, reltype, relow

[BUGS] BUG #4929: Corrupted pg_class, possibly truncate/rollback related

2009-07-20 Thread Robert Treat
The following bug has been logged online: Bug reference: 4929 Logged by: Robert Treat Email address: xzi...@users.sourceforge.net PostgreSQL version: 8.3.1 Operating system: Linux 2.6.18-53.1.14.el5 #1 SMP x86_64 GNU/Linux (Centos) Description:Corrupted pg_class, poss

Re: [BUGS] fix: plpgsql: return query and dropped columns problem

2009-07-20 Thread Jaime Casanova
On Mon, Jul 20, 2009 at 11:34 AM, Jaime Casanova wrote: > On Mon, Jul 20, 2009 at 10:09 AM, Alvaro >> >> Getting rid of the check on natts was "ungood" ... it needs to compare >> the number of undropped columns of both tupdescs. >> > > ah! ok, i see... i will mark the patch as "waiting on author" a

[BUGS] Bug 4906 -- Left join of subselect incorrect

2009-07-20 Thread Mathieu Fenniak
Hi all, After running the attached setup.sql.gz SQL script on a PostgreSQL 8.4.0 database, the following two queries which should be logically identical return different results. As far as I can tell from the query analysis, the LEFT JOIN on query A is happening after "ee.projectid = pc.

Re: [BUGS] fix: plpgsql: return query and dropped columns problem

2009-07-20 Thread Jaime Casanova
On Mon, Jul 20, 2009 at 10:09 AM, Alvaro Herrera wrote: > Tom Lane escribió: >> Jaime Casanova writes: >> > this one applies, compiles and it actually fixes the bug... >> >> And introduces a bunch of new ones.  Surely you don't think that version >> of compatible_tupdesc() is good enough. > > Gett

Re: [BUGS] fix: plpgsql: return query and dropped columns problem

2009-07-20 Thread Alvaro Herrera
Tom Lane escribió: > Jaime Casanova writes: > > this one applies, compiles and it actually fixes the bug... > > And introduces a bunch of new ones. Surely you don't think that version > of compatible_tupdesc() is good enough. Getting rid of the check on natts was "ungood" ... it needs to compar

Re: [BUGS] fix: plpgsql: return query and dropped columns problem

2009-07-20 Thread Jaime Casanova
On Mon, Jul 20, 2009 at 9:55 AM, Tom Lane wrote: > Jaime Casanova writes: >> this one applies, compiles and it actually fixes the bug... > > And introduces a bunch of new ones.  Surely you don't think that version > of compatible_tupdesc() is good enough. > i guess you're talking about my adapted

Re: [BUGS] fix: plpgsql: return query and dropped columns problem

2009-07-20 Thread Tom Lane
Jaime Casanova writes: > this one applies, compiles and it actually fixes the bug... And introduces a bunch of new ones. Surely you don't think that version of compatible_tupdesc() is good enough. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgr

Re: [BUGS] fix: plpgsql: return query and dropped columns problem

2009-07-20 Thread Jaime Casanova
On Sun, Jul 12, 2009 at 10:28 AM, Pavel Stehule wrote: > Hello > > there is fix for bug Re: [BUGS] BUG #4907: stored procedures and changed > tables > this one applies, compiles and it actually fixes the bug... it should be backpatched until 8.3... but applies cleanly only until 8.4 (what a surpr