Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WDVeh-0005sK-0g for pgsql-performance@arkaria.postgresql.org; Wed, 12 Feb 2014 08:58:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WDVeg-0001mR-FY for pgsql-performance@arkaria.postgresql.org; Wed, 12 Feb 2014 08:58:54 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WDVee-0001mK-Vd for pgsql-performance@postgresql.org; Wed, 12 Feb 2014 08:58:53 +0000 Received: from pyrimidin.rz.uni-konstanz.de ([134.34.240.46]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WDVea-0000cy-Th for pgsql-performance@postgresql.org; Wed, 12 Feb 2014 08:58:52 +0000 Received: from vw002367.verwaltung.uni-konstanz.de (HELO PCKKoobs) ([134.34.168.196]) by mailhub.uni-konstanz.de with ESMTP/TLS/AES128-SHA; 12 Feb 2014 08:58:46 +0000 From: "Katharina Koobs" To: Subject: increasing query time after analyze Date: Wed, 12 Feb 2014 09:58:49 +0100 Message-ID: <005e01cf27d0$a52ec3e0$ef8c4ba0$@uni-konstanz.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_005F_01CF27D9.06F7E6D0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac8n0IQSKjTLxvzFRBiSRewGxGpH6w== Content-Language: de X-Pg-Spam-Score: -2.2 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org This is a multipart message in MIME format. ------=_NextPart_000_005F_01CF27D9.06F7E6D0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, We have still problems with our query time. After restoring the database the query time is about one minute. After an analyze the query time is about 70 minutes. We could discover one table which cause the problem. After analyzing this table the query time increases. We have made an explain plan before and after analyzing the table cifx. The plans can be found on After analyze: explain.depesz.com/s/HuZ Before analyze: explain.depesz.com/s/XWF Thanks a lot for your help! ------=_NextPart_000_005F_01CF27D9.06F7E6D0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

We have still = problems with our query time.

After restoring the = database the query time is about one = minute.

After an analyze the = query time is about 70 minutes.

We could discover one = table which cause the problem.

After analyzing this = table the query time increases.

We have made an = explain plan before and after analyzing the table cifx.

 

The = plans can be found on

 

After = analyze:

explain.depesz.com/s/<= span class=3DSpellE>HuZ

 

Before = analyze:

explain.depesz.com/s/X= WF

 

Thanks a = lot for your help!

 

 

 

 

------=_NextPart_000_005F_01CF27D9.06F7E6D0--