Re: [GENERAL] Postgres logs showing error after replication

2017-09-06 Thread Vick Khera 
On Wed, Sep 6, 2017 at 1:16 AM, Vijay Chaudhery  wrote:

> Ok is it possible to release the lock? or it is just a warning messages
> only?
> thanks
>

The message starts with "ERROR" so it is an error, not a warning. The
command failed. The only way to release the lock is to have the other
connection do it.

Re: [GENERAL] Postgres logs showing error after replication

2017-09-05 Thread Vijay Chaudhery 
Ok is it possible to release the lock? or it is just a warning messages only?
thanks

-Original Message-
From: Tatsuo Ishii [mailto:is...@sraoss.co.jp] 
Sent: 06 September 2017 10:31 AM
To: Vijay Chaudhery <vija...@hcl.com>
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Postgres logs showing error after replication

> Ok thank you,
> 
> I have promoted slave server as master in postgres streaming 
> replication , howerver application is working fine after promotion , 
> but getting some error messages in the postgres log (slave which 
> promoted to master)
> 
> what does it mean?
> 
> 
>>ERROR: could not obtain lock on row in relation "main_instance"
> < 2017-09-05 13:08:45.434 UTC >STATEMENT: SELECT "main_instance"."id", 
> "main_instance"."uuid", "main_instance"."hostname", 
> "main_instance"."created", "main_instance"."modified", 
> "main_instance"."version", "main_instance"."capacity" FROM 
> "main_instance" LIMIT 1 FOR UPDATE NOWAIT

Your session (transction) tried to get a row lock on the row but other session 
(transaction) has already gotten the row lock on the same row.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp


::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.





-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Postgres logs showing error after replication

2017-09-05 Thread Tatsuo Ishii 
> Ok thank you,
> 
> I have promoted slave server as master in postgres streaming replication , 
> howerver application is working fine after promotion , but getting some error 
> messages in the postgres log (slave which promoted to master) 
> 
> what does it mean?
> 
> 
>>ERROR: could not obtain lock on row in relation "main_instance"
> < 2017-09-05 13:08:45.434 UTC >STATEMENT: SELECT "main_instance"."id", 
> "main_instance"."uuid", "main_instance"."hostname", 
> "main_instance"."created", "main_instance"."modified", 
> "main_instance"."version", "main_instance"."capacity" FROM "main_instance" 
> LIMIT 1 FOR UPDATE NOWAIT

Your session (transction) tried to get a row lock on the row but other
session (transaction) has already gotten the row lock on the same row.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Postgres logs showing error after replication

2017-09-05 Thread Vijay Chaudhery 
Ok thank you,

I have promoted slave server as master in postgres streaming replication , 
howerver application is working fine after promotion , but getting some error 
messages in the postgres log (slave which promoted to master) 

what does it mean?


>ERROR: could not obtain lock on row in relation "main_instance"
< 2017-09-05 13:08:45.434 UTC >STATEMENT: SELECT "main_instance"."id", 
"main_instance"."uuid", "main_instance"."hostname", "main_instance"."created", 
"main_instance"."modified", "main_instance"."version", 
"main_instance"."capacity" FROM "main_instance" LIMIT 1 FOR UPDATE NOWAIT



-Original Message-----
From: Tatsuo Ishii [mailto:is...@sraoss.co.jp] 
Sent: 06 September 2017 10:02 AM
To: Vijay Chaudhery <vija...@hcl.com>
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Postgres logs showing error after replication

> I am not sure if the sending email is the right way to get the forum help. 
> Could you please let me know how to open forum query to ask postgres 
> questions.

Sending email to this mailing list regarding your questions is the perfect way 
to get help.

Other than this, there's an IRC channel for PostgreSQL.
https://www.postgresql.org/community/irc/

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp


::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.





-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Postgres logs showing error after replication

2017-09-05 Thread Tatsuo Ishii 
> I am not sure if the sending email is the right way to get the forum help. 
> Could you please let me know how to open forum query to ask postgres 
> questions.

Sending email to this mailing list regarding your questions is the
perfect way to get help.

Other than this, there's an IRC channel for PostgreSQL.
https://www.postgresql.org/community/irc/

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] Postgres logs showing error after replication

2017-09-05 Thread Vijay Chaudhery 
Hi,

I am not sure if the sending email is the right way to get the forum help. 
Could you please let me know how to open forum query to ask postgres questions.

Thanks
vijay


::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.