Re: query against pg_locks leads to large memory alloc

From: Dave Owens <dave(at)teamunify(dot)com>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: query against pg_locks leads to large memory alloc
Date: 2014-08-19 15:57:20
Message-ID: CA+OQrzh1fOgZ7WQDm+hwNh-32ONk5xvf7L5cbiz=9ycb0PdzcA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi Kevin,

Looking at pg_stat_all_tables and pg_stat_all_indexes on our four
databases we have:

1358 tables
1808 indexes

The above totals do not include template1, template0, or postgres
databases. We do not use partitioned tables. Only one database has a
meaningful level of concurrency (New Relic reports about 30k calls per
minute, from our main webapp). That database alone consists of 575
tables and 732 indexes.

Dave Owens

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2014-08-19 16:40:41 Re: query against pg_locks leads to large memory alloc
Previous Message Kevin Grittner 2014-08-19 11:38:52 Re: query against pg_locks leads to large memory alloc