Re: GUC-ify walsender MAX_SEND_SIZE constant - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: GUC-ify walsender MAX_SEND_SIZE constant
Date
Msg-id ZkKt4wv_zc-5-toJ@paquier.xyz
Whole thread Raw
In response to Re: GUC-ify walsender MAX_SEND_SIZE constant  (Majid Garoosi <amoomajid99@gmail.com>)
List pgsql-hackers
On Thu, Apr 25, 2024 at 02:53:33PM +0200, Majid Garoosi wrote:
> Unfortunately, I quit that company a month ago (I wish we could
> discuss this earlier) and don't have access to the environment
> anymore.
> I'll try to ask my teammates and see if they can find anything about
> the exact values of latency, bw, etc.
>
> Anyway, here is some description of the environment. Sadly, there
> are no numbers in this description, but I'll try to provide as much details
> as possible.
> There is a k8s cluster running over some VMs. Each postgres
> instance runs as a pod inside the k8s cluster. So, both the
> primary and standby servers are in the same DC, but might be on
> different baremetal nodes. There is an overlay network for the pods to
> see each other, and there's also another overlay network for the VMs
> to see each other.
> The storage servers are in the same DC, but we're sure they're on some
> racks other than the postgres pods. They run Ceph [1] project and provide
> Rados Block Devices (RBD) [2] interface. In order for k8s to use ceph, a
> Ceph-CSI [3] controller is running inside the k8s cluster.
> BTW, the FS type is ext4.

Okay, seeing the feedback for this patch and Andres disagreeing with
it as being a good idea, I have marked the patch as rejected as it was
still in the CF app.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: I have an exporting need...
Next
From: Bruce Momjian
Date:
Subject: Re: First draft of PG 17 release notes