| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: getting rid of SnapshotNow |
| Date: | 2013-07-19 16:51:02 |
| Message-ID: | 20130719165102.GB4130@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-odbc |
Robert Haas escribió:
> On Fri, Jul 19, 2013 at 12:29 PM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
> > I think seeing otherwise invisible rows is useful in pgrowlocks. It
> > helps observe the effects on tuples written by concurrent transactions
> > during experimentation. But then, maybe this functionality belongs in
> > pageinspect instead.
>
> It does seem like it should be useful, at least as an option. But I
> feel like changing that ought to be separate from getting rid of
> SnapshotNow. It seems like too big of a behavior change to pass off
> as a harmless tweak.
Agreed.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2013-07-19 16:58:10 | FKey not enforced resulting in broken Dump/Reload |
| Previous Message | Robert Haas | 2013-07-19 16:47:23 | Re: LOCK TABLE Permissions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-07-19 17:13:37 | Re: [HACKERS] getting rid of SnapshotNow |
| Previous Message | Robert Haas | 2013-07-19 16:46:06 | Re: getting rid of SnapshotNow |