cores - Search results in mailing lists
Mailing lists >> pgsql-performance >> Thread
2025-05-12 20:22:05 | Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17) (Andrei Lepikhov)
core patch. What's more, if, as you predict, it will work, it may provide
Mailing lists >> pgsql-performance >> Thread
2025-01-04 20:45:11 | Re: Question: consolidating strpos searches? (Tom Lane)
extension rather than trying to persuade people it belongs in core Postgres. regards, tom lane
Mailing lists >> pgsql-performance >> Thread
2024-11-11 12:41:01 | Re: Performance of Query 4 on TPC-DS Benchmark (Andrei Lepikhov)
core of the problem in accuracy of selectivity estimation. In this specific example I see lots
Mailing lists >> pgsql-performance >> Thread
2024-11-04 15:05:44 | Re: Postgresql 14/15/16/17 partition pruning on dependent table during join (Andrei Lepikhov)
core feature. But the idea of the extensibility of the clause deduction system looks spectacular
Mailing lists >> pgsql-performance >> Thread >> Search in thread (2)
2024-10-26 10:31:36 | Re: Unexpected Performance for the Function simplify_function (Ba Jinsheng)
Core CPU, 256GB RAM running Ubuntu 22.04
Best regards,
Jinsheng Ba
________________________________
From: Tom Lane
Mailing lists >> pgsql-performance >> Thread
2024-06-11 07:10:45 | Re: Distinct performance dropped by multiple times in v16 (Andrei Lepikhov)
should be discovered by the core developers. [1] https:///postgrespro/aqo -- regards, Andrei Lepikhov Postgres Professional
Mailing lists >> pgsql-performance >> Thread >> Search in thread (3)
2024-01-06 21:09:29 | Re: Slow GroupAggregate and Sort (Darwin Correa)
cores in my case I've tested with few shards and 1:1, 2:1 shards
Mailing lists >> pgsql-performance >> Thread
2023-12-27 13:15:23 | Parallel hints in PostgreSQL with consistent perfromance (mohini mane)
core: 1 Core(s) per socket: 16 Socket(s): 1 NUMA node(s): 1 Vendor
Mailing lists >> pgsql-performance >> Thread
2023-10-02 01:09:05 | Re: Unexpected termination looping over table. (Tom Lane)
core Postgres source code. I surmise that you're using some extension that isn't happy
Mailing lists >> pgsql-performance >> Thread
2023-09-12 03:06:12 | Re: Planning time is time-consuming (David Rowley)
core_yylex 1.18% postgres [.] lappend 1.15% postgres [.] initial_cost_nestloop 1.13% postgres [.] hash_search_with
Mailing lists >> pgsql-performance >> Thread
2023-08-29 09:38:05 | Re: Range partitioning query performance with date_trunc (vs timescaledb) (David Rowley)
that's a core code change, not something that you can do from SQL. David
Mailing lists >> pgsql-performance >> Thread
2023-08-10 08:36:12 | Partitioning update-heavy queue with hash partitions vs partial indexes (Dorian Hoxha)
core of the problem is that the system does not understand the relationship among the partial
Mailing lists >> pgsql-performance >> Thread
2023-06-17 21:42:48 | Re: Merge David and Goliath tables efficiently (nicolas paris)
loop ? It is pg 15.3, on 2 cores / 8GO / 2TO ssds, with defaults cloud provider parameters (RDS).
Mailing lists >> pgsql-performance >> Thread >> Search in thread (3)
2023-06-01 14:26:59 | Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA (Sergio Rus)
cores were at 1.00 GHz. I haven't listed all the cores, but I'm seeing
Mailing lists >> pgsql-performance >> Thread
2023-05-31 08:43:42 | Unaccounted regression from postgresql 11 in later versions (Bob Jolliffe)
core throughout indicating it is probably cpu bound rather than IO. The plan selected in both