public inbox for [email protected]help / color / mirror / Atom feed
[PATCH v2 1/1] don't emit shutdown messages for 'postgres -C' with runtime-computed GUCs 4+ messages / 3 participants [nested] [flat]
* [PATCH v2 1/1] don't emit shutdown messages for 'postgres -C' with runtime-computed GUCs @ 2022-03-15 22:36 Nathan Bossart <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: Nathan Bossart @ 2022-03-15 22:36 UTC (permalink / raw) --- src/backend/postmaster/postmaster.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c index 80bb269599..bf48bc6326 100644 --- a/src/backend/postmaster/postmaster.c +++ b/src/backend/postmaster/postmaster.c @@ -1066,6 +1066,10 @@ PostmasterMain(int argc, char *argv[]) false, false); puts(config_val ? config_val : ""); + + /* don't emit shutdown messages */ + SetConfigOption("log_min_messages", "PANIC", PGC_INTERNAL, PGC_S_OVERRIDE); + ExitPostmaster(0); } -- 2.25.1 --82I3+IH0IqGh5yIs-- ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Built-in Raft replication @ 2025-04-23 16:48 Jim Nasby <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Jim Nasby @ 2025-04-23 16:48 UTC (permalink / raw) To: Greg Sabino Mullane <[email protected]>; +Cc: Ashutosh Bapat <[email protected]>; Andrey Borodin <[email protected]>; Tom Lane <[email protected]>; Konstantin Osipov <[email protected]>; Nikolay Samokhvalov <[email protected]>; PostgreSQL Hackers <[email protected]> On Apr 16, 2025, at 2:29 PM, Greg Sabino Mullane <[email protected]> wrote: > > On Wed, Apr 16, 2025 at 2:18 AM Ashutosh Bapat <[email protected] <mailto:[email protected]>> wrote: >> Users find it a waste of resources to deploy 3 big PostgreSQL instances just for HA where 2 suffice even if they deploy 3 lightweight DCS instances. Having only some of the nodes act as DCS and others purely PostgreSQL nodes will reduce waste of resources. > > A big problem is that putting your DCS into Postgres means your whole system is now super-sensitive to IO/WAL-streaming issues, and a busy database doing database stuff is going to start affecting the DCS stuff. With three lightweight DCS servers, you don't really need to worry about how stressed the database servers are. In that way, I feel etcd et al. are adhering to the unix philosophy of "do one thing, and do it well.” … unless we added multiple WAL streams. That would allow for splitting WAL traffic across multiple devices as well as providing better support for configurations that don’t replicate the entire cluster. The current situation where delayed replication of a single table mandates retention of all the WAL for the entire cluster is less than ideal. ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Built-in Raft replication @ 2025-04-23 17:01 Devrim Gündüz <[email protected]> parent: Jim Nasby <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Devrim Gündüz @ 2025-04-23 17:01 UTC (permalink / raw) To: Jim Nasby <[email protected]>; Greg Sabino Mullane <[email protected]>; +Cc: Ashutosh Bapat <[email protected]>; Andrey Borodin <[email protected]>; Tom Lane <[email protected]>; Konstantin Osipov <[email protected]>; Nikolay Samokhvalov <[email protected]>; PostgreSQL Hackers <[email protected]> Hi, On Wed, 2025-04-23 at 11:48 -0500, Jim Nasby wrote: > unless we added multiple WAL streams. That would allow for splitting > WAL traffic across multiple devices as well as providing better > support for configurations that don’t replicate the entire cluster. > The current situation where delayed replication of a single table > mandates retention of all the WAL for the entire cluster is less than > ideal. I think the problem is handling the stream of global objects. Having separate stream for each database would be awesome as long as it can deal with the "global stream". Regards, -- Devrim Gündüz Open Source Solution Architect, PostgreSQL Major Contributor BlueSky: @devrim.gunduz.org , @gunduz.org Attachments: [application/pgp-signature] signature.asc (858B, ../../[email protected]/2-signature.asc) download ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Built-in Raft replication @ 2025-04-29 20:16 Jim Nasby <[email protected]> parent: Devrim Gündüz <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: Jim Nasby @ 2025-04-29 20:16 UTC (permalink / raw) To: Devrim Gündüz <[email protected]>; +Cc: Greg Sabino Mullane <[email protected]>; Ashutosh Bapat <[email protected]>; Andrey Borodin <[email protected]>; Tom Lane <[email protected]>; Konstantin Osipov <[email protected]>; Nikolay Samokhvalov <[email protected]>; PostgreSQL Hackers <[email protected]> I've always assumed there'd have to be at least one global stream, if for no other purpose than to be the source of truth about transaction commit ordering (though, I was thinking of supporting multiple streams for one database). Presumably the same could be used for shared objects. Or perhaps shared objects just get their own stream. Either way, having a master commit record that points at LSNs of various other streams is what I'd been thinking. On Wed, Apr 23, 2025 at 12:01 PM Devrim Gündüz <[email protected]> wrote: > Hi, > > On Wed, 2025-04-23 at 11:48 -0500, Jim Nasby wrote: > > unless we added multiple WAL streams. That would allow for splitting > > WAL traffic across multiple devices as well as providing better > > support for configurations that don’t replicate the entire cluster. > > The current situation where delayed replication of a single table > > mandates retention of all the WAL for the entire cluster is less than > > ideal. > > I think the problem is handling the stream of global objects. Having > separate stream for each database would be awesome as long as it can > deal with the "global stream". > > Regards, > -- > Devrim Gündüz > Open Source Solution Architect, PostgreSQL Major Contributor > BlueSky: @devrim.gunduz.org , @gunduz.org > ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2025-04-29 20:16 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2022-03-15 22:36 [PATCH v2 1/1] don't emit shutdown messages for 'postgres -C' with runtime-computed GUCs Nathan Bossart <[email protected]> 2025-04-23 16:48 Re: Built-in Raft replication Jim Nasby <[email protected]> 2025-04-23 17:01 ` Re: Built-in Raft replication Devrim Gündüz <[email protected]> 2025-04-29 20:16 ` Re: Built-in Raft replication Jim Nasby <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox