pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Greg Smith <greg@2ndquadrant.com>
To: jtkells@verizon.net
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL and Checkpoints documentation
Date: Mon, 23 May 2011 13:30:31 -0400
Message-ID: <4DDA99B7.6050802@2ndquadrant.com> (raw)
In-Reply-To: <mdrkt69ab5i8l183ss3juvehgjsp6hbb2m@4ax.com>
References: <mdrkt69ab5i8l183ss3juvehgjsp6hbb2m@4ax.com>
jtkells@verizon.net wrote:
> Does anyone know of any good presentations/whitepapers that spell out WAL and check-pointing
> functionality other than the ADMIN guide
http://www.westnet.com/~gsmith/content/postgresql/chkp-bgw-83.htm is the
main free reference that tries to step outside of the documentation into
real-world tuning advice. There are a few of my talks at
http://projects.2ndquadrant.it/talks that mention material around this
area too; "Inside the PostgreSQL Buffer Cache" and "The Write Stuff"
both overlap with checkpoint issues quite a bit. Beyond that, my book
is the main extended commentary discussing this area available.
--
Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
"PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books
view thread (3+ messages)
Message-ID: <4DDA99B7.6050802@2ndquadrant.com> Permalink: ../4DDA99B7.6050802@2ndquadrant.com/ Also on: postgresql.org/message-id/4DDA99B7.6050802@2ndquadrant.com ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients using the --to and --cc options: reply via email To: pgsql-admin@postgresql.org Cc: greg@2ndquadrant.com, jtkells@verizon.net Subject: Re: WAL and Checkpoints documentation In-Reply-To: <4DDA99B7.6050802@2ndquadrant.com> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox