diff options
| author | Andres Freund <andres@anarazel.de> | 2014-11-14 18:20:59 +0100 |
|---|---|---|
| committer | Andres Freund <andres@anarazel.de> | 2014-11-15 01:19:57 +0100 |
| commit | 1a2cb1ea84a1745247a7b41f1b0188889e815794 (patch) | |
| tree | 0c24b2f19cc1134516ecdfe5661c21fb552f8d4a /contrib/postgres_fdw | |
| parent | df3e23e1b509001ac9336763404406bdcad04dcc (diff) | |
| download | postgresql-1a2cb1ea84a1745247a7b41f1b0188889e815794.tar.gz postgresql-1a2cb1ea84a1745247a7b41f1b0188889e815794.zip | |
Ensure unlogged tables are reset even if crash recovery errors out.
Unlogged relations are reset at the end of crash recovery as they're
only synced to disk during a proper shutdown. Unfortunately that and
later steps can fail, e.g. due to running out of space. This reset
was, up to now performed after marking the database as having finished
crash recovery successfully. As out of space errors trigger a crash
restart that could lead to the situation that not all unlogged
relations are reset.
Once that happend usage of unlogged relations could yield errors like
"could not open file "...": No such file or directory". Luckily
clusters that show the problem can be fixed by performing a immediate
shutdown, and starting the database again.
To fix, just call ResetUnloggedRelations(UNLOGGED_RELATION_INIT)
earlier, before marking the database as having successfully recovered.
Discussion: 20140912112246.GA4984@alap3.anarazel.de
Backpatch to 9.1 where unlogged tables were introduced.
Abhijit Menon-Sen and Andres Freund
Diffstat (limited to 'contrib/postgres_fdw')
0 files changed, 0 insertions, 0 deletions