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

From Tatsuo Ishii
Subject Re: [GENERAL] Postgres logs showing error after replication
Date
Msg-id 20170906.140037.1039173594873470705.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Re: [GENERAL] Postgres logs showing error after replication  (Vijay Chaudhery <vijay_c@hcl.com>)
Responses Re: [GENERAL] Postgres logs showing error after replication  (Vijay Chaudhery <vijay_c@hcl.com>)
List pgsql-general
> 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 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


pgsql-general by date:

Previous
From: Vijay Chaudhery
Date:
Subject: Re: [GENERAL] Postgres logs showing error after replication
Next
From: Vijay Chaudhery
Date:
Subject: Re: [GENERAL] Postgres logs showing error after replication