Re: [PERFORM] Fastest way / best practice to calculate "next birthdays"

2015-05-21 Thread Bosco Rama
On 05/20/15 20:22, David G. Johnston wrote: > On Monday, May 18, 2015, er.tejaspate...@gmail.com < > er.tejaspate...@gmail.com> wrote: > >> If I have to find upcoming birthdays in current week and the current week >> fall into different months - how would you handle that? >> > > Extract(week from

Re: [PERFORM] cluster on conditional index?

2012-08-15 Thread Bosco Rama
On 08/15/12 14:05, Josh Berkus wrote: > >> That actually makes sense to me. Cluster the rows covered by that >> index, let the rest fall where they may. I'm typically only accessing >> the rows covered by that index, so I'd get the benefit of the cluster >> command but wouldn't have to spend cycle

Re: [PERFORM] Poor query plan chosen in 9.0.3 vs 8.3.7

2011-05-05 Thread Bosco Rama
Hey Brian, Brian Connolly wrote: > (I had to send a follow up email due the length of email restrictions on the > mailing list.) A tip for when you have this problem in the future -- turn off html mail. It will reduce your email message length by 50% - 90%. HTH Bosco. -- Sent via pgsql-perfor

[PERFORM] perf problem with huge table

2010-02-10 Thread rama
Hi all, i am trying to move my app from M$sql to PGsql, but i need a bit of help :) on M$sql, i had certain tables that was made as follow (sorry pseudo code) contab_y date amt uid contab_yd date amt uid contab_ymd date amt uid and so on.. this was used to "solidif