servers - Search results in mailing lists
Mailing lists >> pgsql-performance >> Thread
2025-04-12 01:43:10 | Re: many sessions wait on LWlock WALWrite suddenly (MichaelDBA)
server. This is all due to the nature of how PG is architected: every connection
Mailing lists >> pgsql-performance >> Thread
2025-04-09 17:27:08 | Question on what Duration in the log (Vitale, Anthony, Sony Music)
Server Side Prepared statement (i.e S_381) which took 6.5 seconds. When I run the Sql using
Mailing lists >> pgsql-performance >> Thread
2025-04-06 17:05:18 | Re: Memory Not Released After Batch Completion – Checkpointer/Background Writer Behavior , postgres 15 (Евгений Чекан)
server. This is totally OK and should help (generally) with the performance. The “idle” thing
Mailing lists >> pgsql-performance >> Thread
2025-03-20 22:57:45 | Re: parallel pg_restore blocks on heavy random read I/O on all children processes (Dimitrios Apostolou)
server having its own deduplication and compression. Further questions: * Does the same happen in an uncompressed
Mailing lists >> pgsql-performance >> Thread
2025-03-06 10:39:17 | Asking for OK for a nasty trick to resolve PG CVE-2025-1094 i (Abraham, Danny)
Server\pgsql\bin>postgres -V postgres (PostgreSQL) 15.3 C:\Program Files\BMC Software\Control-M Server
Mailing lists >> pgsql-performance >> Thread
2025-02-27 16:54:02 | Slow performance of collate "en_US.utf8" (Alexey Borschev)
SERVER|/usr/include/postgresql/17/server | |LIBDIR |/usr/lib/x86_64-linux-gnu | |PKGLIBDIR |/usr/lib/postgresql/17/lib | |LOCALEDIR
Mailing lists >> pgsql-performance >> Thread
2024-12-09 14:02:53 | PostgreSQL and a Catch-22 Issue related to dead rows (Lars Aksel Opsahl)
server not used by others also. Yes there are very good reason for the way removal
Mailing lists >> pgsql-performance >> Thread
2024-11-21 15:13:10 | could not send data to client: Connection reset by peer (James Pang)
server side got error "could not send data to client: Connection reset by peer". any idea
Mailing lists >> pgsql-performance >> Thread
2024-11-13 10:14:18 | Re: tds_fdw : Severe performance degradation from postgresql 10.23 to 16.4 (Achilleas Mantzios - cloud)
just a simple query run on a FOREIGN TABLE living in a MS SQL Server.
Mailing lists >> pgsql-performance >> Thread
2024-10-05 12:23:56 | Performance degradation in Index searches with special characters (Andrey Stikheev)
server running PostgreSQL in an LXC container. Here is a minimal example: testdb=# SELECT version
Mailing lists >> pgsql-performance >> Thread
2024-09-11 10:00:38 | Re: many backends hang on MultiXactOffsetSLRU (James Pang)
server, we see thousands of session hang on ‘MultixactOffsetSLRU" but they are in " bind " stage
Mailing lists >> pgsql-performance >> Thread
2024-08-23 00:47:58 | checking for a NULL date in a partitioned table kills performance (accidentally sent to the (Sbob)
server is an aurora postgresql instance with 128GB of ram and 16 vcpu's The shared
Mailing lists >> pgsql-performance >> Thread
2024-07-31 05:41:41 | Re: logical replication out of memory (khan Affan)
server must be out of memory, Such a process ran out of memory while handling
Mailing lists >> pgsql-performance >> Thread
2024-07-10 13:40:07 | Re: Query performance issue (Tom Lane)
server on seriously underpowered hardware. It could be that you've misinterpreted your data, and what
Mailing lists >> pgsql-performance >> Thread >> Search in thread (2)
2024-07-07 20:23:41 | Re: Low performance between datacenters (Fernando Hevia)
server. For example, establishing a connection has a bit of back and forth dialogue going