On 06/27/2017 11:47 PM, Daniel Westermann wrote:
AFAIK the wal writer process.
>Um, no. "Synchronous" means that the caller has to wait for the
result to appear before it can move on. "Asynchronous" means that >he
caller can issue the instruction and immediately move on. I guessing
AFAIK the wal writer process.
>Um, no. "Synchronous" means that the caller has to wait for the result to
appear before it can move on. "Asynchronous" means that >he caller can issue
the instruction and immediately move on. I guessing here but while usually the
caller would have to
On Tue, Jun 27, 2017 at 3:52 PM, Adrian Klaver
wrote:
> On 06/27/2017 11:19 AM, Daniel Westermann wrote:
> >
> > Thanks, Adrian
> > It is clear now for the asynchronous stuff and wal_writer.
> > But I still did not figure out (or I am just not able to understand it
>
On 06/27/2017 11:19 AM, Daniel Westermann wrote:
>>On 06/23/2017 05:50 AM, Daniel Westermann wrote:
>>> Hi all,
>
> Thanks, Adrian
> It is clear now for the asynchronous stuff and wal_writer.
> But I still did not figure out (or I am just not able to understand it from
> the README linked
On Tuesday, June 27, 2017, Daniel Westermann <
daniel.westerm...@dbi-services.com> wrote:
> >On 06/23/2017 05:50 AM, Daniel Westermann wrote:
>
> But I still did not figure out (or I am just not able to understand it from
> the README linked above)
> which process is actually doing the write to
>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
>>
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