| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Mark Dilger <hornschnorter(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Read Uncommitted |
| Date: | 2019-12-18 21:24:50 |
| Message-ID: | CA+TgmoZdJ8P078KCh06xSUd8E8aFC=0rgU_yXMm_KC8TtpBwjg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 18, 2019 at 2:29 PM Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> I agree that if we have a user-exposed READ UNCOMMITTED isolation level,
> it shouldn't be just a recovery tool. For a recovery tool, I think a
> set-returning function as part of contrib/pageinspect, for example,
> would be more appropriate. Then it could also try to be more defensive
> against corrupt pages, and be superuser-only.
+1.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2019-12-18 22:05:11 | Read Uncommitted regression test coverage |
| Previous Message | Robert Haas | 2019-12-18 21:24:03 | Re: backup manifests |