From: Kenneth Marshall <ktm@rice.edu>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: David Fetter <david@fetter.org>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: Bump default wal_level to logical
Date: Mon, 8 Jun 2020 14:05:26 -0500
Message-ID: <20200608190526.GX22800@aart.rice.edu> (raw)
In-Reply-To: <CA+TgmoYHptTXESRz0BAG3NXORs98Ty3GTb4rD02FTGNfhFre3w@mail.gmail.com>
References: <20200608133824.57lwoctf7gapnkmr@development>
<20200608171619.GA11063@alvherre.pgsql>
<CA+TgmoYHptTXESRz0BAG3NXORs98Ty3GTb4rD02FTGNfhFre3w@mail.gmail.com>
On Mon, Jun 08, 2020 at 02:58:03PM -0400, Robert Haas wrote:
> On Mon, Jun 8, 2020 at 1:16 PM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> > I think it's reasonable to push our default limits for slots,
> > walsenders, max_bgworkers etc a lot higher than current value (say 10 ->
> > 100). An unused slot wastes essentially no resources; an unused
> > walsender is just one PGPROC entry. If we did that, and also allowed
> > wal_level to be changed on the fly, we wouldn't need to restart in order
> > to enable logical replication, so there would be little or no pressure
> > to change the wal_level default.
>
> Wouldn't having a whole bunch of extra PGPROC entries have negative
> implications for the performance of GetSnapshotData() and other things
> that don't scale well at high connection counts?
>
+1
I think just having the defaults raised enough to allow even a couple DB
replication slots would be advantageous and allow it to be used to
address spur of the moment needs for systems that need to stay up. It
does seem wasteful to by default support large numbers of slots and
seems to be contrary to the project stance on initial limits.
Regards,
Ken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: ktm@rice.edu, robertmhaas@gmail.com, alvherre@2ndquadrant.com, tomas.vondra@2ndquadrant.com, magnus@hagander.net, michael@paquier.xyz, amit.kapila16@gmail.com, david@fetter.org
Subject: Re: Bump default wal_level to logical
In-Reply-To: <20200608190526.GX22800@aart.rice.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox