Re: query against pg_locks leads to large memory alloc

Поиск
Список
Период
Сортировка
От Dave Owens
Тема Re: query against pg_locks leads to large memory alloc
Дата
Msg-id CA+OQrzh1fOgZ7WQDm+hwNh-32ONk5xvf7L5cbiz=9ycb0PdzcA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: query against pg_locks leads to large memory alloc  (Kevin Grittner <kgrittn@ymail.com>)
Ответы Re: query against pg_locks leads to large memory alloc  (Kevin Grittner <kgrittn@ymail.com>)
Список 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

В списке pgsql-performance по дате отправления:

Предыдущее
От: Kevin Grittner
Дата:
Сообщение: Re: query against pg_locks leads to large memory alloc
Следующее
От: Kevin Grittner
Дата:
Сообщение: Re: query against pg_locks leads to large memory alloc