| From: | 熊艳辉 <yanhui(dot)xiong(at)enmotech(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | how to ensure parallel restore consistency ? |
| Date: | 2023-08-08 01:54:38 |
| Message-ID: | tencent_27AFC0EB2E64146062C2E769@qq.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
PG version 15.4
i read code about pg_dump & pg_restore, there is an option -j/--jobs related with parallel,
i have questions about parallel dump & restore
1) In pg_dump when running parallel dump, it can ensure dump data consistency using synchronized snaphot,
why should it start a trasaction in every parallel jobs, also set isolation level ,read only, and no need commit trasaction
2) In pg_restore there are no actions same with pg_dump under parallel mode, how to ensure restore data consistency?
no trasaction and no commit action
3) when we do dump or restore under parallel mode, should we set whole database read-only(write behavior forbidden??)
发自我的企业微信
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-08-08 01:57:43 | Re: pg_upgrade fails with in-place tablespace |
| Previous Message | David Rowley | 2023-08-08 01:53:30 | Re: 2023-08-10 release announcement draft |