Re: strange query behavior

From: "Tim Jones" <TJones(at)optio(dot)com>
To: "Matthew O'Connor" <matthew(at)zeut(dot)net>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: strange query behavior
Date: 2006-12-13 22:54:06
Message-ID: 47668A1334CDBF46927C1A0DFEB223D39F7AB0@mail.optiosoftware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

That's what I did and got 8.1.2 ... do you want gcc version etc 3.3.2
powerpc aix5.2

Tim Jones
Healthcare Project Manager
Optio Software, Inc.
(770) 576-3555

-----Original Message-----
From: Matthew O'Connor [mailto:matthew(at)zeut(dot)net]
Sent: Wednesday, December 13, 2006 5:51 PM
To: Tim Jones
Subject: Re: [PERFORM] strange query behavior

From psql perform: select version();
and send us that output.

Tim Jones wrote:
> Looks like 8.1.2
>
> Tim Jones
> Healthcare Project Manager
> Optio Software, Inc.
> (770) 576-3555
>
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Wednesday, December 13, 2006 5:37 PM
> To: Tim Jones
> Cc: pgsql-performance(at)postgresql(dot)org
> Subject: Re: [PERFORM] strange query behavior
>
> "Tim Jones" <TJones(at)optio(dot)com> writes:
>>> Which PG version is this exactly? Are you running with any
>>> nondefault planner parameters?
>
>> Version 8.1
>
> 8.1.what?
>
>> Here are the planner constraints I believe we changed
>> effective_cache_size and random_page_cost
>
> Those look reasonably harmless.
>
> My best bet at the moment is that you've got a pretty early 8.1.x
> release and are hitting one of the planner bugs that we fixed earlier
> this year. Not enough info to say for sure though.
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tomeh, Husam 2006-12-13 23:15:40 Re: Optimizing a query
Previous Message Tim Jones 2006-12-13 22:44:36 Re: strange query behavior