| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Noppavong Chalermlapvaraboon <noppavong(dot)varaboon(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: extensive data use setting in production |
| Date: | 2025-06-16 05:37:44 |
| Message-ID: | 8a57af9dbb70c2b35471cd1cf8448ee59ff3215b.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, 2025-06-16 at 12:31 +0700, Noppavong Chalermlapvaraboon wrote:
> is postgres-sql can support
>
> data around 200-300 million rows around 4-5 table
> with query multiple joins and high read write
>
> concurrent user around 4000 connections
Sure.
> do you have strategy or setting to suggestion ?
- test your application well with realistic amounts of test data
- use a connection pool
- keep your database transactions very short
- tune your statements so that they are fast
- consider when you can discard old data and design partitioning accordingly
- don't use a cloud service
- implement good monitoring, including monitoring for your backup
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gambhir Singh | 2025-06-16 07:15:18 | alter the datatype of Partition Key |
| Previous Message | Noppavong Chalermlapvaraboon | 2025-06-16 05:31:33 | extensive data use setting in production |