Re: Decreasing WAL size effects

From: Kyle Cordes <kyle(at)kylecordes(dot)com>
To: pgsql <pgsql-general(at)postgresql(dot)org>
Subject: Re: Decreasing WAL size effects
Date: 2008-10-30 20:42:59
Message-ID: 490A1C53.7040602@kylecordes.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Greg Smith wrote:

> there's no chance it can accidentally look like a valid segment. But
> when an existing segment is recycled, it gets a new header and that's
> it--the rest of the 16MB is still left behind from whatever was in that
> segment before. That means that even if you only write, say, 1MB of new

[...]

> What clearxlogtail does is look inside the WAL segment, and it clears
> the "tail" behind the portion of that is really used. So our example
> file would end up with just the 1MB of useful data, followed by 15MB of

It sure would be nice if there was a way for PG itself to zero the
unused portion of logs as they are completed, perhaps this will make it
in as part of the ideas discussed on this list a while back to make a
more "out of the box" log-ship mechanism?

--
Kyle Cordes
http://kylecordes.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jason Long 2008-10-30 20:51:18 Re: Decreasing WAL size effects
Previous Message Joao Ferreira 2008-10-30 20:19:37 Re: speed up restore from dump

Browse pgsql-hackers by date

  From Date Subject
Next Message Jason Long 2008-10-30 20:51:18 Re: Decreasing WAL size effects
Previous Message Bernd Helmle 2008-10-30 20:24:08 WIP: Automatic view update rules