| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: COMMIT NOWAIT Performance Option (patch) |
| Date: | 2007-02-26 23:14:24 |
| Message-ID: | 24211.1172531664@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> A prototype patch is posted to -patches, which is WORK IN PROGRESS.
> [This patch matches discussion thread on -hackers.]
What does this accomplish other than adding syntactic sugar over a
feature that really doesn't work well anyway? I don't see any point
in encouraging people to use commit_delay in its present form. If we
had a portable solution for millisecond-or-so waits then maybe it would
work ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew T. O'Connor | 2007-02-26 23:23:22 | Re: autovacuum next steps, take 2 |
| Previous Message | Alvaro Herrera | 2007-02-26 23:11:44 | Re: autovacuum next steps, take 2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-02-26 23:49:33 | Re: COMMIT NOWAIT Performance Option (patch) |
| Previous Message | Simon Riggs | 2007-02-26 22:56:45 | COMMIT NOWAIT Performance Option (patch) |