cores - Search results in mailing lists
Mailing lists >> pgsql-bugs >> Thread
2025-06-18 19:46:35 | Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned (Tom Lane)
core test suites, either.) Also, looking at the error message changes, I'm less sure
Mailing lists >> pgsql-bugs >> Thread
2025-06-12 02:46:26 | Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements (Michael Paquier)
core, for example imagine an extension looking at a ViewStmt where we set the location
Mailing lists >> pgsql-bugs >> Thread
2025-06-11 06:58:32 | Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set (Никита Калинин)
core dumped). Coredump: #0 __pthread_kill_implementation (threadid=255760382287552, signo=signo@entry=6, no_tid=no_tid@entry
Mailing lists >> pgsql-bugs >> Thread
2025-06-05 07:52:46 | Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without (Michael Paquier)
core code. Well, now that you mention these things, I do feel like it while
Mailing lists >> pgsql-bugs >> Thread
2025-06-03 08:48:06 | Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1 (Michael Paquier)
core extensions, to give these a way to install something inside a plugins/ folder. At least
Mailing lists >> pgsql-bugs >> Thread
2025-05-19 18:21:27 | Re: BUG #18935: The optimiser's choice of sort doubles the execution time. (Tom Lane)
core of the problem is that the estimate of the number of rows coming into
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2025-05-08 21:17:01 | Re: BUG #18918: cron.schedule_in_database ERROR: must be superuser to create a job (David G. Johnston)
core community PostgreSQL distribution. You should report this wherever the people who created that extension
Mailing lists >> pgsql-bugs >> Thread
2025-04-24 09:04:59 | DSA refcnt overflow in pg_stat/could not attach to dynamic shared area (李园园)
cores shared_buffers = 128GB max_connections = 3000 worm_mem = 8M max_worker
Mailing lists >> pgsql-bugs >> Thread
2025-04-23 07:48:23 | BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c" (PG Bug reporting form)
Core was generated by `postgres: test postgres [local] EXPLAIN '. Program terminated with signal SIGABRT, Aborted
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2025-04-17 02:54:23 | Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load (Zane Duffield)
cores, 256GB RAM), and the other was quite weak (2 cores, 2GB RAM). I found
Mailing lists >> pgsql-bugs >> Thread
2025-04-10 02:49:18 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Thomas Munro)
core PostgreSQL tooling had a built-in assumption that the pre-Vista locales are 100% compatible
Mailing lists >> pgsql-bugs >> Thread
2025-03-31 11:38:37 | PostgreSQL 17.4 bug with JSON+UUID under high load (Constantine Plotnikov)
Core(TM) i9-13900K 3.00 GHz * 128M memory * Java 21 + PG JDBC 42.7.5 (the test
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2025-03-27 12:42:27 | Re: BUG #18832: Segfault in GrantLockLocal (Robins Tharakan)
Core was generated by `postgres: 44fe6ceb51f@sqith: u8 postgres 127.0.0.1(37802) ROLLBACK '. Program terminated with
Mailing lists >> pgsql-bugs >> Thread
2025-03-20 04:44:43 | Re: 回复：Re: The != and +/- signs are joined together as an operator (Tom Lane)
core and elsewhere, that would be broken by changing those rules now. regards, tom lane
Mailing lists >> pgsql-bugs >> Thread
2025-03-14 17:27:07 | Re: BUG #18848: DEREF_AFTER_NULL.EX.COND After having been compared to a NULL (Tom Lane)
core if ind_name is null, with or without an Assert. Given the lack of field