Re: [GENERAL] Postgres logs showing error after replication - Mailing list pgsql-general

From Vijay Chaudhery
Subject Re: [GENERAL] Postgres logs showing error after replication
Date
Msg-id SG2PR0401MB21754C43B8B25FF400E6020B83970@SG2PR0401MB2175.apcprd04.prod.outlook.com
Whole thread Raw
In response to Re: [GENERAL] Postgres logs showing error after replication  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Responses Re: [GENERAL] Postgres logs showing error after replication  (Vick Khera <vivek@khera.org>)
List pgsql-general
Ok is it possible to release the lock? or it is just a warning messages only?
thanks

-----Original Message-----
From: Tatsuo Ishii [mailto:ishii@sraoss.co.jp]
Sent: 06 September 2017 10:31 AM
To: Vijay Chaudhery <vijay_c@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?
>
> <tag>
>>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
lockon 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.


----------------------------------------------------------------------------------------------------------------------------------------------------



pgsql-general by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [GENERAL] Postgres logs showing error after replication
Next
From: Diags101
Date:
Subject: [GENERAL] Inconsistent Postgres error when installing our product containingPostgreSQL 9.3.4