The issue resolved with the latest HammerDBv4.2(HammerDB-4.2/src/postgresql/pgolap.tcl)
also they have added these lines in pgolap.tcl set sql(17) "CREATE INDEX LINEITEM_PART_SUPP_FKIDX ON LINEITEM (L_PARTKEY,| ------------------------------------------------------------------------- set sql(18) "CREATE INDEX ORDER_CUSTOMER_FKIDX ON ORDERS (O_CUSTKEY)" | ------------------------------------------------------------------------- set sql(19) "CREATE INDEX PARTSUPP_PART_FKIDX ON PARTSUPP (PS_PARTKEY)" | ------------------------------------------------------------------------- set sql(20) "CREATE INDEX PARTSUPP_SUPPLIER_FKIDX ON PARTSUPP (PS_SUPPKEY)| ------------------------------------------------------------------------- set sql(21) "CREATE INDEX SUPPLIER_NATION_FKIDX ON SUPPLIER (S_NATIONKEY)"| ------------------------------------------------------------------------- set sql(22) "CREATE INDEX CUSTOMER_NATION_FKIDX ON CUSTOMER (C_NATIONKEY)"| ------------------------------------------------------------------------- set sql(23) "CREATE INDEX NATION_REGIONKEY_FKIDX ON NATION (N_REGIONKEY)" | ------------------------------------------------------------------------- set sql(24)
In the older version HammerDB4.0 ,Indexes are not created when running Postgres TPCH
Sent from my iPhone
On 18-Aug-2021, at 3:49 PM, David Rowley <dgrowleyml@gmail.com> wrote:
On Wed, 18 Aug 2021 at 19:12, PG Bug reporting form <noreply@postgresql.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.
