| From: | "Matthew T(dot) O'Connor" <matthew(at)tocr(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, Postgresql-Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [RFC] GSoC Work on readonly queries done so far |
| Date: | 2007-06-06 22:53:06 |
| Message-ID: | 46673AD2.30403@tocr.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Simon Riggs wrote:
>> On Wed, 2007-06-06 at 12:17 -0400, Matthew T. O'Connor wrote:
>>> Florian G. Pflug wrote:
>>>> Work done so far:
>>>> -----------------
>>>> .) Don't start autovacuum and bgwriter.
>>> Do table stats used by the planner get replicated on a PITR slave? I
>>> assume so, but if not, you would need autovac to do analyzes.
>> The replication is an exact block-level replication of the master. We
>> can't write very much at all on the slave.
>
> Hmm, something to keep in mind is forcing cache invals when the master
> causes them (for example relation cache, catalog caches and plan
> caches).
Perhaps if you are as PITR master and you have active readonly slaves
then there should be a WAL record to note plan invalidations, etc?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2007-06-06 22:56:25 | Re: How do we create the releases? |
| Previous Message | Simon Riggs | 2007-06-06 21:41:18 | Re: [RFC] GSoC Work on readonly queries done so far |