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

Re: PG planning randomly ?

From: "Laurent Raufaste" <analogue(at)glop(dot)org>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: PG planning randomly ?
Date: 2008-02-26 17:12:07
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
2008/2/26, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> What PG version is this?
>  If it's 8.2 or later then increasing the stats target for _comment.path
>  to 100 or more would likely help.

I'm using PG 8.2.4.
We are using 100 as default_statistics_target by default and all our
column are using this value:
# SELECT attname,attstattarget FROM pg_attribute WHERE attrelid=16743
AND attname='path' ;
 attname | attstattarget
 path    |            -1

I tried increasing the stats target with the command:
SET default_statistics_target=1000 ;
That's the command I launched before executing the ANALYZE showed in
the previous mail.
The ANALYZE were longer to complete, but it did not change the planner
behavior (sometimes right, sometimes wrong).

I did not try setting up the target stats directly using an ALTER
TABLE because it implies some LOCK on our replication cluster. Do you
think the planner will act differently by using an ALTER TABLE rather
then just the "SET default_statistics_target" command ?

If so, I will try it =)


Laurent Raufaste

In response to


pgsql-performance by date

Next:From: Tom LaneDate: 2008-02-26 17:43:26
Subject: Re: LISTEN / NOTIFY performance in 8.3
Previous:From: Kynn JonesDate: 2008-02-26 16:49:21
Subject: Re: Q on views and performance

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