Postgresql 13.7 hangs down

Hi all, I have a postgresql cluster (13.7) with two nodes (master,slave) compiled in docker (alpine 3.15) with flags: ./configure --prefix=${PG_DIR} --exec-prefix=${PG_DIR} --enable-integer-datetimes --enable-thread-safety --disable-rpath --with-uuid=e2fs --with-gnu-ld --with-pgport=5432 --with-sy

Postgrsql blocked for more than 120 s

Hi, I have a problem with my slave postgresql instance. During normal operations databaseis locked and in syslog I see stacktrace: Jul 16 22:34:12 ec1-prd-postgresan-2 kernel: [ 1331.289110] INFO: task postgres:1172 blocked for more than 120 seconds. Jul 16 22:34:12 ec1-prd-postgresan-2 kernel: [

Re: Postgrsql blocked for more than 120 s

Hi, Problem was on disk io starvation, storage migration to more iops resolve the problem. Regards BS pon., 17 lip 2023 o 07:40 Bogdan Siara napisał(a): > Hi, I have a problem with my slave postgresql instance. During normal > operations databaseis locked and in syslog I see stacktrace: &

huge_pages=on cause could not map anonymous shared memory: Cannot allocate memory

Hi, I have problem to run postgresql on ubuntu 24.04 server with huge_pages = on. My instance have 8GB ram and 2 vcpus (t3a.large). My configuration is: max_connections = 1000 superuser_reserved_connections = 3 shared_buffers = 1960MB effective_cache_size = 5881MB huge_pages = on temp_buffers = 32

Re: huge_pages=on cause could not map anonymous shared memory: Cannot allocate memory

Hi Alicja, Thanks for your advice, now postgresql works fine with 'huge_pages=on'. Regards Bogdan śr., 7 maj 2025 o 14:17 Alicja Kucharczyk napisał(a): > Hi Bogdan, > The root cause here is that the number of huge pages you've configured > (vm.nr_hugepages = 980) is not sufficient. > Each huge p