Thank you all a lot!
I have got it.
Best regards
2013/10/10 Stuart Bishop
> On Wed, Oct 9, 2013 at 9:58 AM, 高健 wrote:
>
> > The most important part is:
> >
> > 2013-09-22 09:52:47 JST[28297][51d1fbcb.6e89-2][0][XX000]FATAL: Could
> not
> > receive data from WAL stream: could not receive dat
On Wed, Oct 9, 2013 at 9:58 AM, 高健 wrote:
> The most important part is:
>
> 2013-09-22 09:52:47 JST[28297][51d1fbcb.6e89-2][0][XX000]FATAL: Could not
> receive data from WAL stream: could not receive data from server: connection
> timeout
> scp: /opt/PostgresPlus/9.2AS/data/arch/00AC01F1
On 10/09/2013 05:51 PM, 高健 wrote:
Hello:
Thanks for replying.
The recovery.conf file on standby(DB2) is like that:
standby_mode = 'on'
primary_conninfo = 'host=DB1 port=5432 application_name=testpg
user=postgres connect_timeout=10 keepalives_idle=5 keepalives_interval=1'
re
Hello:
Thanks for replying.
The recovery.conf file on standby(DB2) is like that:
standby_mode = 'on'
primary_conninfo = 'host=DB1 port=5432 application_name=testpg
user=postgres connect_timeout=10 keepalives_idle=5 keepalives_interval=1'
recovery_target_timeline = 'latest'
re
On 10/08/2013 07:58 PM, 高健 wrote:
Hello:
My customer encountered some connection timeout, while using one
primary-one standby streaming replication.
The original log is japanese, because there are no error-code like
oracle's ora-xxx,
I tried to translate the japanese information into English, B
Hello:
My customer encountered some connection timeout, while using one
primary-one standby streaming replication.
The original log is japanese, because there are no error-code like oracle's
ora-xxx,
I tried to translate the japanese information into English, But that might
be not correct English