Re: Master - Slave Replication Window Server

2021-06-14 Thread Haseeb Khan
Thankyou Rory ! Br, Haseeb Ahmad > On 15-Jun-2021, at 12:42 AM, Rory Campbell-Lange > wrote: > > On 15/06/21, Haseeb Khan (khanhasee...@gmail.com) wrote: >> Does anyone have complete documentation to configure PostgreSQL V13 Master >> and Slave on Windows Server and also how to test Manual

Re: overcommit_ratio setting

2021-06-14 Thread Yi Sun
> On Mon, 2021-06-14 at 18:16 +0800, Yi Sun wrote: > > After checking doc, only mentioned vm.overcommit_memory=2, but didn't > mentioned vm.overcommit_ratio recommended value > > > https://www.postgresql.org/docs/11/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT > > some articles mentioned that 80

Re: Master - Slave Replication Window Server

2021-06-14 Thread Rory Campbell-Lange
On 15/06/21, Haseeb Khan (khanhasee...@gmail.com) wrote: > Does anyone have complete documentation to configure PostgreSQL V13 Master > and Slave on Windows Server and also how to test Manual Failover ? I suggest having a look at https://www.postgresql.org/docs/13/high-availability.html The

Master - Slave Replication Window Server

2021-06-14 Thread Haseeb Khan
Hello Everyone ! I trust that you guys are keep doing very Well ! Does anyone have complete documentation to configure PostgreSQL V13 Master and Slave on Windows Server and also how to test Manual Failover ? Would highly appreciated, if someone could help in this regard. Br, Haseeb Ahmad

Re: Planning performance problem (67626.278ms)

2021-06-14 Thread Manuel Weitzman
> However, I'm skeptical that any problem actually remains in > real-world use cases. Hello Tom, We also had some issues with planning and get_actual_variable_range(). We actually found some interesting behaviour that probably requires an eye with better expertise in how the planner works. For

Re: overcommit_ratio setting

2021-06-14 Thread Laurenz Albe
On Mon, 2021-06-14 at 18:16 +0800, Yi Sun wrote: > After checking doc, only mentioned vm.overcommit_memory=2, but didn't > mentioned vm.overcommit_ratio recommended value > https://www.postgresql.org/docs/11/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT > some articles mentioned that 80 or 90

Re: overcommit_ratio setting

2021-06-14 Thread Julien Rouhaud
On Mon, Jun 14, 2021 at 06:16:35PM +0800, Yi Sun wrote: > > So is it OK just to configure vm.overcommit_ratio to 90 please? This parameter entirely depends on the amount of RAM and swap you have on your server, and how much memory you want to be allocable. See

Re: pg_dumpall --exclude-database case folding, was Re: AWS forcing PG upgrade from v9.6 a disaster

2021-06-14 Thread Tom Lane
Andrew Dunstan writes: > On 6/10/21 2:23 PM, Andrew Dunstan wrote: >> Ouch. That looks like a plain old bug. Let's fix it. IIRC I just used >> the same logic that we use for pg_dump's --exclude-* options, so we need >> to check if they have similar issues. > Peter Eisentraut has pointed out to

pg_dumpall --exclude-database case folding, was Re: AWS forcing PG upgrade from v9.6 a disaster

2021-06-14 Thread Andrew Dunstan
On 6/10/21 2:23 PM, Andrew Dunstan wrote: > On 6/10/21 2:00 PM, Tom Lane wrote: >> "Dean Gibson (DB Administrator)" writes: >>> On 2021-06-10 09:54, Ranier Vilela wrote: Your cmd lacks = =>pg_dumpall -U Admin --exclude-database=MailPen >zzz.sql >>> I read that before posting, but

overcommit_ratio setting

2021-06-14 Thread Yi Sun
Hello, After checking doc, only mentioned vm.overcommit_memory=2, but didn't mentioned vm.overcommit_ratio recommended value https://www.postgresql.org/docs/11/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT some articles mentioned that 80 or 90 configuration in their env So is it OK just to