Re: alter table tablename add column - breaks pl/pgsql function returns tablename

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Palle Girgensohn <girgen(at)pingpong(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Amit kapila <amit(dot)kapila(at)huawei(dot)com>, Palle Girgensohn <girgen(at)freebsd(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: alter table tablename add column - breaks pl/pgsql function returns tablename
Date: 2012-11-05 21:23:43
Message-ID: 25105.1352150623@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Palle Girgensohn <girgen(at)pingpong(dot)net> writes:
> Please note that this problem does not go away by disconnecting and reconnecting, and other sessions get the error immediately, so the claim that it is bound to a session is false.

Huh? The test case you provided certainly doesn't exhibit any such
behavior. I get

regression=# SELECT * FROM test_func();
ERROR: wrong record type supplied in RETURN NEXT
CONTEXT: PL/pgSQL function test_func() line 6 at RETURN NEXT
regression=# \c -
You are now connected to database "regression" as user "postgres".
regression=# SELECT * FROM test_func();
id | foo
----+-----
1 |
(1 row)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2012-11-05 21:23:58 Re: Pg_upgrade speed for many tables
Previous Message Bruce Momjian 2012-11-05 21:22:59 Re: Pg_upgrade speed for many tables