Re: [PATCH] 2PC state files on shared memory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, heikki(dot)linnakangas(at)enterprisedb(dot)com
Subject: Re: [PATCH] 2PC state files on shared memory
Date: 2009-08-08 00:11:31
Message-ID: 3680.1249690291@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> Based on an idea of Heikki Linnakangas, here is a patch in order to improve
> 2PC
> by sending the state files of prepared transactions to shared memory instead
> of disk.

I don't understand how this can possibly work. The entire point of
2PC is that the state file is guaranteed to be on disk so it will
survive a crash. What good is it if it's in shared memory?

Quite aside from that, the fixed size of shared memory makes this seem
pretty impractical.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Herodotos Herodotou 2009-08-08 00:34:06 Re: Join optimization for inheritance tables
Previous Message Andrew Dunstan 2009-08-07 23:28:14 Re: Alpha releases: How to tag