Re: Properly handle OOM death?
On 3/18/23 18:02, Tomas Pospisek wrote: On 13.03.23 21:25, Joe Conway wrote: Hmm, well big +1 for having swap turned on, but I recommend setting "vm.overcommit_memory=2" even so. I've snipped out the context here, since my advice is very unspecific: do use swap only as a safety net. Once your system starts swapping performance goes down the toilet. While I agree with this statement in principle, it is exactly the notion that "once your system starts swapping performance goes down the toilet" that leads people to conclude that having lots of memory and disabling swap will solve all their problems. Because of how the Linux kernel works, you should, IMHO, always have some swap available. For more on why, see: https://chrisdown.name/2018/01/02/in-defence-of-swap.html -- Joe Conway PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
Re[2]: Getting error while upgrading postgres from version 12 to 13
Hello, As per error it seems you have initiated source data with PG13 binaries. Could you please connect to both source and target psql and share out of select versions(); Also share pg_upgrade complete command which you are using. Regards, Abdul Sayeed Sent from myMail for iOS Sunday, 19 March 2023 at 11:29 AM +0530 from david.g.johns...@gmail.com : >On Sat, Mar 18, 2023 at 7:27PM shashidhar Reddy < shashidharreddy...@gmail.com >> wrote: >>Can someone please help me with this? >>> > >You haven't given others enough information to help you. Present to the >fullest extent possible your current environment and the commands you are >running. Showing that psql itself works on both running clusters would be a >good start. Show inputs, not just outputs those inputs creates. > >David J.
