Horton

Re: Connection slots reserved for replication

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Alexander Kukushkin <cyberdemn@gmail.com>
Cc: Oleksii Kliukin <alexk@hintbits.com>, Petr Jelinek <petr.jelinek@2ndquadrant.com>, Stephen Frost <sfrost@snowman.net>, Magnus Hagander <magnus@hagander.net>, Masahiko Sawada <sawada.mshk@gmail.com>, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-01-15T20:21:18Z
Lists: pgsql-hackers 
On Wed, Jan 2, 2019 at 6:36 AM Alexander Kukushkin <cyberdemn@gmail.com> wrote:
> I was also thinking about changing the value in PG_CONTROL_VERSION,
> because we added the new field into the control file, but decided to
> leave this change to committer.

We typically omit catversion bumps from submitted patches to avoid
unnecessary conflicts, but I think PG_CONTROL_VERSION doesn't change
enough to cause a problem.  Also, it's not date-dependent the way
catversion is.  So I would include the bump in the patch, if it were
me.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

  1. Fix description of WAL record XLOG_PARAMETER_CHANGE

  2. Move max_wal_senders out of max_connections for connection slot handling