Re: [HACKERS] Document bug regarding read only transactions
От | Michael Paquier |
---|---|
Тема | Re: [HACKERS] Document bug regarding read only transactions |
Дата | |
Msg-id | CAB7nPqS_pH=+X7Dm4JK+6242j1DKW88+0S62ggA2sCPA969GSg@mail.gmail.com обсуждение исходный текст |
Ответ на | [HACKERS] Document bug regarding read only transactions (Tatsuo Ishii <ishii@sraoss.co.jp>) |
Ответы |
Re: [HACKERS] Document bug regarding read only transactions
|
Список | pgsql-hackers |
On Wed, Jun 14, 2017 at 11:08 AM, Tatsuo Ishii <ishii@sraoss.co.jp> wrote: > <para> > In normal operation, <quote>read-only</> transactions are allowed to > - update sequences and to use <command>LISTEN</>, <command>UNLISTEN</>, and > + use <command>LISTEN</>, <command>UNLISTEN</>, and > <command>NOTIFY</>, so Hot Standby sessions operate under slightly tighter > restrictions than ordinary read-only sessions. It is possible that some > of these restrictions might be loosened in a future release. Your modification does not look completely correct to me either. Temporary sequences can be updated in read-only transactions. I think that the page listing the sequence-related functions should as well mention those restrictions for nextval() and setval(). -- Michael
В списке pgsql-hackers по дате отправления: