Re: Question about concurrent synchronous and asynchronous commits
| От | Dan Birken |
|---|---|
| Тема | Re: Question about concurrent synchronous and asynchronous commits |
| Дата | |
| Msg-id | AANLkTik_MPnkuh63SDNGSncD5kYfD9ti406nD1PSZWNU@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Question about concurrent synchronous and asynchronous commits (Vick Khera <vivek@khera.org>) |
| Ответы |
Re: Question about concurrent synchronous and asynchronous commits
|
| Список | pgsql-general |
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 wrong.
-Dan
On Wed, Jan 12, 2011 at 12:32 PM, Vick Khera <vivek@khera.org> wrote:
On Wed, Jan 12, 2011 at 12:03 AM, Dan Birken <birken@gmail.com> wrote:I'm pretty sure it does, because it has to flush the write-ahead log
> If I commit asynchronously and then follow that with a synchronous commit,
> does that flush the asynchronous commit as well?
to disk, and there's only one. You can think of it as getting the
flush for free from the first transaction, since the single flush
covered the requirements of both transactions.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: