Message-ID: <582219F1.9030502@nrc-cnrc.gc.ca>
Date: Tue, 8 Nov 2016 10:31:13 -0800
From: ghiureai <isabella.ghiurea@nrc-cnrc.gc.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: PG 9..5 index performance Q's
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Hi List,

  running PGSQL 9.5.1 ( EL7) ,
we are seeing a issues with one of our SQL statement getting the wrong 
plan once in a while ( large temp tables being generate, exec time   
takes  > 3 minutes compared with fastes plan < 1 min), we want to 
undestand why a new/ expensive plan is been used instead of efficient 
one, there are not data changes on the tables, any tips where to look?
Second , I would like to know if when re-creating one index ( non pk ) 
on  a large table with already existing indexes, are  All tables 
statistics  being re-generated? ( there is a way to control persistency 
of old stats?)

Isabella


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin