From: | Radoslav Nedyalkov <rnedyalkov(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | partitioned tables in high OLTP db |
Date: | 2022-04-27 11:38:41 |
Message-ID: | CANhtRiYrBTPfHcJCuZsZG=P6o-X5dZ_VQu1urGxXDeCagTWsYA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
I'd like to ask for your opinion and experience you might have with
partitioned tables on a production OLTP database.
We have a couple of tables reaching 1T and beyond and liked to have them
partitioned.
We built a pg14 full volume db.
To get an impression of the new performance we're executing most frequent
oltp queries
and comparing plans and execution times with the production "monolithic"
pg12 db.
For most of the queries we managed to get the optimal plans.
Execution times however increased , especially with planning time. Say from
1ms to 6ms/10ms
Typically there are joins between 3-6 partitioned (~40 partitions) tables.
That's the only thing we can examine . No load/stress tests are available.
Something else we should consider? (I saw lock contention has been noted
in the forum.)
Thank you for your time.
Regards,
Rado
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2022-04-27 12:37:59 | Re: Fresh eyeballs needed: input into error [FIXED] |
Previous Message | Laurenz Albe | 2022-04-27 10:51:11 | Re: errcodes.h and others not generated when compiling 13.6 on M1 Mac |