Mailing lists [pgsql-admin]

13 October 2023

• 02:46   Locks analyze Rajesh Kumar
• 04:41   Re: Fwd: Why does pg_rewind deny permission for pg_read_binary_file() other than 'dbname=postgres'? Zhaoxun Yan
• 05:03   Re: Fwd: Why does pg_rewind deny permission for pg_read_binary_file() other than 'dbname=postgres'? Tom Lane
• 05:21   Re: Locks analyze Scott Ribe
• 09:02   Re: Locks analyze Laurenz Albe
• 09:40   Re: Fwd: Why does pg_rewind deny permission for pg_read_binary_file() other than 'dbname=postgres'? Zhaoxun Yan
• 10:04   Re: Why does pg_rewind deny permission for pg_read_binary_file() other than 'dbname=postgres'? David G. Johnston
• 11:51   Re: Automation Rajesh Kumar
• 12:39   Re: Locks analyze Rajesh Kumar
• 14:59   Re: Locks analyze Laurenz Albe
• 16:06   One PG process eating more than 40GB of RAM and getting killed by OOM Jean-Christophe Boggio
• 16:12   Re: One PG process eating more than 40GB of RAM and getting killed by OOM MichaelDBA
• 16:13   Re: One PG process eating more than 40GB of RAM and getting killed by OOM Johannes Truschnigg
• 16:13   Re: One PG process eating more than 40GB of RAM and getting killed by OOM Michael Banck
• 16:14   Re: Locks analyze Scott Ribe
• 17:31   Re: One PG process eating more than 40GB of RAM and getting killed by OOM Jean-Christophe Boggio
• 17:57   Re: Locks analyze Rajesh Kumar
• 18:02   Re: One PG process eating more than 40GB of RAM and getting killed by OOM Tom Lane
• 19:48   Re: One PG process eating more than 40GB of RAM and getting killed by OOM Jeff Janes
• 22:12   Re: One PG process eating more than 40GB of RAM and getting killed by OOM Jean-Christophe Boggio
• 22:38   Re: One PG process eating more than 40GB of RAM and getting killed by OOM Tom Lane