Re: Looks like merge join planning time is too big, 55 seconds

From: Sergey Burladyan <eshkinkot(at)gmail(dot)com>
To: Thomas Reiss <thomas(dot)reiss(at)dalibo(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Looks like merge join planning time is too big, 55 seconds
Date: 2013-08-01 11:45:15
Message-ID: CAJ2ymdj7rEjJSTRa07PpQ2n3m9ZZXo_esmigKeYcZoZ9vjr5JA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Aug 1, 2013 at 2:04 PM, Thomas Reiss <thomas(dot)reiss(at)dalibo(dot)com>wrote:

> Le 01/08/2013 11:55, Sergey Burladyan a écrit :
> At first look, this reminds me some catalog bloat issue. Can you provide
> the result of these queries :
> SELECT pg_size_pretty(pg_table_size('pg_class')) AS size_pg_class;
> SELECT pg_size_pretty(pg_table_size('pg_attribute')) AS size_pg_attribute;
>

SELECT pg_size_pretty(pg_table_size('pg_class')) AS size_pg_class; --- '16
MB'
SELECT pg_size_pretty(pg_table_size('pg_attribute')) AS size_pg_attribute;
--- '63 MB'

--
Sergey Burladyan

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Sergey Burladyan 2013-08-01 14:30:39 Re: Looks like merge join planning time is too big, 55 seconds
Previous Message Sergey Burladyan 2013-08-01 11:27:14 Re: Looks like merge join planning time is too big, 55 seconds