From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Beena Emerson <memissemerson(at)gmail(dot)com>, 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-22 00:58:31 |
Message-ID: | CA+TgmoY0Rjw=T-swpotmpQpzOPE9ZecOq=HZ2pjMJ9OZ4c8DVg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 22, 2017 at 4:06 AM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> 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)?
I think it's OK to treat that as something of a corner case. There's
nothing to keep you from doing that today: just use pg_buffercache to
dump a list of blocks on one server, and then pass those blocks to
pg_prewarm on another server. The point of this patch, AIUI, is to
automate a particularly common case of that, which is to dump before
shutdown and load upon startup. It doesn't preclude other things that
people want to do.
I suppose we could have an SQL-callable function that does an
immediate dump (without starting a worker). That wouldn't hurt
anything, and might be useful in a case like the one you mention.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-02-22 01:01:55 | Re: SERIALIZABLE with parallel query |
Previous Message | Andrew Dunstan | 2017-02-21 23:16:14 | Re: Json support for array pseudotypes |