Ken Tanzer writes:
> On Sat, Jul 20, 2019 at 7:46 AM Tom Lane wrote:
>> and then to add insult to injury, has to search pg_description a second
>> time for each hit.
> Not sure if I'm understanding this correctly, but are you saying that
> because col_description() is specified in two places in
On Sat, Jul 20, 2019 at 7:46 AM Tom Lane wrote:
> But if you do so manually you'll end up with something like
>
> SELECT c.relname AS table, a.attname AS column, d.description AS comment
> FROM
> pg_catalog.pg_attribute a JOIN pg_catalog.pg_class c ON a.attrelid =
> c.oid
> LEFT JOIN pg_catal
Ken Tanzer writes:
> Hi. I've got an app that queries pg_catalog to find any table columns that
> have comments. After setting up PgBadger, it was #2 on my list of time
> consuming queries, with min/max/avg duration of 199/2351/385 ms (across
> ~12,000 executions logged).
> I'm wondering if ther
