| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Alexander Shutyaev" <shutyaev(at)gmail(dot)com> |
| Cc: | "Andres Freund" <andres(at)anarazel(dot)de>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Adrian Klaver" <adrian(dot)klaver(at)aklaver(dot)com>,"pgsql-general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade and wraparound |
| Date: | 2018-06-27 09:43:45 |
| Message-ID: | 3987660e-ff1a-47cb-bf44-52cfd3029cfb@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alexander Shutyaev wrote:
> Is there any hope the issue with pg_upgrade can be resolved? If not,
> could you give me some hints as to how can I decrease time needed
> for pg_dumpall | psql?
Not sure about the larger problem, but for the part about having more
than 1 million large objects that get committed individually, setting
fsync=off for the reload phase is likely to help a lot.
Just don't forget to turn it on again when it's done. See
https://blog.2ndquadrant.com/postgresql-fsync-off-warning-in-config-file/
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ERR ORR | 2018-06-27 09:44:02 | Re: Code of Conduct committee: call for volunteers |
| Previous Message | Akshaya Acharya | 2018-06-27 09:29:29 | Re: Too many range table entries error |