Guidance Needed: Scaling PostgreSQL for 12 TB Data Growth - New Feature Implementation

Dear PostgreSQL Community, We are implementing a new feature in our application that is expected to generate a significant amount of data, and we are seeking your expert guidance on how to best handle this growth within our existing PostgreSQL setup. Currently, our PostgreSQL instance runs on a

Re: Memory Not Released After Batch Completion – Checkpointer/Background Writer Behavior , postgres 15

; As for memory climbing to 90%, you might want to reduce shared buffers to > something less than 1/3 of your RAM and see if it helps. > But again, if there’s no issues with system availability and health then > you should not be bothered imo > > > 6 апр. 2025 г., в 14:37, Motog

Memory Not Released After Batch Completion – Checkpointer/Background Writer Behavior , postgres 15

Hi All, I’m running PostgreSQL on an EC2 c5.4xlarge Ubuntu instance with the following specs: 32 GB RAM 1.2 TB disk 16 vCPUs Pgpool-II Configuration: max_pool = 2 num_init_children = 1000 client_idle_limit = 300 seconds connection_life_time = 300 seconds load_balance_mode = on PostgreS

Background writer not active

Hi Team, Hope you are doing well! We are doing performance testing of our applications. During testing our postgres db got crashed with the error checkpointer was killed by signal 9. When checked system logs we found it was OOM issue. We have postgreSQL on independent node with 32GB RAM, multiple