| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | dhaval jaiswal <dhavallj(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: streaming replication vacuum |
| Date: | 2011-12-31 00:06:21 |
| Message-ID: | CAOR=d=3BWSatqdvQZNt9+bozB+AQmpMS=FEKAua-OdomTO6ERA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Dec 30, 2011 at 5:03 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Fri, Dec 30, 2011 at 07:35, dhaval jaiswal <dhavallj(at)hotmail(dot)com> wrote:
>>
>> Might be discussed but not clear for the below query.
>>
>> In async. streaming replication do I need to run VACUUM & ANALYZE on both
>> master & slave.
>> Bec, while querying on master getting below result, but slave's system table
>> is not updated.
>
> You run VACUUM and ANALYZE on the master only, and the results are
> automatically replicated to the slave.
>
> However, the *statistics views* on the slave are not updated. That's
> why it looks like it's not been run, even though it has.
Given the use of hot spares in this setup, wouldn't that kind of be a
bug that they're not updated?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-12-31 03:43:08 | Re: streaming replication vacuum |
| Previous Message | Simon Windsor | 2011-12-30 23:54:57 | Large Objects and and Vacuum |