time server - 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)
times the number of CPUs, you probably have a CPU overload problem and your solution may be to add a connection pooler between the client and the DB server
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 explain analyze it runs shows an execution time
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 is slightly less straightforward, as checkpointer and writer try to spread the load in time
Mailing lists >> pgsql-performance >> Thread
2025-02-27 16:54:02 | Slow performance of collate "en_US.utf8" (Alexey Borschev)
Time: 73.600 ms 3) The index search operations are also slower with en_US.utf8, but the difference is not as high. Please see attached file with test table and indexes, with tests on index
Mailing lists >> pgsql-performance >> Thread
2024-12-09 14:02:53 | PostgreSQL and a Catch-22 Issue related to dead rows (Lars Aksel Opsahl)
time, committing its progress and returning control to the caller. The caller must then trigger new jobs to complete the remaining tasks until done. If there were a way to remove dead rows without requiring
Mailing lists >> pgsql-performance >> Thread
2024-11-21 15:13:10 | could not send data to client: Connection reset by peer (James Pang)
time, but sometimes, database server side got error "could not send data to client: Connection
Mailing lists >> pgsql-performance >> Thread
2024-10-05 12:23:56 | Performance degradation in Index searches with special characters (Andrey Stikheev)
time increases drastically when these characters are used, whereas queries with alphabetic characters do not show such degradation. This behavior is observed both on macOS (using the official postgres:17 image via Docker
Mailing lists >> pgsql-performance >> Thread
2024-07-10 13:40:07 | Re: Query performance issue (Tom Lane)
time for some other session, unless you are running the server on seriously underpowered hardware
Mailing lists >> pgsql-performance >> Thread >> Search in thread (2)
2024-07-07 18:17:28 | Low performance between datacenters (Tamás PAPP)
server in another DC. The ping response time is 20ms. I measured the bandwidth via scp and it is more
Mailing lists >> pgsql-performance >> Thread >> Search in thread (2)
2024-07-05 02:15:42 | Re: Hash Right join and seq scan (David Rowley)
time which one that'll be and the partitions might drastically vary in size. The best I think we could do is take the total cost of those 10 and divide
Mailing lists >> pgsql-performance >> Thread
2024-06-27 10:45:04 | Re: Row level security (Andrew Okhmat)
time, site ID, or customer ID) so each partition stays manageable: Example: CREATE TABLE data ( id SERIAL PRIMARY KEY, site_id INT, customer_id INT, division_id INT, department_id INT, data_payload JSONB, created
Mailing lists >> pgsql-performance >> Thread
2024-06-17 09:35:02 | performance of sql and plpgsql functions (Julius Tuskenis)
server a function written in SQL language executes *100 times slower* than the one written
Mailing lists >> pgsql-performance >> Thread
2024-04-09 03:07:49 | [MASSMAIL]LWlock:LockManager waits (James Pang)
time, saw many sessions waiting on "LockManager". for example, pg_stat_activity show. It's a production server
Mailing lists >> pgsql-performance >> Thread
2024-01-26 04:22:58 | Re: I don't understand that EXPLAIN PLAN timings (Jean-Christophe Boggio)
server, which is running PG 14.10 on Debian 11, same work_mem, execution time is ~45ms
Mailing lists >> pgsql-performance >> Thread
2024-01-06 21:09:29 | Re: Slow GroupAggregate and Sort (Darwin Correa)
server) I no understand why if cooridnator not aree too busy, and I've already test with less shards, and time