Re: Signature change for SPI_cursor_open

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Signature change for SPI_cursor_open
Дата
Msg-id 11383.1099166019@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Signature change for SPI_cursor_open  (Thomas Hallgren <thhal@mailblocks.com>)
Список pgsql-hackers
Thomas Hallgren <thhal@mailblocks.com> writes:
> Ok, now I understand. Thanks for the explanation. I guess that if 
> read_only is set to true and an attempt is made to execute a plan that 
> has side effect, that will cause an ERROR?

Right, it'll bounce anything except a SELECT query.  (This test is not
watertight; consider SELECT nextval() ... but on the other hand that's a
non-transactional operation that does not care about snapshots anyway.)
        regards, tom lane


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

Предыдущее
От: Thomas Hallgren
Дата:
Сообщение: Re: Signature change for SPI_cursor_open
Следующее
От: David Fetter
Дата:
Сообщение: array_to_column function