From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kasia Tuszynska <ktuszynska@esri.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: transaction time and log analysis
Date: Mon, 18 Oct 2010 19:09:02 -0400
Message-ID: <27499.1287443342@sss.pgh.pa.us> (raw)
In-Reply-To: <232B5217AD58584C87019E8933556D110219AA4FA6@redmx2.esri.com>
References: <4CBC8886.9040608@nrc-cnrc.gc.ca>
<232B5217AD58584C87019E8933556D110219AA4FA6@redmx2.esri.com>
Kasia Tuszynska <ktuszynska@esri.com> writes:
> 1. Is there anything I could do to in postgresql.conf file to speed up the time it takes postgres to commit a transaction?
If you want the traditional guarantee that "commit" means "your data is
safely down on persistent storage", there's not much you can do except
buy better storage hardware. A disk controller card with battery-backed
cache can be a relatively inexpensive solution. Try the pgsql-performance
archives for more information than you need on that topic.
If you're willing to live with weaker guarantees, consider disabling
synchronous_commit.
> 2. Is there anything better than pg_fouine to analyze logs?
No idea on that one.
regards, tom lane
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: tgl@sss.pgh.pa.us, ktuszynska@esri.com
Subject: Re: transaction time and log analysis
In-Reply-To: <27499.1287443342@sss.pgh.pa.us>
* 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