Alvaro, Thomas,
Putting a 256kb file full of 0x55 that's 01010101 and represents 4
commits
It did the job in being able to restart the server.
According to our data a “better” way, with less garbage.
The “Toast” issues how ever are still present.
To spend our weekend well we setup a new serve
On Fri, Feb 7, 2020 at 1:47 AM Nick Renders wrote:
> Thank you for the feedback, Alvaro.
>
> Unfortunately, the database is no longer "dumpable". We were able to do
> a pg_dump yesterday morning (12 hours after the crash + purging the
> pg_clog) but if we try one now, we get the following error:
>
Thank you for the feedback, Alvaro.
Unfortunately, the database is no longer "dumpable". We were able to do
a pg_dump yesterday morning (12 hours after the crash + purging the
pg_clog) but if we try one now, we get the following error:
unexpected chunk number 1 (expected 0) for toast value 8
On 2020-Feb-05, Nick Renders wrote:
> Is there anything specific I should check in our postgres installation /
> database to make sure it is running ok now? Anyway to see what the
> consequences were of purging that one pg_clog file?
Losing pg_clog files is pretty bad, and should not happen; then
Hello,
Yesterday, we experienced some issues with our Postgres installation
(v9.6 running on macOS 10.12).
It seems that the machine was automatically rebooted for a yet unknown
reason, and afterwards we were unable to start the Postgres service.
The postgres log shows the following:
2020-02
