we test again with the
performance-tuned PostgreSQL.
Hope we can contribute to improving PostgreSQL.
Thanks,
Jinho Jung
From: MichaelDBA
Sent: Monday, March 1, 2021 8:04 AM
To: Jung, Jinho
Cc: pgsql-performa...@postgresql.org
Subject: Re: Potential performa
# Performance issues discovered from differential test
Hello. We are studying DBMS from GeorgiaTech and reporting interesting queries
that potentially show performance problems.
To discover such cases, we used the following procedures:
* Install four DBMSs with the latest version (PostgreSQL, S
Hi Andres:
Could you please share your thoughts on QUERY 3?
The performance impact of this regression increases *linearly* on larger
databases. We concur with Andrew in that this is related to the lack of a
Materialize node and mis-costing of the Nested Loop Anti-Join.
We found more than 20 r
ead. We will not
report regressions related to NULLIF in the future.
### QUERY 1:
This regression is also not present in DEV head. We will validate our
regressions on DEV head in the future report.
Best,
Jinho Jung
From: Tom Lane
Sent: Saturday, February
th=20) (actual
time=0.000..0.000 rows=0 loops=30044)
One-Time Filter: false
Planning Time: 0.350 ms
Execution Time: 79.237 ms
________
From: Jeff Janes
Sent: Tuesday, February 12, 2019 1:03 PM
To: Jung, Jinho
Cc: pgsql-performa...@postgresql.org
Hello,
We are developing a tool called sqlfuzz for automatically finding performance
regressions in PostgreSQL. sqlfuzz performs mutational fuzzing to generate SQL
queries that take more time to execute on the latest version of PostgreSQL
compared to prior versions. We hope that these queries
