pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Justin <justin@emproshunts.com>
To: Shaun Thomas <sthomas@leapfrogonline.com>
To: pgsql-performance@postgresql.org
Subject: Re: need to speed up query
Date: Tue, 06 May 2008 12:22:11 -0500
Message-ID: <482093C3.1050604@emproshunts.com> (raw)
In-Reply-To: <1210092209.14833.32.camel@berners-lee>
References: <481FBC0D.7010509@emproshunts.com>
	<1210092209.14833.32.camel@berners-lee>

it worked it had couple missing parts but it worked and ran in 3.3 
seconds.  *Thanks for this *
i need to review the result and balance it to my results as the 
Accountant already went through and balanced some accounts by hand to 
verify my results

<<begin quote>>

 You might want to consider a
denormalized summary table that contains this information (and maybe
more) maintained by a trigger or regularly invoked stored-procedure and
then you can select from *that* with much less agony.

<<end quote>>

I just dumped the summary table because it kept getting out of balance 
all the time and was missing accounts that did not have transaction in 
them for given period.  Again i did not lay out the table nor the old 
code which was terrible and did not work  correctly.   I tried several 
times to fix the summary table  but to many  things allowed it to get 
out of sync.  Keeping the Ending and Beginning Balance correct was to 
much trouble and i needed to get numbers we can trust to the accountant. 

The developers of the code got credits and debits backwards so instead 
of fixing the code they just added code to flip the values on the front 
end.  Its really annoying.  At this point if i could go back 7 months 
ago i would not purchased this software if i had known what i know now.

I've had to make all kinds of changes i never intended to make in order 
to get the stuff to balance and agree. I've spent the last 3 months in 
code review fixing things that allow accounts to get out of balance and 
stop stupid things from happening, like posting GL Transactions into 
non-existing accounting periods.  the list of things i have to fix is 
getting dam long.

view thread (11+ messages)  latest in thread

Message-ID: <482093C3.1050604@emproshunts.com>
Permalink:  ../482093C3.1050604@emproshunts.com/
Also on:    postgresql.org/message-id/482093C3.1050604@emproshunts.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: justin@emproshunts.com, sthomas@leapfrogonline.com
  Subject: Re: need to speed up query
  In-Reply-To: <482093C3.1050604@emproshunts.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