before.
We will be upgrading to PostgreSQL 9.3.17 during the weekend, but I'd like to
hear
if anyone has seen something like this, or have some ideas of how to
investigate/what the cause might be.
Best regards,
Adam
--
"Lägg ditt liv i min hand Ada
he response!
Adam
--
"Lägg ditt liv i min handAdam Sjøgren
Sälj din själ till ett band" a...@novozymes.com
--
Sent via pgsql-general mailing list (pgsql-general
s other than pg_default?
> I can only replicate the issue when using separately mounted
> tablespaces.
No, we are using pg_default only.
I hope your finding can be reproduced, it would be really interesting to
see.
Best regards,
Adam
--
"Lägg ditt liv i min hand
Alvaro Herrera wrote:
> ADSJ (Adam Sjøgren) wrote:
>
>> Our database has started reporting errors like this:
>>
>> 2017-05-31 13:48:10 CEST ERROR: unexpected chunk number 0 (expected 1)
>> for toast value 14242189 in pg_toast_10919630
> Does the problem sti
Adam Sjøgren wrote:
> Meanwhile, I can report that I have upgraded from 9.3.14 to 9.3.17 and
> the errors keep appearing the log.
Just a quick update with more observations:
All the errors in the postgres.log from one of the tables are triggered
by a stored procedure that gathers data
On 2017-06-21 Adam Sjøgren wrote:
> Adam Sjøgren wrote:
>> Meanwhile, I can report that I have upgraded from 9.3.14 to 9.3.17 and
>> the errors keep appearing the log.
Just to close this, for the record: We haven't seen the errors since
2017-06-30. We upgraded to 9.3.
