Postgres Pro
Downloads
Home   >   mailing lists

Re: query against pg_locks leads to large memory alloc - Mailing list pgsql-performance

From Dave Owens
Subject Re: query against pg_locks leads to large memory alloc
Date
Msg-id CA+OQrzh1fOgZ7WQDm+hwNh-32ONk5xvf7L5cbiz=9ycb0PdzcA@mail.gmail.com
Whole thread Raw
In response to Re: query against pg_locks leads to large memory alloc  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: query against pg_locks leads to large memory alloc  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-performance
Tree view 
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

pgsql-performance by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: query against pg_locks leads to large memory alloc
Next
From: Kevin Grittner
Date:
Subject: Re: query against pg_locks leads to large memory alloc