| 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, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] COMMIT NOWAIT Performance Option (patch) |
| Date: | 2007-02-27 04:07:10 |
| Message-ID: | 10522.1172549230@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:
> On Mon, 2007-02-26 at 18:14 -0500, Tom Lane wrote:
>> What does this accomplish other than adding syntactic sugar over a
>> feature that really doesn't work well anyway?
> This patch doesn't intend to implement group commit. I've changed the
> meaning of commit_delay, sorry if that confuses.
Ah. The patch was pretty much unintelligible without the discussion
(which got here considerably later :-(). I've still got misgivings
about how safe it really is, but at least this is better than what
commit_delay wishes it could do.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-02-27 04:14:01 | Re: Expanding DELETE/UPDATE returning |
| Previous Message | Jeroen T. Vermeulen | 2007-02-27 04:05:45 | Re: COMMIT NOWAIT Performance Option |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Marcellino | 2007-02-27 05:00:09 | POSIX shared memory support |
| Previous Message | John Bartlett | 2007-02-27 03:23:17 |