Re: more anti-postgresql FUD

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, andrew(at)supernews(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: more anti-postgresql FUD
Date: 2006-10-13 18:07:44
Message-ID: 20061013180744.GJ28647@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Fri, Oct 13, 2006 at 01:52:10PM -0400, Merlin Moncure wrote:
> On 10/13/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> >> Is that really true? In theory block n+1 could be half a revolution
> >> after block n, allowing you to commit two transactions per revolution.
> >
> >Not relevant, unless the prior transaction happened to end exactly at a
>
> does full page writes setting affect this?

If anything it makes it more true, but full pages are only written the
first time a page is dirtied after a checkpoint, so in a
high-transaction system I suspect they don't have a lot of impact.

It would be nice to have stats on how many transactions have to write a
full page, as well as how many have been written, though...
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-10-13 18:19:12 Re: some log statements ignored
Previous Message brian 2006-10-13 18:06:49 Re: some log statements ignored

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2006-10-13 18:32:26 Re: more anti-postgresql FUD
Previous Message Stefan Kaltenbrunner 2006-10-13 18:07:17 Re: [PERFORM] Hints proposal