| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Daniel Westermann <daniel(dot)westermann(at)dbi-services(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Which process is actually doing the WAL writes/calls XLogFlush? |
| Date: | 2017-06-23 13:32:40 |
| Message-ID: | 8434fcbf-f75d-57c9-51a6-677d23b5a14c@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 06/23/2017 05:50 AM, Daniel Westermann wrote:
> Hi all,
>
> as I did not find the answer in the documentation: Which background
> process is actually doing the writes/flushes to the WAL? In the docs
> (https://www.postgresql.org/docs/10/static/wal-configuration.html) it is
> explained which internal functions are responsible for this:
> XLogInsertRecord and XLogFlush but who does call them, especially the
> flush? Is it the process for the user connection itself then which calls
> this after commit?
For all the details see here:
>
> Initially I thought it is the job of the wal_writer but according to
> this blog post
> (http://www.cybertec.at/postgresql-writer-and-wal-writer-processes-explained/)
> this seems not to be true, right? Why do I need the wal_writer at all
> then when synchronous_commit is set to something else than off?
See here:
https://www.postgresql.org/docs/9.6/static/wal-async-commit.html
>
> Thanks for your help
> Daniel
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2017-06-23 13:41:24 | Re: PostgreSQL Cookbook Testing |
| Previous Message | Karsten Hilbert | 2017-06-23 13:17:34 | Re: PostgreSQL Cookbook Testing |