Home > mailing lists

PG Sharding - Mailing list pgsql-general

From	Matej
Subject	PG Sharding
Date	January 29, 2018 20:34:18
Msg-id	CAJB+8maToQO3nnCgJ-giJ6Wsu+210O6rYEP-KWq0RLG_HZnfWQ@mail.gmail.com Whole thread Raw
Responses	Re: PG Sharding (Melvin Davidson <melvin6925@gmail.com>) Re: PG Sharding (Rakesh Kumar <rakeshkumar464@aol.com>) Re: PG Sharding (Steven Lembark <lembark@wrkhors.com>)
List	pgsql-general

Hi Everyone.

We are looking at a rather large fin-tech installation. But as scalability requirements are high we look at sharding of-course.

I have looked at many sources for Postgresql sharding, but we are a little confused as to shared with schema or databases or both.

So far our understanding:

SCHEMA.

PROS:

- seems native to PG

- backup seems easier

- connection pooling seems easier, as you can use same connection between shard.

CONS:

- schema changes seems litlle more complicated

- heard of backup and maintenance problems

- also some caching problems.

DATABASE:

PROS:

- schema changes litlle easier

- backup and administration seems more robust

CONS:

- heard of vacuum problems

- connection pooling is hard, as 100 shards would mean 100 pools

So what is actually the right approach? If anyone could shed some light on my issue.

Thanks

pgsql-general by date:

From: Alban Hertroys
Date: 29 January 2018, 20:11:42
Subject: Re: Information on savepoint requirement within transctions

From: Melvin Davidson
Date: 29 January 2018, 20:44:45
Subject: Re: PG Sharding