| From: | Mircea Cadariu <cadariu(dot)mircea(at)gmail(dot)com> |
|---|---|
| To: | Madhumitha C <madhumitha(at)titan(dot)co(dot)in>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Inieya Dharshini <Inieya(at)titan(dot)co(dot)in>, Paarkavi K Subramaniam <paarkavik(at)titan(dot)co(dot)in> |
| Subject: | Re: Request for Guidance on Reducing PostgreSQL DB Restoration Time |
| Date: | 2025-08-11 00:10:21 |
| Message-ID: | ab48a5bd-55ab-4058-b808-c594dff0e190@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Madhumitha,
On 08/08/2025 23:27, Madhumitha C wrote:
>
> Could you please advise us on how we can optimize or reduce the
> restoration time?
I suggest asking this in the pgsql-performance mailing list. Have a look
at this first before posting:
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
Just off the cuff, you have to find the actual bottleneck first. In case
you already have evidence to rule out everything else, you can have a
look on this page for some options:
https://www.postgresql.org/docs/current/populate.html.
Kind regards,
Mircea Cadariu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2025-08-11 02:01:08 | Re: GB18030-2022 Support in PostgreSQL |
| Previous Message | Tom Lane | 2025-08-10 22:56:00 | Re: `pg_ctl init` crashes when run concurrently; semget(2) suspected |