| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Speeding up pg_upgrade |
| Date: | 2017-12-05 17:59:08 |
| Message-ID: | abcfba8f-feef-faf1-ba0a-bd472bf153fc@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/5/17 09:23, Stephen Frost wrote:
> Right, but that doesn't really answer the question as to which part of
> the pg_upgrade process is taking up the time.
Yeah, that should be measured before we do anything.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-12-05 18:01:43 | Re: Usage of epoch in txid_current |
| Previous Message | Andres Freund | 2017-12-05 17:45:01 | Re: Usage of epoch in txid_current |