Re: Deriving Recovery Snapshots

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Deriving Recovery Snapshots
Date: 2008-10-23 05:40:48
Message-ID: 49000E60.4050902@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
> On Wed, 2008-10-22 at 21:47 +0100, Simon Riggs wrote:
>
>> But once you reach 64 transactions, you'll need to write an extra WAL
>> record for every subtransaction, which currently I've managed to avoid.
>
> Yes, I've managed to avoid it, but it will simplify the patch if you
> think its not worth bothering with. This won't really effect anybody
> I've met running straight Postgres, but it may effect EDB. It's not a
> problem for me, but I was second guessing objections.
>
> If I do that then I can just pass the slotId in full on every WAL
> record, which simplifies a couple of other things also.
>
> So, does everybody accept that we will write a WAL record for every
> subtransaction assigned, once we hit the size limit of the subxid cache?
> i.e. currently 65th subxid and beyond.

Would have to see the patch to understand what the code simplicity vs.
extra WAL logging tradeoff really is.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2008-10-23 06:09:56 Re: Block level concurrency during recovery
Previous Message Tom Lane 2008-10-23 05:08:51 Re: Can anyone explain to me how the "ps_OuterTupleSlot" in PlanState is being used in implementing HashJoin?