| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Repeatable Read Isolation Level "transaction start time" |
| Date: | 2024-09-24 16:16:50 |
| Message-ID: | dcf7f34d-0f5e-4674-8a26-081dfff387c4@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/24/24 09:12, Ron Johnson wrote:
> Makes sense. Never would have occurred to me to try and change the
> isolation level using a second SET TRANSACTION statement, though.
From the docs:
https://www.postgresql.org/docs/current/sql-set-transaction.html
The SET TRANSACTION command sets the characteristics of the current
transaction. It has no effect on any subsequent transactions. SET
SESSION CHARACTERISTICS sets the default transaction characteristics for
subsequent transactions of a session. These defaults can be overridden
by SET TRANSACTION for an individual transaction.
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> crustacean!
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ayush Vatsa | 2024-09-24 16:32:28 | Re: Issues with PostgreSQL Source Code Installation |
| Previous Message | Adrian Klaver | 2024-09-24 16:12:47 | Re: Issues with PostgreSQL Source Code Installation |