Re: [PATCHES] WIP archive_timeout patch

From: "Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Hannu Krosing" <hannu(at)skype(dot)net>, <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [PATCHES] WIP archive_timeout patch
Date: 2006-08-18 08:20:47
Message-ID: E1539E0ED7043848906A8FF995BDA5790140FDD9@m0143.s-mxs.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


> I noticed a minor annoyance while testing: when the system is
> completely idle, you get a forced segment switch every
> checkpoint_timeout seconds, even though there is nothing
> useful to log. The checkpoint code is smart enough not to do
> a checkpoint if nothing has happened since the last one, and
> the xlog switch code is smart enough not to do a switch if
> nothing has happened since the last one ... but they aren't
> talking to each other and so each one's change looks like
> "something happened"
> to the other one. I'm not sure how much trouble it's worth
> taking to prevent this scenario, though. If you can't afford
> a WAL file switch every five minutes, you probably shouldn't
> be using archive_timeout anyway ...

Um, I would have thought practical timeouts would be rather more
than 5 minutes than less. So this does seem like a problem to me :-(

Andreas

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2006-08-18 08:23:20 Re: Win32 max connections bug (causing crashes)
Previous Message Simon Riggs 2006-08-18 08:14:47 Re: [PATCHES] WIP archive_timeout patch

Browse pgsql-patches by date

  From Date Subject
Next Message Magnus Hagander 2006-08-18 11:49:06 Re: pg_regress in C
Previous Message Simon Riggs 2006-08-18 08:14:47 Re: [PATCHES] WIP archive_timeout patch