Re: [PATCHES] Load Distributed Checkpoints, take 3

2007-06-24 Thread Simon Riggs
On Fri, 2007-06-22 at 22:19 +0100, Heikki Linnakangas wrote: However, I think shortening the checkpoint interval is a perfectly valid solution to that. Agreed. That's what checkpoint_timeout is for. Greg can't choose to use checkpoint_segments as the limit and then complain about unbounded

Re: [PATCHES] Load Distributed Checkpoints, take 3

2007-06-24 Thread Heikki Linnakangas
Simon Riggs wrote: On Fri, 2007-06-22 at 22:19 +0100, Heikki Linnakangas wrote: However, I think shortening the checkpoint interval is a perfectly valid solution to that. Agreed. That's what checkpoint_timeout is for. Greg can't choose to use checkpoint_segments as the limit and then

Re: [PATCHES] Load Distributed Checkpoints, take 3

2007-06-24 Thread Simon Riggs
On Fri, 2007-06-22 at 16:21 -0400, Tom Lane wrote: Heikki Linnakangas [EMAIL PROTECTED] writes: 3. Recovery will take longer, because the distance last committed redo ptr will lag behind more. True, you'd have to replay 1.5 checkpoint intervals on average instead of 0.5 (more or less,

Re: [PATCHES] Load Distributed Checkpoints, take 3

2007-06-24 Thread Simon Riggs
On Fri, 2007-06-22 at 16:57 -0400, Greg Smith wrote: If you're not, I think you should be. Keeping that replay interval time down was one of the reasons why the people I was working with were displeased with the implications of the very spread out style of some LDC tunings. They were already

[PATCHES] Docs for CREATE RULE with WHERE/NOTIFY

2007-06-24 Thread Dariusz Suchojad
Hello, I've just been bitten by this: dsuch=# CREATE RULE foorule AS ON UPDATE dsuch-# TO foo WHERE NEW.x = '1' dsuch-# DO ALSO NOTIFY bar; ERROR: rules with WHERE conditions may only have SELECT, INSERT, UPDATE, or DELETE actions Here's an explanation

Re: [PATCHES] Load Distributed Checkpoints, take 3

2007-06-24 Thread Greg Smith
On Sun, 24 Jun 2007, Simon Riggs wrote: I can't see why anyone would want to turn off smoothing: If they are doing many writes, then they will be effected by the sharp dive at checkpoint, which happens *every* checkpoint. There are service-level agreement situations where a short and sharp

Re: [PATCHES] Load Distributed Checkpoints, take 3

2007-06-24 Thread Tom Lane
Greg Smith [EMAIL PROTECTED] writes: I am not a fan of introducing a replacement feature based on what I consider too limited testing, and I don't feel this one has been beat on long yet enough to start pruning features that would allow better backward compatibility/transitioning. I think

Re: [PATCHES] Load Distributed Checkpoints, take 3

2007-06-24 Thread Greg Smith
On Mon, 25 Jun 2007, Tom Lane wrote: I'm not sure why you hold such strong allegiance to the status quo. We know that the status quo isn't working very well. Don't get me wrong here; I am a big fan of this patch, think it's an important step forward, and it's exactly the fact that I'm so

Re: [PATCHES] Load Distributed Checkpoints, take 3

2007-06-24 Thread Greg Smith
On Sun, 24 Jun 2007, Simon Riggs wrote: Greg can't choose to use checkpoint_segments as the limit and then complain about unbounded recovery time, because that was clearly a conscious choice. I'm complaining only because everyone seems content to wander in a direction where the multiplier