From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Read Uncommitted |
Date: | 2019-12-19 12:38:19 |
Message-ID: | 2f27cf50-f580-2192-9c4a-d89bffa2bd5b@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2019-12-18 16:14, Simon Riggs wrote:
> On Wed, 18 Dec 2019 at 12:11, Konstantin Knizhnik
> <k(dot)knizhnik(at)postgrespro(dot)ru <mailto:k(dot)knizhnik(at)postgrespro(dot)ru>> wrote:
>
> As far as I understand with "read uncommitted" policy we can see two
> versions of the same tuple if it was updated by two transactions
> both of which were started before us and committed during table
> traversal by transaction with "read uncommitted" policy. Certainly
> "read uncommitted" means that we are ready to get inconsistent
> results, but is it really acceptable to multiple versions of the
> same tuple?
>
>
> "In general, read uncommitted will return inconsistent results and
> wrong answers. If you look at the changes made by a transaction
> while it continues to make changes then you may get partial results
> from queries, or you may miss index entries that haven't yet been
> written. However, if you are reading transactions that are paused
> at the end of their execution for whatever reason then you can
> see a consistent result."
>
> I think I already covered your concerns in my suggested docs for this
> feature.
Independent of the technical concerns, I don't think the SQL standard
allows the READ UNCOMMITTED level to behave in a way that violates the
logical requirements of the defined database schema. So if we wanted to
add this, we should probably name it something else.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Bernd Helmle | 2019-12-19 12:42:19 | Re: Read Uncommitted |
Previous Message | Tatsuro Yamada | 2019-12-19 12:06:50 | Re: progress report for ANALYZE |