| From: | Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com> |
|---|---|
| To: | Ray Stell <stellr(at)cns(dot)vt(dot)edu> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, alexondi <alexondi(at)rambler(dot)ru> |
| Subject: | Re: Wal archiving and streaming replication |
| Date: | 2011-08-24 01:46:50 |
| Message-ID: | CA+h6Ahgr6fEW5hyLKe=vNo4tYLQHC-SO+mjxZNNsDBb3pOrAoQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Aug 23, 2011 at 10:49 PM, Ray Stell <stellr(at)cns(dot)vt(dot)edu> wrote:
> On Tue, Aug 23, 2011 at 08:30:55PM +0530, Raghavendra wrote:
> >
> > Is it a best practice to keep cluster in Archive_mode = on and setup
> > streaming replication or just leave archive_mode=off?
>
> Depends. The reason for creating WAL is in case they are needed for
> recovery.
> In the event that the stby host goes down, if bringing it back into service
> exceeds wal_keep_segments on the primary then you would need to rebuild
> the standby. This is a local decision and should be made based on business
> rules.
>
Thanks Ray.
--Raghav
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Nelson | 2011-08-24 01:58:13 | Re: JDBC Connection Errors |
| Previous Message | Chris Hanks | 2011-08-23 23:54:39 | Collapsing multiple subqueries into one |