Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)
| От | Adrian Klaver |
|---|---|
| Тема | Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication) |
| Дата | |
| Msg-id | 942b979a-c5e8-40e7-bdec-0234a0e5a010@aklaver.com обсуждение исходный текст |
| Ответ на | Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication) (Bala M <krishna.pgdba@gmail.com>) |
| Ответы |
Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)
|
| Список | pgsql-general |
On 11/4/25 22:27, Bala M wrote: > Thank you all for your suggestions, > > Thanks for your quick response and for sharing the details. > After reviewing the options, the logical replication approach seems to > be the most feasible one with minimal downtime. > > However, we currently have 7 streaming replication setups running from > production, with a total database size of around 15 TB. Out of this, > there are about 10 large tables ranging from 1 TB (max) to 50 GB (min) > each, along with approximately 150+ sequences. > > Could you please confirm if there are any successful case studies or > benchmarks available for a similar setup? Since you have given minimal information in this post, I doubt there is really a way to compare to other situations. Collect the details you provided earlier in the thread for those folks getting to it just now. That would be: 1) Postgres versions on both ends 2) OS and versions on both ends. 3) Network distance between 'machines'. 4) The logical replication settings. > Additionally, please share any recommended parameter tuning or best > practices for handling logical replication at this scale. Since you have already started is that not already to late for this? > > Current server configuration: > > CPU: 144 cores > > RAM: 512 GB > > > Thanks & Regards > Krishna. > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: