From: Simon Riggs <simon@2ndquadrant.com>
To: Greg Smith <gsmith@gregsmith.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Matthew Wakeling <matthew@flymine.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: I/O on select count(*)
Date: Fri, 16 May 2008 19:23:55 +0100
Message-ID: <1210962235.18922.109.camel@ebony.site> (raw)
In-Reply-To: <Pine.GSO.4.64.0805161118210.4987@westnet.com>
References: <920841.71690.qm@web44808.mail.sp1.yahoo.com>
<482B1D5F.EE98.0025.0@wicourts.gov>
<Pine.GSO.4.64.0805142133250.27290@westnet.com>
<20080515020553.GN9838@alvh.no-ip.org>
<Pine.LNX.4.64.0805151245360.16756@aragorn.flymine.org>
<20080515155232.GC8221@alvh.no-ip.org>
<Pine.GSO.4.64.0805161118210.4987@westnet.com>
On Fri, 2008-05-16 at 14:05 -0400, Greg Smith wrote:
> After reading the code and that documentation a bit, the part I'm
> still not sure about is whether the CLOG entry is created when the XID
> is assigned and then kept current as the state changes, or whether
> that isn't even in CLOG until the transaction is committed. It seems
> like the latter, but there's some ambiguity in the wording and too
> many code paths for me to map right now.
Alvaro already said this, I thought? The clog is updated only at sub or
main transaction end, thank goodness. When the transactionid is assigned
the page of the clog that contains that transactionid is checked to see
if it already exists and if not, it is initialised.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: simon@2ndquadrant.com, gsmith@gregsmith.com, alvherre@commandprompt.com, matthew@flymine.org
Subject: Re: I/O on select count(*)
In-Reply-To: <1210962235.18922.109.camel@ebony.site>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox