From: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Synchronous Commit Doc Patch |
Date: | 2007-07-13 19:00:40 |
Message-ID: | 20070713190040.GD39272@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On Fri, Jul 13, 2007 at 07:11:54PM +0100, Simon Riggs wrote:
> On Fri, 2007-07-13 at 12:38 -0500, Jim C. Nasby wrote:
> > One question... can operations that shortcut the WAL by fsyncing direct
> > to disk also use async commit? I suspect the answer is an implicit "no"
> > because the only examples I can think of all involve DDL, but it's
> > probably worth spelling that out...
>
> They can, but the WAL-avoiding ops are all designed for bulk ops, so
> you'll get something like 0.0001% benefit by using async commit for
> them.
Yeah, I knew it wouldn't help much, I just wasn't clear on what the
effect would be. I guess I'm also a bit confused... the only shortcut I
know of (COPY into a table created in the same transaction) involves
creating files, so it would be ineligible for async commit, or are there
other shortcuts? Do we list the shortcuts anywhere in the docs?
> Thanks for reading.
Thanks for writing. :)
--
Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-07-13 19:12:29 | Re: Synchronous Commit Doc Patch |
Previous Message | Heikki Linnakangas | 2007-07-13 18:23:22 | Re: HOT latest patch - version 8 |