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
