Re: Repeatable Read Isolation in SQL running via background worker - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Repeatable Read Isolation in SQL running via background worker
Date
Msg-id CA+TgmoYprsCtSHshZWk9pJQ+khM1SdZFmr9Hrq8hcU7uhZ+orQ@mail.gmail.com
Whole thread Raw
In response to Re: Repeatable Read Isolation in SQL running via background worker  (Jeremy Finzel <finzelj@gmail.com>)
Responses Re: Repeatable Read Isolation in SQL running via background worker
List 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 by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Improve behavior of concurrent ANALYZE/VACUUM
Next
From: Michael Paquier
Date:
Subject: Re: Temporary tables prevent autovacuum, leading to XID wraparound