Re: Looks like merge join planning time is too big, 55 seconds - Mailing list pgsql-performance

From Sergey Burladyan
Subject Re: Looks like merge join planning time is too big, 55 seconds
Date
Msg-id CAJ2ymdj7rEjJSTRa07PpQ2n3m9ZZXo_esmigKeYcZoZ9vjr5JA@mail.gmail.com
Whole thread Raw
In response to Re: Looks like merge join planning time is too big, 55 seconds  (Thomas Reiss <thomas.reiss@dalibo.com>)
List pgsql-performance
On Thu, Aug 1, 2013 at 2:04 PM, Thomas Reiss <thomas.reiss@dalibo.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

pgsql-performance by date:

Previous
From: Sergey Burladyan
Date:
Subject: Re: Looks like merge join planning time is too big, 55 seconds
Next
From: Sergey Burladyan
Date:
Subject: Re: Looks like merge join planning time is too big, 55 seconds