From: | Venkat Balaji <venkat(dot)balaji(at)verse(dot)in> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: [GENERA]: Postgresql-9.1.1 synchronous replication issue |
Date: | 2012-02-10 11:17:42 |
Message-ID: | CAFrxt0h_Y+XL6QiXpyKrP9HoYTR2MNa2gAMkQq5XZHYeO_FcBA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
This issue stays resolved !!!
The statements are no more hanging on production now :)
The suspected problem was -
Our brand new production server did not have the port 5432 open.
I had opened the port using "iptables" command and everything started
working.
synchronous replication is fast and awesome.
Thanks
VB
On Fri, Feb 3, 2012 at 9:45 PM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>wrote:
> On Thursday, February 02, 2012 10:21:28 pm Venkat Balaji wrote:
>
> >
> > Connection is working fine between primary and standby, ping is working
> > fine and wal archive file transfer is working without any issues.
> >
> > I tried CREATE TABLE and CREATE DATABASE, both were hanging.
> >
> > Apart from regular streaming replication settings, I did the following on
> > primary to enable synchronous replication -
> >
> > synchronous_standby_names='*'
> >
> > Commands started hanging after that. Is there anything else i need to do.
>
> From here:
>
> http://www.postgresql.org/docs/9.1/interactive/runtime-config-replication.html
>
> "
> synchronous_standby_names (string)
> ... The synchronous standby will be the first standby named in this list
> that is
> both currently connected and streaming data in real-time (as shown by a
> state of
> streaming in the pg_stat_replication view). Other standby servers appearing
> later in this list represent potential synchronous standbys....
>
> The name of a standby server for this purpose is the application_name
> setting of
> the standby, as set in the primary_conninfo of the standby's walreceiver.
> There
> is no mechanism to enforce uniqueness. In case of duplicates one of the
> matching
> standbys will be chosen to be the synchronous standby, though exactly
> which one
> is indeterminate. The special entry * matches any application_name,
> including
> the default application name of walreceiver.
>
> "
>
> So I would check the pg_stat_replication view to see if Postgres is seeing
> the
> standby as streaming.
>
>
> >
> > Thanks
> > VB
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)gmail(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Vincent Veyron | 2012-02-10 15:49:35 | Re: Strategy for Primary Key Generation When Populating Table |
Previous Message | Chris Travers | 2012-02-10 02:53:39 | Re: Strategy for Primary Key Generation When Populating Table |