Re: (PATCH) Adding CORRESPONDING (NULL error)

From: "Erik Rijkers" <er(at)xs4all(dot)nl>
To: "Kerem Kat" <keremkat(at)gmail(dot)com>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: (PATCH) Adding CORRESPONDING (NULL error)
Date: 2011-10-27 12:45:24
Message-ID: cc632458cd3518d43c164ec4ea87aff4.squirrel@webmail.xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2011-10-27 13:26:00 Hot Standby startup with overflowed snapshots
Previous Message Robert Haas 2011-10-27 12:09:19 Re: isolationtester and invalid permutations