[pgpool-general: 7499] Use pgpool as a way to split a large database

Kyaw Zin Win kz.win at seismic.com
Mon Apr 12 23:46:20 JST 2021

Dear List,

We have a 1.3TB a single postgres instance in one database that houses multiple tenants.  Each tenant is given a dedicated schema and we have about 1000 tenants or so.  We would like to split up the server/database into smaller instances with each holding different set of tenants.  So server 1 will have tenants number 0-100.

Is it possible to use pgpool between our application and multiple postgres instances in a way that application can connect to pgpool using a single connection string and pgpool do the right routing?  All my reading says that pgpool only routes to different backends for SELECT queries.  Upon reading the source code, I find `is_select_query` function; if I patch the function to just return true almost unconditionally, do you think pgpool will route any requests?  Can we rely on other pgpool config (such as routing to specific nodes based on database)  to make this possible?

We are also wondering whether we can leverage slony mode and load balancing.  Does pgpool distribute all queries (read and write) to all bankends in this mode?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20210412/97a712da/attachment.htm>

More information about the pgpool-general mailing list