pg_attribute, pg_class, pg_depend grow huge in count and size withmultiple tenants.

Поиск
Список
Период
Сортировка
От samhitha g
Тема pg_attribute, pg_class, pg_depend grow huge in count and size withmultiple tenants.
Дата
Msg-id CAG5FJBVFp4TtEde-xn2hpYQKByFxPQChXitrLorwyiN71+cPyA@mail.gmail.com
обсуждение исходный текст
Ответы Re: pg_attribute, pg_class, pg_depend grow huge in count and sizewith multiple tenants.  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: pg_attribute, pg_class, pg_depend grow huge in count and sizewith multiple tenants.  (Jeff Janes <jeff.janes@gmail.com>)
Список pgsql-performance
Дерево обсуждения
Hi experts,

Our application serves multiple tenants. Each tenant has the schema with a few hundreds of tables and few functions.
We have 2000 clients so we have to create 2000 schemas in a single database.

While doing this, i observed that the catalog tables pg_attribute, pg_class, pg_depend grow huge in count and size.

Do you think this will be a challenge during execution of every query ? 

When Postgres parses an sql to find the best execution plan, does it scan any of these catalogs that could eventually take more time? 

Any other challenges you have come across or foresee in such cases ? 

Thanks,
Sammy. 

 

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

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNERQuery )
Следующее
От: Amarendra Konda
Дата:
Сообщение: Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNERQuery )