Re: Subtransaction commits and Hot Standby

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Subtransaction commits and Hot Standby
Date: 2008-09-16 14:38:45
Message-ID: 1221575925.3913.1873.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


On Tue, 2008-09-16 at 17:01 +0300, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > Subtransactions cause a couple of problems for Hot Standby:
>
> Do we need to treat subtransactions any differently from normal
> transactions? Just treat all subtransactions as top-level transactions
> until commit, and mark them all as committed when you see the commit
> record for the top-level transaction.

If we do that, snapshots become infinitely sized objects though, which
then requires us to invent some way of scrolling it to disk. So having
removed the need for subtrans, I then need to reinvent something similar
(or at least something like a multitrans entry).

Perhaps it is sufficient to throw an error if the subxid cache
overflows? But I suspect that may not be acceptable...

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-09-16 14:40:09 Re: Subtransaction commits and Hot Standby
Previous Message Robert Haas 2008-09-16 14:32:34 Re: Autovacuum and Autoanalyze

Browse pgsql-patches by date

  From Date Subject
Next Message Simon Riggs 2008-09-16 14:40:09 Re: Subtransaction commits and Hot Standby
Previous Message Alvaro Herrera 2008-09-16 14:11:49 Re: Subtransaction commits and Hot Standby