Re: (PATCH) Adding CORRESPONDING (NULL error) - Mailing list pgsql-hackers

From Erik Rijkers
Subject Re: (PATCH) Adding CORRESPONDING (NULL error)
Date
Msg-id cc632458cd3518d43c164ec4ea87aff4.squirrel@webmail.xs4all.nl
Whole thread Raw
In response to Re: (PATCH) Adding CORRESPONDING to Set Operations  (Kerem Kat <keremkat@gmail.com>)
Responses Re: (PATCH) Adding CORRESPONDING (NULL error)  (Kerem Kat <keremkat@gmail.com>)
List pgsql-hackers
(pgsql 9.2devel (25 oct) with your latest CORRESPONDING patch;
linux x86_64 GNU/Linux 2.6.18-274.3.1.el5)

Hi,

here is another peculiarity, which I think is a bug:

-- first without CORRESPONDING:

$ psql -Xaf null.sql           select 1 a   , 2 b
union all           select null a, 4 b ;a | b
---+---1 | 2  | 4
(2 rows)

-- then with CORRESPONDING:
           select 1 a   , 2 b
union all
corresponding           select null a, 4 b ;
psql:null.sql:9: ERROR:  failed to find conversion function from unknown to integer


If the null value is in a table column the error does not occur:

drop table if exists t1; create table t1 (a int, b int); insert into t1 values (1,2);
drop table if exists t2; create table t2 (a int, b int); insert into t2 values (null,2);               select a,b from
t1
union all
corresponding               select a,b from t2 ;a | b
---+---1 | 2  | 2
(2 rows)


I'm not sure it is actually a bug; but it seems an unneccessary error.


thanks,

Erik Rijkers



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: isolationtester and invalid permutations
Next
From: Simon Riggs
Date:
Subject: Hot Standby startup with overflowed snapshots