| From: | Rob Wultsch <wultsch(at)gmail(dot)com> |
|---|---|
| To: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Group commit and commit delay/siblings |
| Date: | 2010-12-05 20:40:28 |
| Message-ID: | AANLkTik3dr076BMQ6MqCLZZ0x2-qxmQgWoqCR7c0ePoD@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Manual: http://www.postgresql.org/docs/9.0/static/runtime-config-wal.html#RUNTIME-CONFIG-WAL-SETTINGS
Recent discussion:
http://www.facebook.com/notes/mysql-at-facebook/group-commit-in-postgresql/465781235932
It is my understanding that group commit in PG works without the
commit_delay or commit_siblings being enabled. For many people coming
from other databases, the existence of these GUC seems to suggest that
group commit does not work without the being enabled.
Are these setting useful, and if so how should they be tuned?
If they are generally are not useful, should these settings be removed?
--
Rob Wultsch
wultsch(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jignesh Shah | 2010-12-06 02:30:40 | Re: Group commit and commit delay/siblings |
| Previous Message | Tom Lane | 2010-12-05 20:14:38 | Re: Query-plan for partitioned UPDATE/DELETE slow and swaps vmem compared to SELECT |