Re: Repeatable Read Isolation in SQL running via background worker
От | Robert Haas |
---|---|
Тема | Re: Repeatable Read Isolation in SQL running via background worker |
Дата | |
Msg-id | CA+TgmoYprsCtSHshZWk9pJQ+khM1SdZFmr9Hrq8hcU7uhZ+orQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Repeatable Read Isolation in SQL running via background worker (Jeremy Finzel <finzelj@gmail.com>) |
Ответы |
Re: Repeatable Read Isolation in SQL running via background worker
|
Список | pgsql-hackers |
On Mon, Aug 13, 2018 at 10:52 AM, Jeremy Finzel <finzelj@gmail.com> wrote: > On Thu, Aug 9, 2018 at 4:34 PM, Jeremy Finzel <finzelj@gmail.com> wrote: >> I am using worker_spi as a model to run a SQL statement inside a >> background worker. From my browsing of the Postgres library, I believe that >> if I want repeatable read isolation level, the proper way for me to attain >> this is to add this line after StartTransactionCommand() in worker_spi_main: >> >> XactIsoLevel = XACT_REPEATABLE_READ; It's usually a good idea to only change GUCs through the GUC machinery i.e. use SetConfigOption(). Are you using StartTransactionCommand() and CommitTransactionCommand() to manage transaction boundaries? If not, maybe you should. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: