2016-12-22 10:23 GMT+01:00 Brian Sutherland :
> Perhaps try 9.5.5 which has a fix for a problem with the same symptoms:
>
> https://wiki.postgresql.org/wiki/Free_Space_Map_Problems
> https://www.postgresql.org/docs/9.5/static/release-9-5-5.
> html#AEN126074
>
> Yes it was that!
I tried the
Perhaps try 9.5.5 which has a fix for a problem with the same symptoms:
https://wiki.postgresql.org/wiki/Free_Space_Map_Problems
https://www.postgresql.org/docs/9.5/static/release-9-5-5.html#AEN126074
On Wed, Dec 21, 2016 at 10:51:47AM +0100, Tom DalPozzo wrote:
> Hi,
> I was doing some t
>
>
>>
> If it where me I would use one of the -X methods:
>
> https://www.postgresql.org/docs/9.5/static/app-pgbasebackup.html
>
>
>
>> To me that looks like an issue with the associated TOAST table. I do not
> have a suggestion at this time. Maybe this rings a bell with someone else.
>
> --
> Adr
On 12/21/2016 10:06 AM, Tom DalPozzo wrote:
Is there an index on this table?
Have you tried a REINDEX on it?
yes there is an index on id field. I tried REINDEX. Nothing changes but
I notice now (but perhaps it was like that even before reindexing) that
every time I issue that UPDAT
>
> Is there an index on this table?
>>
>
> Have you tried a REINDEX on it?
>
> yes there is an index on id field. I tried REINDEX. Nothing changes but I
notice now (but perhaps it was like that even before reindexing) that every
time I issue that UPDATE query, the number of the block it can't read
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 expecte
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 r
On 12/21/2016 01:51 AM, Tom DalPozzo wrote:
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
