Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e9cAR-0001Wz-1X for pgsql-performance@arkaria.postgresql.org; Tue, 31 Oct 2017 19:25:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e9cAQ-0006ke-Cd for pgsql-performance@arkaria.postgresql.org; Tue, 31 Oct 2017 19:25:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e9cAP-0006jz-FQ for pgsql-performance@postgresql.org; Tue, 31 Oct 2017 19:25:41 +0000 Received: from mail-oi0-x242.google.com ([2607:f8b0:4003:c06::242]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1e9cAL-0003Jx-TG for pgsql-performance@postgresql.org; Tue, 31 Oct 2017 19:25:40 +0000 Received: by mail-oi0-x242.google.com with SMTP id a132so87033oih.11 for ; Tue, 31 Oct 2017 12:25:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2pkmRn+SrYX+GNBmtHN/YuPSIea73yJk6dqBdO8Vv40=; b=KHQxptUSYDWwvKelIGBqQa7aSoQlNPITd9qxmzlsKk/kWEzCEEuX0JZNNU4H3w2URB 4U2Eet3kuGs+LFgaVowRguO7XpQII9lSiT4XbkFVskDz4eGeoUvm/ysSuYURyM8UMhkC bsDlRtEguJy+rXD4L8zIZfhDjLCqiHHv2qfu9eAGTBJAW6KsV52osFp7HuqL8EBfL4TZ tUqDJrptPvnGwYuZVGPKSVQ5Hx9hT/Ab/Znbd90ENMBBxH2U6VORLUP2Jxtw4+Ci9I1G ZLaNupha63PrrvucaIke2/XaY0uo0ZO5JnPWEMDhuBYmnl2+UA4jkqB7iva8kYizf2B9 +w1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2pkmRn+SrYX+GNBmtHN/YuPSIea73yJk6dqBdO8Vv40=; b=LqVyvh0NlNF6Y6IiMK3GP3xpez8z8KSSantId5ANXEE12lwzdcWhfV07g+nVtLlO8L OKo12yHIH/h3LWi2fwIt3jEg0Sgq4OGjqUy3i4i2coJjS8h3VcmtfSENGeicAtt9MSOX rJpjX7aZGVv1veZa6osXwyRUm6NT7JtVMpwK3Ey6JBoUDWCADBgDH6Mlark1W1Xq6Yoc +lqrU/3FVRhn4kw1UWYRtRCkItmhps/x0ozgZ2/MkMmfs6N9tjwRIuDzYPLbMH1wnxPw 803eteIlk7r46ySiWKE8/hK2249YkBip0Z/ALo0VfahnDAvdWsqqqnmbExAnxGJfiyka 3bTw== X-Gm-Message-State: AMCzsaV/JiWooJGY56F6MOcaIxtDpURMYHSMFmxSWmAMr+7UaAIoI83W HQLZTdXBwm++wX+oFboxxOYsHC/7wDA8r/O2TpA= X-Google-Smtp-Source: ABhQp+TFyne+ev8twZiPkxy2Ajwj+pSinw1DMQsnD6aAyWdW3bQIMj5ayGfTOWc5v/Gm2I9QfmrHmL8y8SJz2Nq2Eas= X-Received: by 10.202.222.197 with SMTP id v188mr1448024oig.294.1509477936479; Tue, 31 Oct 2017 12:25:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.66.157 with HTTP; Tue, 31 Oct 2017 12:25:36 -0700 (PDT) In-Reply-To: References: From: Alexandre de Arruda Paes Date: Tue, 31 Oct 2017 17:25:36 -0200 Message-ID: Subject: Re: Index-Advisor Tools To: Neto pr Cc: Anthony Sotolongo , postgres performance list Content-Type: multipart/alternative; boundary="001a113d5a7e3342a1055cdcb8c1" List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org --001a113d5a7e3342a1055cdcb8c1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I will be very happy with a tool(or a stats table) that shows the most searched values from a table(since a statistic reset). i.e.: table foo (id int, year int) top 3 searched value for year field: 2017(500x), 2016(300x), 2015(55x) With this info we can create partial indexes or do a table partitioning. 2017-10-31 15:25 GMT-02:00 Neto pr : > Thanks for reply Antony. > But from what I've read, HYPOPG only allows you to create hypothetical > indexes, so the DBA can analyze if it brings benefits. > What I would like is a tool that from a SQL Query indicates which indexes > would be recommended to decrease the response time. > > Best Regards > Neto > > 2017-10-31 15:19 GMT-02:00 Anthony Sotolongo : > >> Hi Neto, maybe HypoPG >> Can help you: >> >> https://github.com/dalibo/hypopg >> >> El 31 oct. 2017 2:13 PM, "Neto pr" escribi=C3=B3: >> >>> >>> Hello All I'm researching on Index-Advisor Tools to be applied in SQL >>> queries. At first I found this: - EnterpriseDB - >>> https://www.enterprisedb.com/docs/en/9.5/asguide/EDB_Postgre >>> s_Advanced_Server_Guide.1.56.html Someone would know of other tools for >>> this purpose. I'd appreciate it if you can help me. >>> >>> Best Regards >>> Neto >>> >> > --001a113d5a7e3342a1055cdcb8c1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I will be very happy with a tool(or a stats table) that sh= ows the most searched values from a table(since a statistic reset).=C2=A0 i= .e.:

table foo (id int, year int)

top 3 searched value for year field: 2017(500x), 2016(300x), 2015(55x)

With this info we can create partial indexes or do = a table partitioning.



2017-10-31 15:25 GMT-02:00 = Neto pr <netopr9@gmail.com>:
Thanks for reply Antony.=C2=A0
But fro= m what I've read, HYPOPG only allows you to create hypothetical indexes= , so the DBA can analyze if it brings benefits.
What I would like= is a tool that from a SQL Query indicates which indexes would be recommend= ed to decrease the response time.

Best Regards
Neto

2017-10-31 15:19 GMT-02:00 Anthony Sotolong= o <asotolongo@gmail.com>:
Hi Neto,=C2=A0 maybe=C2=A0

HypoPG

Can h= elp you:


El 31 oct. 2017 2:13 PM, "Neto pr" <netopr9@gmail.com> = escribi=C3=B3:

Hello All I'm researching on Index-Advisor Tools to be applied in SQL queries. At first I found this: - EnterpriseDB - https://w= ww.enterprisedb.com/docs/en/9.5/asguide/EDB_Postgres_Advanced_Ser= ver_Guide.1.56.html Someone would know of other tools for this purpose. I'd appreciate it i= f you can help me.

Best Regards
= Net= o


--001a113d5a7e3342a1055cdcb8c1--