Re: [GENERAL] error updating a tuple after promoting a standby - Mailing list pgsql-general

From Tom DalPozzo
Subject Re: [GENERAL] error updating a tuple after promoting a standby
Date
Msg-id CAK77FCQyOsOy6yk=jJa6jNbNrvJa+bJ-TnkZH5j055z=p6Z2Ng@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] error updating a tuple after promoting a standby  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: [GENERAL] error updating a tuple after promoting a standby
List pgsql-general
Hi, 
 
First I would find what base/16384/29153 actually is. So in the database where stato is:

select relname from pg_class where relfilenode = 29153;

below here the query you suggested, showing that file belongs to stato table as expected.
ginopino=# select relname from pg_class where relfilenode = 29153;
 relname 
---------
 stato
(1 row)
 


0 of 8192 bytes
ginopino=# select * from stato where id=409;  <<< IT WORKS FINE

But does it have the updated info?
Yes,  it  correctly shows the expected data before issuing the update query which generates the problem:
 ginopino=# select * from stato where id=409;
  id  |  .......  dati         .......
-----+--------------  .......
 409 | \x4a735300db8f4b31ab8660f85192bc.................... 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

Thanks
Pupillo

pgsql-general by date:

Previous
From: Jaime Soler
Date:
Subject: Re: [GENERAL]
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] How well does PostgreSQL 9.6.1 support unicode?