Re: BUG #17077: about three parameters in postgresql 13.3

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: BUG #17077: about three parameters in postgresql 13.3
Дата
Msg-id 202107171724.hycens5f43ho@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: BUG #17077: about three parameters in postgresql 13.3  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #17077: about three parameters in postgresql 13.3  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
On 2021-Jul-17, Tom Lane wrote:

> I've concluded that we should just document them (and am working
> on that right now).  It's certainly true that there is a use-case
> for reading them: libpq does "SHOW transaction_read_only", for
> example.  And since we've gone to the trouble of making SET of one
> of these equivalent to SET TRANSACTION, we should probably just
> document that it is.

Maybe include "SET NAMES" while at it?  It drove me crazy when I found
out that was accepted, last year.

-- 
Álvaro Herrera              Valdivia, Chile  —  https://www.EnterpriseDB.com/



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

Предыдущее
От: Andrey Borodin
Дата:
Сообщение: Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #17077: about three parameters in postgresql 13.3