Re: ECPG bug fix: DECALRE STATEMENT and DEALLOCATE, DESCRIBE

Поиск
Список
Период
Сортировка
От Michael Meskes
Тема Re: ECPG bug fix: DECALRE STATEMENT and DEALLOCATE, DESCRIBE
Дата
Msg-id 716c23b239ff3f11ea1a574e81683d9d8bd58d8c.camel@postgresql.org
обсуждение исходный текст
Ответ на Re: ECPG bug fix: DECALRE STATEMENT and DEALLOCATE, DESCRIBE  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: ECPG bug fix: DECALRE STATEMENT and DEALLOCATE, DESCRIBE
Список pgsql-hackers
> Sure, DECLARE does not matter as it is new.  However, please note
> that
> the specific point I was trying to make with my link [2] from
> upthread
> is related to the use of cached connection names with DEALLOCATE, as
> of this line in the new test declare.pgc:
>     EXEC SQL DEALLOCATE PREPARE stmt_2;
>
> And DEALLOCATE is far from being new.

I'm not sure I understand. Any usage of DECLARE STATEMENT makes the
file need the current version of ecpg anyway. On the other hand
DEALLOCATE did not change its behavior if no DECLARE STATEMENT was
issued, or what did I miss?

Michael
--
Michael Meskes
Michael at Fam-Meskes dot De
Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Melanie Plageman
Дата:
Сообщение: Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: Use extended statistics to estimate (Var op Var) clauses