cores - Search results in mailing lists
Mailing lists >> pgsql-hackers >> Thread
2025-06-19 08:59:04 | Support for 8-byte TOAST values (aka the TOAST infinite loop problem) (Michael Paquier)
core code and in core because all the places that touch external TOAST pointers need
Mailing lists >> pgsql-hackers >> Thread
2025-06-17 16:38:18 | Re: Add progressive backoff to XactLockTableWait functions (Xuneng Zhou)
core, 16 GB AMD system—and collected both profiling traces and hardware-counter metrics. 1. Hardware
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (2)
2025-06-13 19:41:45 | Re: CREATE DATABASE command for non-libc providers (Daniel Verite)
core, although only for non-digits. Patch syncs support digits and nondigits in both hostname
Mailing lists >> pgsql-hackers >> Thread
2025-06-10 19:39:48 | Re: [PATCH v1] Add pg_stat_multixact view for multixact membership usage monitoring (Andrew Johnson)
core observability problem. I'm happy to keep discussing what the best approach for the community
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (2)
2025-06-10 10:30:18 | Re: [PATCH] PGSERVICEFILE as part of a normal connection string (Michael Paquier)
Core libpq changes with API and tests. - psql changes. +# "service" param included service file (invalid
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (3)
2025-06-09 00:49:20 | Re: Sanding down some edge cases for PL/pgSQL reserved words (Tom Lane)
core grammar. * Currently, the following words are reserved here but not in the core: * BEGIN
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (7)
2025-06-07 19:22:10 | Re: [PATCH] Re: Proposal to Enable/Disable Index using ALTER INDEX (Sami Imseih)
core, or should this be delegated to other tools in the ecosystem, like pg_hint
Mailing lists >> pgsql-hackers >> Thread
2025-06-07 00:48:18 | md5 password deprecation might cause problems with PgBouncer setups (Jelte Fennema-Nio)
core that PgBouncer is running on, the only way out is complicating your setup with
Mailing lists >> pgsql-hackers >> Thread
2025-06-06 10:00:05 | Proposal: Global Index for PostgreSQL (Dilip Kumar)
core idea of partitioning. However, they become essential when business needs dictate partitioning data on one key while
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (2)
2025-06-06 06:38:45 | Enhancing PostgreSQL Management and Observability in Cloud Environments (sreekanta reddy 1996)
cores: Number of CPU cores • RAM: Total available memory • os_uptime: OS uptime since the last
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (3)
2025-06-05 11:16:35 | Re: [19] Proposal: function markers to indicate collation/ctype sensitivity (Peter Eisentraut)
core or third-party, do you need to update, versus having a negative/opt-out approach. My conclusion
Mailing lists >> pgsql-hackers >> Thread
2025-06-02 09:01:30 | Re: Batch TIDs lookup in ambulkdelete (John Naylor)
core (or maybe just the tests?). It seems like we could just change the API for it rather
Mailing lists >> pgsql-hackers >> Thread
2025-05-30 14:30:39 | Optimize shared LWLock acquisition for high-core-count systems (Zhou, Zhiguo)
core-count systems. During performance analysis of HammerDB/TPCC (192 virtual users, 757 warehouses) on a 384-vCPU
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (2)
2025-05-26 22:36:14 | Re: Fixing memory leaks in postgres_fdw (Tom Lane)
core code will filter the - * statements we return according to those lists anyway. But it - * should
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (7)
2025-05-26 02:44:48 | Re: Non-reproducible AIO failure (Thomas Munro)
core?! I doubt it ... I kinda wonder if the debugger might be confused about libsystem