Re: Slow planning, fast execution for particular 3-table query

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: David Wheeler <dwheeler(at)dgitsystems(dot)com>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>
Cc: Cameron Redpath <credpath(at)dgitsystems(dot)com>
Subject: Re: Slow planning, fast execution for particular 3-table query
Date: 2019-11-04 04:46:41
Message-ID: c22789f2c87c55827c03c5361db54b30d919eb98.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

David Wheeler wrote:
> I'm not sure what "unusually large" is, but they're all < 1mb which is a little larger
> than some of our other comparable databases (mostly <300kb) but seems reasonable to me.

I forgot the condition "AND n.nspname = 'pg_catalog'"...

But if all your tables are small, catalog bloat is probably not your problem.

Do you have many tables in the database? Partitioning?

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2019-11-04 05:00:59 Re: Slow planning, fast execution for particular 3-table query
Previous Message David Wheeler 2019-11-04 04:42:00 Re: Slow planning, fast execution for particular 3-table query