Re: Slow response to my query

From: Bzzzz <lazyvirus(at)gmx(dot)com>
To: Goke Aruna <goksie(at)gmail(dot)com>
Cc: 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 14:56:28
Message-ID: 20191129155628.7a97343f@msi.defcon1.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

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

> On Fri, Nov 29, 2019 at 3:21 PM Bzzzz <lazyvirus(at)gmx(dot)com> wrote:
>
> > On Fri, 29 Nov 2019 12:09:04 +0100
> > Goke Aruna <goksie(at)gmail(dot)com> wrote:
> >
> > Oops, I forgot,
> >
> > as you're not using V.12, it might not be a bad idea to create new
> > columns and trigger(s) to pre-calculate all of the EXTRACT/2 you
> > need.
> >
> > Jean-Yves
> >

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Keith 2019-11-29 15:01:16 Re: Slow response to my query
Previous Message Goke Aruna 2019-11-29 14:38:53 Re: Slow response to my query