From: | akp geek <akpgeek(at)gmail(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Replication stopped on 9.0.2 after making change to conf file |
Date: | 2013-03-08 16:53:48 |
Message-ID: | CACnhOf+GPDLv4CE4psnLALc2+SF0LXb2o9oz04aUasrGj1C6Pg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I got it fixed.
What I did was
$ psql -c "SELECT pg_start_backup('label', true)"
$ rsync -a ${PGDATA}/ standby:/srv/pgsql/standby/ --exclude postmaster.pid
$ psql -c "SELECT pg_stop_backup()"
It took a while a to catch up the data.
One question I have , are there any scripts to monitor the status of
the replciation. so that I can be little proactive
Regards
On Thu, Mar 7, 2013 at 9:25 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:
> On Thu, Mar 7, 2013 at 5:28 PM, akp geek <akpgeek(at)gmail(dot)com> wrote:
> > Hi all -
> >
> > Recently made change on our primary database
> >
> > default_text_search_config = 'pg_catalog.simple' . After
> that
> > the replication is stopped. Can you please help me ? how to fix the
> issue. I
> > am sure I made the change on the slave also.
> >
> > How can I start the replication and catch up the data. Thanks for your
> time.
>
> What are you seeing in your slony and / or postgresql logs, if anything?
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2013-03-08 16:56:01 | Re: stored procedure slower when called through c client than pgadmin |
Previous Message | Bradley Russell | 2013-03-08 16:11:13 | stored procedure slower when called through c client than pgadmin |