Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] WAL logging freezing

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>,"Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>,<pgsql-hackers(at)postgresql(dot)org>,<pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] WAL logging freezing
Date: 2006-10-31 14:24:12
Message-ID: 1162304652.11568.634.camel@silverbirch.site (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Mon, 2006-10-30 at 20:40 -0500, Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> > That was understood; in the above example I agree you need to flush. If
> > you don't pass a truncation point, you don't need to flush whether or
> > not you actually truncate. So we don't need to flush *every* time,
> 
> OK, but does that actually do much of anything for your performance
> complaint?  Just after GlobalXmin has passed a truncation point, *every*
> vacuum the system does will start performing a flush-n-fsync, which
> seems like exactly what you didn't like.  If the syncs were spread out
> in time for different rels then maybe this idea would help, but AFAICS
> they won't be.

Makes sense, so we shouldn't do it that way after all.

Are you OK with the other patches I've submitted? My understanding was
that you're gonna have a look at those and this general area? I don't
want to hold up the release because of a PITR patch.

Feedback welcome ;-)

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com



In response to

pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2006-10-31 14:42:23
Subject: Re: [HACKERS] Index greater than 8k
Previous:From: Heikki LinnakangasDate: 2006-10-31 10:41:10
Subject: Re: [HACKERS] WAL logging freezing

pgsql-patches by date

Next:From: Tom LaneDate: 2006-10-31 15:06:40
Subject: Re: [HACKERS] WAL logging freezing
Previous:From: Heikki LinnakangasDate: 2006-10-31 10:41:10
Subject: Re: [HACKERS] WAL logging freezing

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group