causing crash - Search results in mailing lists
Mailing lists >> pgsql-general >> Thread
2025-05-26 17:30:37 | Re: Postgres 16 unexpected shutdown (postgres@arcict.com)
cause of this issue. During the crash, we found the following in the System Logs
Mailing lists >> pgsql-general >> Thread
2025-04-23 14:52:42 | segmentation fault (Zechman, Derek S)
crash and anything higher than that causes a segfault. Can anyone help with this problem
Mailing lists >> pgsql-general >> Thread
2024-11-25 00:58:01 | Re: Questions on Upgrading PostgreSQL from 15.0 to 15.9 and Setting Up Streaming Replication (Adrian Klaver)
crashes and know nothing about the state of their consumer(s). They will prevent removal of required resources even when there is no connection using them. This consumes storage because neither required WAL nor required
Mailing lists >> pgsql-general >> Thread
2024-11-09 08:04:09 | Re: pgsql_tmp consuming most of the space. (Ron Johnson)
crashing can cause it. What version of PG are you running? -- Death to , and butter
Mailing lists >> pgsql-general >> Thread
2024-11-04 00:27:49 | Re: Random memory related errors on live postgres 14.13 instance on Ubuntu 22.04 LTS (Vijaykumar Jain)
crashes and is often linked to improper memory handling in the application. Corrupted Size vs. Prev_Size: Similar to the previous errors, this suggests that there is a mismatch in expected memory sizes, which
Mailing lists >> pgsql-general >> Thread
2024-10-31 13:36:14 | pg_wal folder high disk usage (Paul Brindusa)
causing two applications to crash. Unfortunately our database admin is on leave today, and we are trying
Mailing lists >> pgsql-general >> Thread
2024-10-10 22:44:28 | Re: Question on indexes (sud)
crashed repetitively a few times and teammates suspecting the cause while it tried extending this
Mailing lists >> pgsql-general >> Thread
2024-07-11 01:19:16 | Query on partitioned table needs memory n_partitions * work_mem (Dimitrios Apostolou)
causes the postgres backend process to grow insanely very fast, and the kernel OOM killer to kill it rather soon. It seems it tries to allocate at least 1000 * work_mem. If I reduce
Mailing lists >> pgsql-general >> Thread >> Search in thread (2)
2024-06-08 20:33:34 | Re: Questions on logical replication (Justin)
cause any significant WAL build up to put the publisher at risk of of crashing
Mailing lists >> pgsql-general >> Thread >> Search in thread (3)
2024-06-05 10:22:57 | Re: Long running query causing XID limit breach (Laurenz Albe)
crash caused by a full disk on the standby, the answer is probably "no". Make
Mailing lists >> pgsql-general >> Thread
2024-05-08 16:28:01 | Re: Unexpected data when subscribing to logical replication slot (Adrian Klaver)
causing the commit on the server to wait for the WAL records to be flushed to disk and this is not happening in a timely manner in the '... 1 in 50 times' you mention
Mailing lists >> pgsql-general >> Thread >> Search in thread (2)
2024-04-17 13:06:31 | constant crashing hardware issue and thank you TAKE AWAY (jack)
I discovered that one of the memory sticks in the machine was damaged. Running memtest86
Mailing lists >> pgsql-general >> Thread
2024-04-15 00:50:46 | Re: constant crashing (Adrian Klaver)
On 4/14/24 14:50, jack wrote: Reply to list also Ccing list Go to the
Mailing lists >> pgsql-general >> Thread
2024-04-14 19:44:40 | re: constant crashing (jack)
Here is the table structure: The fields being updated are the ones that are NOT
Mailing lists >> pgsql-general >> Thread >> Search in thread (2)
2024-04-14 18:11:23 | Re: constant crashing (David G. Johnston)
causing the crash but can definitely be an issue and is pointless to incur during