Re: [HACKERS] Priorities for 6.6

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Don Baccus <dhogaza(at)pacifier(dot)com>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Priorities for 6.6
Date: 1999-06-06 12:25:52
Message-ID: 375A68D0.A8DD3AC9@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> Don Baccus <dhogaza(at)pacifier(dot)com> writes:
> > While I don't doubt your analysis is correct for the case you've
> > uncovered, it doesn't explain why surrounding a bunch of selects
> > with a begin/end block greatly descreases disk activity for tables
> > that don't change.
>
> Hmm, I'm not sure why that should be, either. Anyone?

pg_log fsync for read-only xactions...
And more of that, commit fsyncs ALL dirty buffers
in pool, even dirtied not by xaction being committed!

Vadim

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vadim Mikheev 1999-06-06 12:26:46 Re: [HACKERS] Priorities for 6.6
Previous Message Vadim Mikheev 1999-06-06 12:22:44 Re: [HACKERS] Priorities for 6.6