Re: Multixid hindsight design - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Multixid hindsight design
Date
Msg-id CAEepm=262u+wVKxmb3y+pUM5rDBrhmLYUZWKZntDQfwCqnVfiw@mail.gmail.com
Whole thread Raw
In response to Multixid hindsight design  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: Multixid hindsight design  (Greg Stark <stark@mit.edu>)
Re: Multixid hindsight design  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Tue, May 12, 2015 at 9:20 AM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> The beauty of this would be that the TED entries can be zapped at restart,
> just like pg_subtrans, and pg_multixact before 9.3. It doesn't need to be
> WAL-logged, and we are free to change its on-disk layout even in a minor
> release.

What about prepared transactions?  They can lock rows FOR SHARE that
survive server restarts.

-- 
Thomas Munro
http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Join Filter vs. Index Cond (performance regression 9.1->9.2+/HEAD)
Next
From: Robert Haas
Date:
Subject: Re: Join Filter vs. Index Cond (performance regression 9.1->9.2+/HEAD)