From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Accidental removal of a file causing various problems |
Date: | 2018-08-24 19:33:02 |
Message-ID: | 20180824193302.atba6jchedmzllnh@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2018-Aug-25, Pavan Deolasee wrote:
> The errors were simply about about the missing file. See attached
> reproduction script that I created while studying this complaint. It will
> throw errors such as:
>
> psql: FATAL: could not open file "base/12669/16387": No such file or
> directory
> CONTEXT: writing block 207724 of relation base/12669/16387
>
> Now of course, the file is really missing. But the user was quite surprised
> that they couldn't connect to any database, even though mishap happened to
> a user table in one of their reporting databases.
Hmm, that sounds like there's a bunch of dirty pages waiting to be
written to that nonexistant file, and the error prevents the starting
backend from acquiring a free page on which to read something from disk
for another relation.
> To add to their misery, while restart fixed this error and opened
> their other databases for regular operation, it caused the toast
> corruption.
Sounds like the right data was in shared buffers, but it was lost in the
shutdown.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-08-24 19:38:15 | Re: Accidental removal of a file causing various problems |
Previous Message | Pavan Deolasee | 2018-08-24 19:26:17 | Re: Accidental removal of a file causing various problems |