| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Beena Emerson <memissemerson(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal : For Auto-Prewarm. |
| Date: | 2017-02-21 22:36:21 |
| Message-ID: | d799a3f9-162d-2e71-116a-b67183158cbf@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/10/17 15:12, Robert Haas wrote:
> Right. I can't see why you'd want to be able to separately control
> those two things. If you're not dumping, you don't want to load; if
> you're not loading, you don't want to dump.
What about the case where you want to prewarm a standby from the info
from the primary (or another standby)?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2017-02-21 22:40:41 | Json support for array pseudotypes |
| Previous Message | Peter Eisentraut | 2017-02-21 22:25:59 | Re: Change in "policy" on dump ordering? |