BUG #14836: Is there an option to change and run isolation level only for a single statement as in DB2

From: aistrong(dot)hs(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Cc: aistrong(dot)hs(at)gmail(dot)com
Subject: BUG #14836: Is there an option to change and run isolation level only for a single statement as in DB2
Date: 2017-09-29 09:28:41
Message-ID: 20170929092841.28566.78613@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 14836
Logged by: Isaac Arasavalli
Email address: aistrong(dot)hs(at)gmail(dot)com
PostgreSQL version: 9.3.0
Operating system: Any
Description:

If a transaction is started and some isolation level li repeatable read is
set.
Then if lock will be set.
And I want to read uncommitted rows.
How can I?
In db2 we can run a statement like
SELECT * FROM X WITH CS;
meaning cursor stability read uncommitted.

Is this available in postgres?
Or any turn around work can be done. Without making other transaction give
error like couldnt serialize or aborted.

Please give me little detailed solution

Browse pgsql-bugs by date

  From Date Subject
Next Message gkostov79 2017-09-29 09:52:06 BUG #14837: pglogical subscription strange behavior
Previous Message Tom Lane 2017-09-28 17:37:45 Re: BUG #14834: quote_literal and composite types, different behaviour between sql and plpgsql