| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal : For Auto-Prewarm. |
| Date: | 2017-01-26 15:15:45 |
| Message-ID: | d8c72cff-e135-3bb8-7947-2736b45e3b8a@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/24/17 3:26 AM, Mithun Cy wrote:
> In my code by default, we only dump at shutdown time. If we want to
> dump at regular interval then we need to set the GUC
> pg_autoprewarm.buff_dump_interval to > 0.
Just a thought with an additional use case: If I want to set up a
standby for offloading queries, could I take the dump file from the
primary or another existing standby, copy it to the new standby, and
have it be warmed up to the state of the other instance from that?
In my experience, that kind of use is just as interesting as preserving
the buffers across a restart.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-01-26 15:16:35 | Re: [COMMITTERS] pgsql: Reindent table partitioning code. |
| Previous Message | Robert Haas | 2017-01-26 15:02:34 | Re: Assignment of valid collation for SET operations on queries with UNKNOWN types. |