| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | anilbommareddy09(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17153: tpch-hammerdb-Query21 |
| Date: | 2021-08-18 10:19:06 |
| Message-ID: | CAApHDvoQ7QXg3EV9Qy0dS1bcKxuWr02xTNOpJewOGfeib9T=rg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 18 Aug 2021 at 19:12, PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> In PostgreSQL13.3 , tried to run tpch with Hammedb benchmark environment .
> Observed Q17,Q20, Q21 executed long period time .
> Q17--->5000 seconds
> Q20--->6124 seconds
> Q21--->53271 seconds.
> the issue was may not observe with pervious/older PostgreSQL version like
> 12.x
There's really not much to go on here. We'd need much more detail than
you've provided to be able to identify if there are any bugs.
How long did those queries take to run in v12?
We'd also need:
* EXPLAIN ANALYZE output for each query on each version
* postgresql.conf from each version.
* schema from each version.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2021-08-18 11:44:00 | Re: BUG #17148: About --no-strict-names option and --quiet option of pg_amcheck command |
| Previous Message | Daniel Gustafsson | 2021-08-18 09:31:51 | Re: BUG #17149: About --skip option of pg_amcheck command |