pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Jeff Janes <jeff.janes@gmail.com>
To: Victor Yegorov <vyegorov@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Estimates on partial index
Date: Thu, 18 Aug 2016 17:01:05 -0500
Message-ID: <4c143963-7fc1-b1b8-e605-35b695969830@BlueTreble.com> (raw)
In-Reply-To: <CAMkU=1zyFp3JCFsj26J7suTfA1OJ-+VxSwf1q1FpicG=E7Eubg@mail.gmail.com>
References: <CAGnEbohwiUPY1-x6=u4bJuAvnhr1oNYP_oTpWOPVcdCsyisjyw@mail.gmail.com>
	<CAMkU=1ymn6xjf37LS6BAuuJE3PhCogRszzSBbTKcNFttjkKcmA@mail.gmail.com>
	<CAGnEbogE7gUtAAD1b4KT_xHdFqu=dcNK4gr_V+YbTAbfbp7roQ@mail.gmail.com>
	<CAGnEbogdo7ji_UK7h4bU_8iA320B1id5h=7JAYQWUhR5s2H=Bg@mail.gmail.com>
	<CAMkU=1zyFp3JCFsj26J7suTfA1OJ-+VxSwf1q1FpicG=E7Eubg@mail.gmail.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

On 8/18/16 3:06 PM, Jeff Janes wrote:
> If you can come up with a data generator which creates data that
> others can use to reproduce this situation, we can then investigate it
> in more detail.

BTW, the easy fix to this is most likely to create an index on due_date 
WHERE is_current. Or perhaps partition the table so non-current rows 
don't live with current ones. I'm not a fan of mixing history tracking 
in with the main table, because it leads to problems like this.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



view thread (10+ messages)  latest in thread

Message-ID: <4c143963-7fc1-b1b8-e605-35b695969830@BlueTreble.com>
Permalink:  ../4c143963-7fc1-b1b8-e605-35b695969830@BlueTreble.com/
Also on:    postgresql.org/message-id/4c143963-7fc1-b1b8-e605-35b695969830@BlueTreble.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: Jim.Nasby@BlueTreble.com, jeff.janes@gmail.com, vyegorov@gmail.com
  Subject: Re: Estimates on partial index
  In-Reply-To: <4c143963-7fc1-b1b8-e605-35b695969830@BlueTreble.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox