causing crash - Search results in mailing lists
Mailing lists >> pgsql-performance >> Thread
2025-03-18 07:04:30 | Background writer not active (Motog Plus)
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 DBs are there witl multiple
Mailing lists >> pgsql-performance >> Thread
2025-02-01 01:28:16 | High System CPU Usage on Selects Seemingly Caused By Vacuum of Same Table (Joshua Banton)
Hello, We are experiencing a high system cpu issue with our database that we can
Mailing lists >> pgsql-performance >> Thread
2023-05-04 20:37:22 | Re: Fsync IO issue (ProfiVPS Support)
crashes we lose data anyways until restart, ofc we could have HA I know and we will when there'll be a need) . Around 100 times the write need for wall than the useful data
Mailing lists >> pgsql-performance >> Thread
2021-11-25 17:09:03 | Re: pg_dump backup verification (Justin Pryzby)
causing the main DB to fail queries or crash. 8) Keep a few backups rotated
Mailing lists >> pgsql-performance >> Thread
2021-09-23 13:00:22 | hashjoins, index loops to retrieve pk/ux constrains in pg12 (Arturas Mazeika)
Causes all statements generating error at or above this level to be logged. log_min_messages warning Sets the message levels that are logged. log_parser_stats off Writes parser performance statistics to the server
Mailing lists >> pgsql-performance >> Thread
2020-05-18 18:42:09 | Execution time from >1s -> 80m+ when extra columns added in SELECTfor sub-query (A Guy Named Ryan)
Causes all statements generating error at or above this level to be logged. log_min_messages | warning | Sets the message levels that are logged. log_parser_stats | off | Writes parser performance statistics to the server
Mailing lists >> pgsql-performance >> Thread
2019-09-29 15:32:23 | Re: sequence depends on many tables (Tom Lane)
crash, or did something weird with backup/recovery, causing the counter to get reset? Anyway, the short
Mailing lists >> pgsql-performance >> Thread >> Search in thread (2)
2019-04-15 17:38:48 | Re: Out of Memory errors are frustrating as heck! (Alvaro Herrera)
causing crashes elsewhere. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training
Mailing lists >> pgsql-performance >> Thread
2019-02-27 14:47:13 | What is pg_stat_user_tables Showing NULL for last_autoanalyze &last_autovacuum (Fd Habash)
crash or restart with ‘immediate’ option will cause the timestamps to nullify. 3. Table never
Mailing lists >> pgsql-performance >> Thread >> Search in thread (2)
2018-12-21 13:40:25 | Re: database crash during pgbench run (Merlin Moncure)
cause the kind of memory consumption issues that would trigger an OOM. This is definitely not a database crash
Mailing lists >> pgsql-performance >> Thread >> Search in thread (3)
2018-08-29 07:44:07 | Re: dsa_allocate() faliure (Sand Stone)
caused the crash: "dsa_allocate could not find 13 free pages" on one of the worker
Mailing lists >> pgsql-performance >> Thread
2018-03-14 16:49:58 | Re: Too many .history file in pg_xlog takes lots of space (Alvaro Herrera)
causing a crash each time you restart. Are you using immediate mode in shutdown maybe
Mailing lists >> pgsql-performance >> Thread
2018-02-04 19:04:56 | Re: postgresql 10.1 wrong plan in when using partitions bug (Rick Otten)
crashes some queries when they have parallel gather enabled). My hope is that 10.2 will fix our issue "by accident" rather than on purpose. I'll try to build a test case this afternoon
Mailing lists >> pgsql-performance >> Thread
2017-08-09 17:37:29 | Re: [PERFORM] Unlogged tables (David G. Johnston)
cause the system to ensure that the data files are fully populated and then set a flag in the catalog that informs the crash
Mailing lists >> pgsql-performance >> Thread
2017-05-08 21:48:29 | Re: [PERFORM] Speed differences between two servers (Scott Marlowe)
cause of the difference would be that one server IS honoring fsync requests from the db and the other one isn't. If you run pgbench on both (something simple like pgbench