Re: Slow response to my query

From: Keith <keith(at)keithf4(dot)com>
To: Bzzzz <lazyvirus(at)gmx(dot)com>
Cc: Goke Aruna <goksie(at)gmail(dot)com>, Steven Pousty <steve(dot)pousty(at)gmail(dot)com>, pgsql-novice(at)lists(dot)postgresql(dot)org, Babatunde Adeyemi <barbietunnie(at)gmail(dot)com>
Subject: Re: Slow response to my query
Date: 2019-11-29 15:01:16
Message-ID: CAHw75vuDpf+XVPKotPTy7vDAqy2=NNDWdTsGR35JUORdKjOUQA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Fri, Nov 29, 2019 at 9:56 AM Bzzzz <lazyvirus(at)gmx(dot)com> wrote:

> On Fri, 29 Nov 2019 15:38:53 +0100
> Goke Aruna <goksie(at)gmail(dot)com> wrote:
>
> > Thanks Jean-Yves / Steven,
> > am using V12.
>
> Depending on the way you mostly use your columns, you can also do the
> opposite: store date/timestamp into "pieces" in different columns
> (century, month, day, hours, minutes, seconds, milliseconds, time zone
> shift) and reconstitute a whole date/ts into an auto-generated column.
>
> Sometimes, you have to break the rules, especially with a large number of
> rows, because pre-calculation is way better than post in this case.
>
> Depending on your needs, you might also be interested into that:
> https://severalnines.com/database-blog/guide-partitioning-data-postgresql
>
> BTW, don't leave us dry, share your progress and results *<;-)
>
> Jean-Yves
>

Please do not advise the use of inheritance/trigger based partitioning
anymore, especially on PG12. Partitioning is now part of core and is much
more easily managed that way

https://www.postgresql.org/docs/12/ddl-partitioning.html

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Bzzzz 2019-11-29 15:23:37 Re: Slow response to my query
Previous Message Bzzzz 2019-11-29 14:56:28 Re: Slow response to my query