Search Postgresql Archives

Re: error updating a tuple after promoting a standby

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/21/2016 08:17 AM, Tom DalPozzo wrote:
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)

Is there an index on this table?

Have you tried a REINDEX on it?


In your original post you mention this error occurred while testing backup/replication/standby promotion.

What was the procedure you followed in doing the testing?




        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@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>


Thanks
Pupillo


--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx


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



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux