Re: [HACKERS] PL/PGSQL bug in handling composite types

2012-04-25 Thread Tom Lane
Boszormenyi Zoltan writes: > we have found a way to make pl/pgsql throw an error for > a legitimate use case that works in plain SQL. The fact that it doesn't work the way you thought doesn't make it a bug. plpgsql expects an assignment "INTO row_variable" to be supplied from one select column p

Re: [HACKERS] PL/PGSQL bug in handling composite types

2012-04-24 Thread Boszormenyi Zoltan
2012-04-24 10:01 keltezéssel, Boszormenyi Zoltan írta: 2012-04-24 09:59 keltezéssel, Boszormenyi Zoltan írta: Hi, we have found a way to make pl/pgsql throw an error for a legitimate use case that works in plain SQL. Minimal test case: create table x1 (id serial primary key, d timestamptz); c

Re: [HACKERS] PL/PGSQL bug in handling composite types

2012-04-24 Thread Boszormenyi Zoltan
2012-04-24 09:59 keltezéssel, Boszormenyi Zoltan írta: Hi, we have found a way to make pl/pgsql throw an error for a legitimate use case that works in plain SQL. Minimal test case: create table x1 (id serial primary key, d timestamptz); create table x2 (id serial primary key, d timestamptz); i

[HACKERS] PL/PGSQL bug in handling composite types

2012-04-24 Thread Boszormenyi Zoltan
Hi, we have found a way to make pl/pgsql throw an error for a legitimate use case that works in plain SQL. Minimal test case: create table x1 (id serial primary key, d timestamptz); create table x2 (id serial primary key, d timestamptz); insert into x2 (d) values ('now'); create type mytype as