Re: Read Uncommitted - Mailing list pgsql-hackers

From Bernd Helmle
Subject Re: Read Uncommitted
Date
Msg-id c6c4e23b84db8ef211318021a4995d8089f264d0.camel@oopsware.de
Whole thread Raw
In response to Re: Read Uncommitted  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Read Uncommitted  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Am Donnerstag, den 19.12.2019, 00:13 +0000 schrieb Simon Riggs:
> So the consensus is for a more-specifically named facility.
> 
> I was aiming for something that would allow general SELECTs to run
> with a
> snapshot that can see uncommitted xacts, so making it a SRF wouldn't
> really
> allow that.

There's pg_dirtyread() [1] around for some while, implementing a SRF
for debugging usage on in normal circumstances disappeared data. Its
nice to not have worrying about anything when you faced with such kind
of problems, but for such use cases i think a SRF serves quite well.

[1] https://github.com/df7cb/pg_dirtyread


    Bernd





pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Read Uncommitted
Next
From: Simon Riggs
Date:
Subject: Re: Read Uncommitted