Re: Multixid hindsight design - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Multixid hindsight design
Date
Msg-id CANP8+j+mg5qSFEQ=WsBNRaqV7KXWfb1rO3iV3BE1w1MJtyphCw@mail.gmail.com
Whole thread Raw
In response to Re: Multixid hindsight design  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: Multixid hindsight design  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 1 June 2015 at 20:53, Thomas Munro <thomas.munro@enterprisedb.com> wrote:
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.

Interesting comment. I'm not aware that we do.

If we do support row locking that survives server restart, how did it work before 9.3? 

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: "Shulgin, Oleksandr"
Date:
Subject: Re: Handle PGRES_COPY_BOTH in psql for logical replication?
Next
From: Shigeru HANADA
Date:
Subject: Re: [idea] more aggressive join pushdown on postgres_fdw