Skip site navigation (1) Skip section navigation (2)

Re: optimizing Postgres queries

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Teran <david(dot)teran(at)cluster9(dot)com>
Cc: Shridhar Daithankar <shridhar_daithankar(at)myrealbox(dot)com>,pgsql-performance(at)postgresql(dot)org
Subject: Re: optimizing Postgres queries
Date: 2004-01-05 15:22:32
Message-ID: 9966.1073316152@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
David Teran <david(dot)teran(at)cluster9(dot)com> writes:
> This is my bigger problem: i am using EOF (OR mapping tool) which frees 
> me more or less form writing a lot of SQL. If i need to typecast to use 
> an index then i have to see how to do this with this framework.

It's worth pointing out that this problem is fixed (at long last) in
CVS tip.  Ypu probably shouldn't expend large amounts of effort on
working around a problem that will go away in 7.5.

If you don't anticipate going to production for six months or so, you
could adopt CVS tip as your development platform, with the expectation
that 7.5 will be released by the time you need a production system.
I wouldn't recommend running CVS tip as a production database but it
should be plenty stable enough for devel purposes.

Another plan would be to use int4 columns for the time being with the
intention of widening them to int8 when you move to 7.5.  This would
depend on how soon you anticipate needing values > 32 bits, of course.

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: John SiracusaDate: 2004-01-05 16:19:04
Subject: Re: Use my (date) index, darn it!
Previous:From: Christopher Kings-LynneDate: 2004-01-05 15:15:27
Subject: Re: optimizing Postgres queries

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group