From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kasia Tuszynska <ktuszynska(at)esri(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: transaction time and log analysis |
Date: | 2010-10-18 23:09:02 |
Message-ID: | 27499.1287443342@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Kasia Tuszynska <ktuszynska(at)esri(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Lukasz Brodziak | 2010-10-19 05:02:37 | Re: Postgres service won't start, doesn't log any errors |
Previous Message | Joe Carr | 2010-10-18 22:55:47 | Re: Postgres service won't start, doesn't log any errors |