Re: PostgreSQL 10.5 : Logical replication timeout results in PANIC in pg_wal "No space left on device"

From: Rui DeSousa <rui(at)crazybean(dot)net>
To: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL 10.5 : Logical replication timeout results in PANIC in pg_wal "No space left on device"
Date: 2018-11-16 15:36:04
Message-ID: 3631323B-8B6B-410E-9B08-D5877D99304A@crazybean.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> On Nov 16, 2018, at 3:18 AM, Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> wrote:
>
>>
>> net.inet.tcp.always_keepalive=1
>
> This setting is from FreeBSD. I have tested changing the settings on my PostgreSQL 11.1 on my FreeBSD 11.2-RELEASE-p3, and this would have no effect at all to the postgresql settings, they remained all three of them at zero.

That setting is not going to change Postgresql settings it’s not possible; however, it overrides the connection and forces TCP keep alive even if the application attempts to disable it. If you would to watch the connection you see the keep alive packets.

> This is completely irrelevant with my problem but anyway.

You have network related issue and this would detect and resolve the issue without fixing the network issue. You have to fix at least one or both of them.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Achilleas Mantzios 2018-11-17 10:51:42 Re: PostgreSQL 10.5 : Logical replication timeout results in PANIC in pg_wal "No space left on device"
Previous Message Rui DeSousa 2018-11-16 15:29:07 Re: PostgreSQL 10.5 : Logical replication timeout results in PANIC in pg_wal "No space left on device"