From: | Tom DalPozzo <t(dot)dalpozzo(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: error updating a tuple after promoting a standby |
Date: | 2016-12-21 16:17:03 |
Message-ID: | CAK77FCQyOsOy6yk=jJa6jNbNrvJa+bJ-TnkZH5j055z=p6Z2Ng@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)klaver(at)aklaver(dot)com
Thanks
Pupillo
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-12-21 16:31:38 | Re: How well does PostgreSQL 9.6.1 support unicode? |
Previous Message | Jaime Soler | 2016-12-21 15:45:25 | Re: |