From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | "Sander, Ingo (NSN - DE/Munich)" <ingo(dot)sander(at)nsn(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Streaming Replication: sql error on standby |
Date: | 2010-06-27 11:46:56 |
Message-ID: | 1277639216.25074.56529.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2010-06-23 at 10:48 +0200, Sander, Ingo (NSN - DE/Munich) wrote:
> Sql query "select pg_last_xlog_receive_location(); " does not work
> during startup of standby database.
Thanks for the report.
We need to understand more about what you are saying. There is no error
message with that text.
> TestScenario;
> We have a active-standby system with PostgreSQL Streaming Replication
> beta2. If the active database is up the database is in use (read/write
> queries will be performed). Then the standby PostgreSQL SR will be
> started (the complete database from the active side is copied to the
> standby side; nec. Files for starting streaming replication are
> created). Directly after the possibility to connect to the standby
> system, the above given sql query will be executed. To this timepoint
> the sql query delivers an error. To a later timepoint (all wal
> segments are completly incooperated) the query delivers a valid
> result.
>
> Question:
> What is the reason for the error?
> Exists a command to find out if the standby database is really active
> to accept/can work with sql commands?
Could you show us the log?
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2010-06-27 11:48:46 | Re: Re: [COMMITTERS] pgsql: Fix log_temp_files docs and comments to say bytes not kilobytes. |
Previous Message | Simon Riggs | 2010-06-27 11:39:38 | Re: EOL is when? |