error updating a tuple after promoting a standby

From: Tom DalPozzo <t(dot)dalpozzo(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: error updating a tuple after promoting a standby
Date: 2016-12-21 09:51:47
Message-ID: CAK77FCR86jWm70uPzoZ7Fmrzwxv7oJ8eo0m7yaMoVzpywmL1Vw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,
I was doing some tests with backup, replication, standby. After promoting a
standby server, I found my db in a condition that raises me an error while
trying to update a particular tuple.
Below here you can se my UPDATE statment and the error raised.
The select * from stato where id=409; executed immediately after worked
well however.
I checked the file and it's readable.
Before my standby promotion test I performed millions of this UPDATE
statments without problem on my db.
I can not reproduce the issue.

Perhaps I did something wrong during my test but I don't know what. I
didn't touch any file in base directory however.
Anyway I'd like to know if in your opinion it's possible that this error
was caused by something wrong done by me or if it should never happen as
the file is perfectly readable.

Regards
Pupillo

psql (9.5.4)
Type "help" for help.

ginopino=# UPDATE stato SET
dati='\x5353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353535353'
WHERE id=409;
ERROR: could not read block 12281 in file "base/16384/29153": read only 0
of 8192 bytes
ginopino=# select * from stato where id=409; <<< IT WORKS FINE

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2016-12-21 11:34:09 Re:
Previous Message Yogesh Sharma 2016-12-21 09:02:34 Fwd: Request to share approach during REINDEX operation