On Thu, Jan 13, 2011 at 6:55 PM, Dan Birken wrote:
> When you begin a transaction, all your changes write to the in-memory WAL
> buffer, and that buffer flushes to disk when:
> a) Somebody commits a synchronous transaction
> b) The WAL buffer runs out of space
> Please correct me if I'm wrong.
I
Ok given your response, this is my understanding of how the WAL works:
When you begin a transaction, all your changes write to the in-memory WAL
buffer, and that buffer flushes to disk when:
a) Somebody commits a synchronous transaction
b) The WAL buffer runs out of space
Please correct me if I'm
On Wed, Jan 12, 2011 at 12:03 AM, Dan Birken wrote:
> If I commit asynchronously and then follow that with a synchronous commit,
> does that flush the asynchronous commit as well?
I'm pretty sure it does, because it has to flush the write-ahead log
to disk, and there's only one. You can think of
I notice on the documentation page about Asynchronous Commit (
http://www.postgresql.org/docs/8.3/static/wal-async-commit.html*)*, it says
the follow "The user can select the commit mode of each transaction, so that
it is possible to have both synchronous and asynchronous commit transactions
runnin
