From: | Jeremy Finzel <finzelj(at)gmail(dot)com> |
---|---|
To: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Repeatable Read Isolation in SQL running via background worker |
Date: | 2018-08-13 14:52:14 |
Message-ID: | CAMa1XUhrn5PxPSo9M3NPE7dQPyyqCqeC7NV=aTstYFct1_TSKQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 9, 2018 at 4:34 PM, Jeremy Finzel <finzelj(at)gmail(dot)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;
>
> Or - am I mistaken? Does PushActiveSnapshot already ensure I will get the
> same snapshot of the data within this transaction?
>
> Can anyone help me if this is accurate or if there are any other gotchas I
> should be aware of?
>
> The SQL statement will be run every minute for example, and each time with
> this isolation level. At least, that is my goal.
>
> Any help is much appreciated.
>
> Thanks,
> Jeremy
>
It seems to be working. If anyone could provide any feedback though I
would be very appreciative.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-08-13 14:54:05 | Re: logical decoding / rewrite map vs. maxAllocatedDescs |
Previous Message | Alvaro Herrera | 2018-08-13 14:50:41 | Re: logical decoding / rewrite map vs. maxAllocatedDescs |