causing crash - Search results in mailing lists
Mailing lists >> pgsql-hackers >> Thread
2025-06-25 19:49:55 | pg_logical_slot_get_changes waits continously for a partial WAL record spanning across 2 (vignesh C)
causing the function to wait indefinitely at read_local_xlog_page_guts function. Currently, the logic attempts to read the complete WAL record based on the size obtained before the crash
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (3)
2025-06-19 14:05:49 | RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly (Hayato Kuroda (Fujitsu))
cause crash. Background =========== When pg_receivewal starts the replication and it uses the replication slot
Mailing lists >> pgsql-hackers >> Thread
2025-06-17 17:03:47 | Re: Avoid possible dereference null pointer (contrib/postgres_fdw/postgres_fdw.c) (Fujii Masao)
causes a crash, so Etsuro-san's analysis seems valid. That said, I still think
Mailing lists >> pgsql-hackers >> Thread
2025-06-17 13:30:22 | Re: Non-reproducible AIO failure (Konstantin Knizhnik)
crash=false max_parallel_workers_per_gather=0 fsync=off Scenario proposed by Andreas: c=16; pgbench -c $c -j $c -M prepared -n -f <(echo "select count(*) FROM large
Mailing lists >> pgsql-hackers >> Thread
2025-06-15 08:11:24 | Timeline switching with partial WAL records can break replica recovery (D Laaren)
crash recovery: a) a special XLOG_OVERWRITE_CONTRECORD record is written after the incomplete record, b) the page header where the rest of the record would reside is flagged with XLP_FIRST_IS_OVERWRITTEN_CONTRECORD
Mailing lists >> pgsql-hackers >> Thread
2025-06-10 19:37:03 | pg_restore causing ENOSPACE on the WAL partition. Fundamental issue? (Dimitrios Apostolou)
Hello list, I have previously raised an issue on pgsql-general, where PostgreSQL is logging
Mailing lists >> pgsql-hackers >> Thread
2025-06-07 01:34:13 | Re: Issues with 2PC at recovery: CLOG lookups and GlobalTransactionData (Noah Misch)
crash revived a file after unlink(), since RemoveTwoPhaseFile() does not fsync - unlink() failed in RemoveTwoPhaseFile() - backup protocol violation I agree start-of-recovery can correctly do your list of two discard actions; they
Mailing lists >> pgsql-hackers >> Thread
2025-05-25 23:10:44 | Re: MERGE issues around inheritance (Dean Rasheed)
causes a crash, even without WCO's or a RETURNING list (see the first test
Mailing lists >> pgsql-hackers >> Thread
2025-05-06 07:52:24 | A thousand pg_commit_ts truncate attempts per second, two restarting autovacuum processes, and a (Ian Axelrod)
crashing, despite no log message indicating so. There were three autovacuum processes running concurrently, with two of them potentially restarting. If they were rerunning due to the high rate of updates, I would expect them
Mailing lists >> pgsql-hackers >> Thread
2025-05-06 02:06:34 | [PATCH] Fix hostaddr crash during non-blocking cancellation (Jacob Champion)
crash in emitHostIdentityInfo(). The problem is that the synthetic connhost entry we've created for cancellation has an incorrect type field, which causes
Mailing lists >> pgsql-hackers >> Thread
2025-05-02 22:04:22 | Re: Adding skip scan (including MDAM style range skip scan) to nbtree (Peter Geoghegan)
crash. The first patch prevents us from dereferencing a NULL pointer (pstate) within _bt_advance_array_keys (unless on an assert-enabled build, where we get an assertion failure first). It would also be possible
Mailing lists >> pgsql-hackers >> Thread
2025-04-22 18:50:49 | Re: Check for tuplestorestate nullness before dereferencing (Tom Lane)
crash on (gdb) p debug_query_string $1 = 0x1d03160 "explain (costs off) declare c1 scroll cursor for select (select 42) as x;" The reason that the subsequent bit of code is safe is that !forward
Mailing lists >> pgsql-hackers >> Thread
2025-04-17 18:54:31 | Re: Changing shared_buffers without restart (Thomas Munro)
cause ftruncate() to try to defragment physical memory to fulfil your request and can eat some serious CPU, and SHM_LARGEPAGE_ALLOC_NOWAIT, and (2) if it's the second thing, well Linux is like
Mailing lists >> pgsql-hackers >> Thread
2025-04-05 19:46:37 | A modest proposal: make parser/rewriter/planner inputs read-only (Tom Lane)
caused (but e33f2335a and 0f43083d1 are the two latest examples), and of how many places there are that are brute-forcing a solution to the problem by copying a whole parsetree before letting
Mailing lists >> pgsql-hackers >> Thread
2025-04-04 18:05:05 | Re: [PoC] Reducing planning time when tables have many partitions (Tom Lane)
crashed in light testing suggests that maybe there's something I'm missing. I would be much happier if there were provision to expand the array at need. regards, tom lane diff --git a/contrib/postgres_fdw/postgres_fdw.c b/contrib/postgres_fdw/postgres_fdw.c