Re: alter table tablename add column - breaks pl/pgsql function returns tablename
От | Palle Girgensohn |
---|---|
Тема | Re: alter table tablename add column - breaks pl/pgsql function returns tablename |
Дата | |
Msg-id | 4617A076-4084-4CB0-96E7-C09FA9795EDE@pingpong.net обсуждение исходный текст |
Ответ на | Re: alter table tablename add column - breaks pl/pgsql function returns tablename (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: alter table tablename add column - breaks pl/pgsql function returns tablename
|
Список | pgsql-hackers |
5 nov 2012 kl. 22:23 skrev Tom Lane <tgl@sss.pgh.pa.us>: > Palle Girgensohn <girgen@pingpong.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 Ah, sorry. Other sessions get the error immediately as well though. Would input parameters matter, or is it just the returntype? I'll see if I can find a test case that breaks permanently, but I'm probably mistaken about that bit then.
В списке pgsql-hackers по дате отправления: