| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | hannu(at)krosing(dot)net, aidan(at)highrise(dot)ca, jesper(at)krogh(dot)cc, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: moving pg_xlog -- yeah, it's worth it! |
| Date: | 2010-02-12 14:10:36 |
| Message-ID: | 20100212141036.GB3737@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Alvaro Herrera wrote:
> Kevin Grittner wrote:
> > Anyway, given that these are replication
> > targets, and aren't the "database of origin" for any data of their
> > own, I guess there's no reason not to try asynchronous commit.
>
> Yeah; since the transactions only ever write commit records to WAL, it
> wouldn't matter a bit that they are lost on crash. And you should see
> an improvement, because they wouldn't have to flush at all.
Actually, a transaction that performed no writes doesn't get a commit
WAL record written, so it shouldn't make any difference at all.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-02-12 14:49:50 | Re: moving pg_xlog -- yeah, it's worth it! |
| Previous Message | Alvaro Herrera | 2010-02-12 14:03:48 | Re: moving pg_xlog -- yeah, it's worth it! |