Re: [Bacula-users] PostgreSQL: WAL and log management

[George via Bacula-users]

On Sat, 24 Nov 2018 11:39:37 -0600 Dmitri Maziuk via
Bacula-users wrote:

> So set
>   max_wal_senders = 0 
> as well. Now looking at the fine manual I see they
> changed the default from 9.x, it used to be 0. 

I read in the manual:

"The value 0 means replication is disabled. [...]
Abrupt streaming client disconnection might cause an
orphaned connection slot until a timeout is reached,
so this parameter should be set slightly higher than
the maximum number of expected clients so disconnected
clients can immediately reconnect."

Could you please explain why this is what I should do?

-- 
George


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] PostgreSQL: WAL and log management

[Dmitri Maziuk via Bacula-users]

On Sat, 24 Nov 2018 01:36:12 +0200
George via Bacula-users  wrote:

> >  wal_level = minimal
> > and restart.
> 
> Trying this results in (journalclt excerpt):
> 
> Nov 24 01:11:05 pc postgresql-script[6374]: 2018-11-24 01:11:05.565 EET   
> [6383]FATAL:  WAL streaming (max_wal_senders > 0) requires wal_level 
> "replica" or "logical"

So set
  max_wal_senders = 0 
as well. Now looking at the fine manual I see they changed the default from 
9.x, it used to be 0. 

-- 
Dmitri Maziuk 


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users