From: | Andrew Puschak <apuschak(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: warm standby replication safe failover |
Date: | 2013-02-03 16:18:28 |
Message-ID: | CALFZoBt3couV46TZE9V7OtgnW3K9MBp8M7__7jaJxpK7bh0B=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hi again,
I setup PostgreSQL 9.2 to try replication and the 9.2 documentation
answered my question whereas the 8.4 documentation is missing the section
25.2.2. Standby Server Operation
http://www.postgresql.org/docs/9.2/static/warm-standby.html#STANDBY-SERVER-OPERATIONIt
explains my assumption that if you copy over the last pg_xlog from the
Primary, which I can do after safely shutting down postgres, recovery will
first apply the WALs from the archive directory and then attempt to recover
anything else in pg_xlog, but take priority over the WALs in the archive
directory.
As for upgrading to the newer release branch, I'm asking the CentOS
community where/how the PostgresSQL version is determined in their
repositories. It would be easier if I could continue to use the default
Base and Update repositories from CentOS to update postgres, but I don't
know when they plan to include 9.x versions.
Andrew
On Sat, Feb 2, 2013 at 12:45 PM, Andrew Puschak <apuschak(at)gmail(dot)com> wrote:
> Thanks Tom!
>
> The PostgreSQL 8.4 is coming from the default latest CentOS 6.3 updates
> repository which makes it an easy install and upgrade later (yum install
> postgresql-server). I'll try installing/upgrading my test setup using
> http://yum.postgresql.org repository. I'm also going to need to find out
> what migrating to a newer version will affect with the current production
> data.
> Andrew
>
>
> On Sat, Feb 2, 2013 at 12:19 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Andrew Puschak <apuschak(at)gmail(dot)com> writes:
>> > I'm new here and have a question. I'm working on a replacement
>> PostgreSQL
>> > 8.4 setup for a small company. They now have a Primary postgres server
>> and
>> > 2 secondaries which are replicated using Slony-I, however the consulting
>> > company that set it up is afraid to failover and keeping Slony running
>> is
>> > taking lots of resources.
>>
>> It sounds like you're trying to keep them on 8.4. Why not move them to
>> some newer release branch where you can make use of streaming
>> replication? Aside from the benefits of that, 8.4 will be out of
>> support next year, so setting up new servers with that release series
>> seems pretty short-sighted.
>>
>> I realize that dealing with a version upgrade might not be their highest
>> priority right now, but they're going to have to deal with it before too
>> long, and doing so now would put them in position to have a far better
>> replication solution than what you're describing.
>>
>> regards, tom lane
>>
>
>
>
> --
> Andrew Puschak
> (267) 614 - 2373
> apuschak(at)gmail(dot)com
> http://andrewpuschak.com
>
--
Andrew Puschak
(267) 614 - 2373
apuschak(at)gmail(dot)com
http://andrewpuschak.com
From | Date | Subject | |
---|---|---|---|
Next Message | Zach Seaman | 2013-02-07 00:56:29 | Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1 |
Previous Message | Andrew Puschak | 2013-02-02 17:45:17 | Re: warm standby replication safe failover |