On Wed, Jun 27, 2018 at 06:39:39PM -0500, Justin Pryzby wrote:
> < 2018-06-17 11:38:45.465 CDT pryzbyj >FATAL: the database system is in
> recovery mode
> < 2018-06-17 11:38:45.466 CDT pryzbyj >FATAL: the database system is in
> recovery mode
> < 2018-06-17 11:38:45.468 CDT >FATAL: could not extend file
> "base/17379/38665798": No space left on device
> < 2018-06-17 11:38:45.468 CDT >HINT: Check free disk space.
> < 2018-06-17 11:38:45.468 CDT >CONTEXT: WAL redo at 2AA/239676B8 for
> Heap/INSERT+INIT: off 1
> < 2018-06-17 11:38:45.468 CDT >WARNING: buffer refcount leak: [2366]
> (rel=base/17379/38665798, blockNum=1241, flags=0x8a000000, refcount=1 1)
> TRAP: FailedAssertion("!(RefCountErrors == 0)", File: "bufmgr.c", Line: 2523)
>
> Unfortunately, I have neither a core nor stacktrace to share, as the DB was
> (until after running out of space) on the same FS as /var :(You may be interested in this thread, vintage 2017, where I also posted a test case, assuming that you can create an extra partition and make it run out of space: https://www.postgresql.org/message-id/19533.1497283...@sss.pgh.pa.us So that's a known problem. -- Michael
signature.asc
Description: PGP signature
