Ynt: WAL and backup recovery - Mailing list pgsql-admin

From Murat YILDIZ
Subject Ynt: WAL and backup recovery
Date
Msg-id 9eis8v$ttv$1@news.tht.net
Whole thread Raw
In response to Re: WAL and backup recovery  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Tom Lane <tgl@sss.pgh.pa.us> wrote in message
news:14951.990634138@sss.pgh.pa.us...
> Dario Brignardello <dbrignar@sinectis.com> writes:
> >       checkpoint_segments = 1
> > checkpoint_timeout = 30
>
> Reducing checkpoint_segments and checkpoint_timeout is actually
> seriously counterproductive, if your problem is amount of disk space
> chewed up by WAL logs during a long transaction (such as bulk load of
> a big table).  The WAL log cannot be truncated until the xact commits,
> so the checkpoints that happen meanwhile just cause log bloat.  Lots
> of it, because each checkpoint causes fresh copying of modified pages
> into the WAL log.
So let me know one thing, does checkpoint cause copying modified pages to
WAL log or does it just flush the modified pages to disk?
I thought WAL writings occur when pages being modified, deleted or inserted,
please correct me if I am wrong...thanx....


Murat



>
> Try increasing those numbers, not decreasing them.  Maybe 10/600 or so?
>
> Also, if you are short on disk space for WAL, increasing wal_files isn't
> such a great idea either.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)



pgsql-admin by date:

Previous
From: "Madness"
Date:
Subject: Ynt: createdb -D /other/path dbname does not work
Next
From: "Jeff Barrett"
Date:
Subject: pqReadData() -- backend closed the channel unexpectedly.