| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Hari Krishna Sunder <hari(dot)db(dot)pg(at)gmail(dot)com> |
| Cc: | 杨伯宇(长堂) <yangboyu(dot)yby(at)alibaba-inc(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 回复：Re: 回复：Re: speed up pg_upgrade with large number of tables |
| Date: | 2025-01-22 20:49:52 |
| Message-ID: | Z5FZ8BKxTNH9bxKM@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jan 19, 2025 at 03:57:18PM -0800, Hari Krishna Sunder wrote:
> The restore side speedups suggested by Yang seem reasonable and can
> potentially speed up the process. We can even go a bit further by starting
> the new postgres in a --binary-upgrade mode and skip some of these locks
> completely.
I am curious about what kind of speedup we can expect with these patches.
IMHO some benchmarking results would be useful.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2025-01-22 21:13:24 | Re: Proposal: "query_work_mem" GUC, to distribute working memory to the query's individual operators |
| Previous Message | Tomas Vondra | 2025-01-22 20:48:51 | Re: Proposal: "query_work_mem" GUC, to distribute working memory to the query's individual operators |