Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mH2P3-00061Q-O0 for pgsql-bugs@arkaria.postgresql.org; Fri, 20 Aug 2021 11:09:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mH2OW-0007Ns-NH for pgsql-bugs@arkaria.postgresql.org; Fri, 20 Aug 2021 11:09:04 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mGy4g-0001oQ-AN for pgsql-bugs@lists.postgresql.org; Fri, 20 Aug 2021 06:32:18 +0000 Received: from mail-pj1-x102d.google.com ([2607:f8b0:4864:20::102d]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mGy4e-00026c-0u for pgsql-bugs@lists.postgresql.org; Fri, 20 Aug 2021 06:32:17 +0000 Received: by mail-pj1-x102d.google.com with SMTP id j1so6670627pjv.3 for ; Thu, 19 Aug 2021 23:32:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=BxGXnlfzg+RKuXBOJ/vLKbJE7gvgmeWhCv1JZ0fXfBo=; b=qBx9XUl2x7RUv9UjPHHhs17YxdDfH1zCqB1pGvmSRswGPilIEKDArTHFO/lRG3ZoLp ruMvWobROHJzlhuSA12Of/DK6sEqJTUGaQBJ4LypMQvblTpSKL9CRy+M/tgnleVvWdxV YHfg8/GDTrVlrCBN6n3j9TGJ6ZyVhCJVkq7pPd+PMbg5yCvC06E5Wh+ZZYb7egTjqwXY qURVh4lr8TRyY98UgtZKbPRMK8Qo6M/4fCIayJ/Vm76vPGsBQq/hTFiCYtkH5MdbmqNq lDlJJP1kpw38uI/j62hzhrI4v7jKH0soS5Bi2gWk7LqEpo3pQOiwNTcbNGyNZDzADaFh 2EyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=BxGXnlfzg+RKuXBOJ/vLKbJE7gvgmeWhCv1JZ0fXfBo=; b=th/Au/P1kvr6EvuW9XIsDDRIcTCDs6erjDfdP44V/lfYqhIl+9ztJde/EOPCDZYjnv 7T/P48GPxDs+cYUseWPMONcNQH5te+DevhX2psTA4jRBI4Vaka4wPxGfDuwpBjK085Ur 9HOCbYFNfTOXgJoegwRXxu14gKe2Mutva1Q+wm7PjMc13gAWoyaftxaHeNt+oDD3IUKH iUdsbS0DlU6KflN64nhWOx4eclP6un4KQTauK9IfqEPbZ/PFul24nb2XBDrdV1AR/+NS ZmqyxA3Be7hxW0I+ojyPKJpLz/fX82ftkG/qoyIxde135zKOGLKrjJD+KsK/Msk3uBfV /R+w== X-Gm-Message-State: AOAM5311pWMrWzkgYj8ifGubdKr/brGNg/VM82o7ORVYUoiiKLzrYR50 V+d+QTJpNYRcPDHzBJ9XUJE= X-Google-Smtp-Source: ABdhPJykjszUwzDeOq3Jxq65zBmWcnPmU3GRvTrs2LQL88IZXN6luiPt4PASkjYjhx+GLs3PNTkSAg== X-Received: by 2002:a17:902:d343:b029:12d:3624:d997 with SMTP id l3-20020a170902d343b029012d3624d997mr15306878plk.79.1629441134673; Thu, 19 Aug 2021 23:32:14 -0700 (PDT) Received: from [192.168.1.48] ([136.185.96.85]) by smtp.gmail.com with ESMTPSA id w130sm5634756pfd.118.2021.08.19.23.32.13 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 19 Aug 2021 23:32:14 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-463621CB-CDE2-404F-9874-93E9BB337E57 Content-Transfer-Encoding: 7bit From: anil bommareddy Mime-Version: 1.0 (1.0) Subject: Re: BUG #17153: tpch-hammerdb-Query21 Date: Fri, 20 Aug 2021 12:02:11 +0530 Message-Id: <26241341-EB9F-40BE-8ABF-C9C93C27A54D@gmail.com> References: Cc: PostgreSQL mailing lists In-Reply-To: To: David Rowley X-Mailer: iPhone Mail (18D70) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail-463621CB-CDE2-404F-9874-93E9BB337E57 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 Postg= res TPCH Sent from my iPhone > On 18-Aug-2021, at 3:49 PM, David Rowley wrote: >=20 > =EF=BB=BFOn Wed, 18 Aug 2021 at 19:12, PG Bug reporting form > 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 >=20 > 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. >=20 > How long did those queries take to run in v12? >=20 > We'd also need: > * EXPLAIN ANALYZE output for each query on each version > * postgresql.conf from each version. > * schema from each version. >=20 > David --Apple-Mail-463621CB-CDE2-404F-9874-93E9BB337E57 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable The issue resolved with the latest HammerDB= v4.2(HammerDB-4.2/src/postgresql/pgolap.tcl)

also they have added thes= e lines in pgolap.tcl
set sql(17) "CREATE INDEX LINEITEM_PART_SUPP_FKIDX ON LINEITEM (L_PARTKEY,| &= nbsp;-----------------------------------------------------------------------= --
  set sql(18) "CREATE INDEX ORDER_CUSTOMER_FKIDX ON ORDERS (O_CUST= KEY)"     |  --------------------------------------= -----------------------------------
  set sql(19) "CREATE INDEX PARTSUPP_PART_FKIDX ON PARTSUPP (PS_PA= RTKEY)"   |  ------------------------------------------------= -------------------------
  set sql(20) "CREATE INDEX PARTSUPP_SUPPLIER_FKIDX ON PARTSUPP (P= S_SUPPKEY)|  ----------------------------------------------------------= ---------------
  set sql(21) "CREATE INDEX SUPPLIER_NATION_FKIDX ON SUPPLIER (S_N= ATIONKEY)"|  ----------------------------------------------------------= ---------------
  set sql(22) "CREATE INDEX CUSTOMER_NATION_FKIDX ON CUSTOMER (C_N= ATIONKEY)"|  ----------------------------------------------------------= ---------------
  set sql(23) "CREATE INDEX NATION_REGIONKEY_FKIDX ON NATION (N_RE= GIONKEY)" |  ----------------------------------------------------------= ---------------
  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> wrot= e:

=EF=BB= =BFOn Wed, 18 Aug 2021 at 19:12, PG Bug reporting form
<noreply@postgresql.org> wrote:
<= span>In PostgreSQL13.3 , tried to run tpch with Hammedb benchmark environmen= t .
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 PostgreSQ= L version like
12.x

There's really not much to go o= n here. We'd need much more detail than
you've provided to b= e able to identify if there are any bugs.

H= ow long did those queries take to run in v12?

We'd also need:
* EXPLAIN ANALYZE output for each query o= n each version
* postgresql.conf from each version.* schema from each version.

David
= --Apple-Mail-463621CB-CDE2-404F-9874-93E9BB337E57--