From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14598: Duplicate values found when reindexing unique index |
Date: | 2017-03-27 18:15:15 |
Message-ID: | 5916.1490638515@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
John R Pierce <pierce(at)hogranch(dot)com> writes:
> However, running out of disk space in the disk volume holding pgdata is
> a catastrophic error, that can leave the database in an unknown state,
> depending on exactly what was allocating file space when it ran out.
It's not supposed to do that; the worst case ought to be a forced
database shutdown until you free up some space. (And that should
be an unusual case -- ideally, you just get a normal query failure
from an INSERT or UPDATE.) So there may in fact be a bug here,
if there were not any additional factors involved. But, as was said
upthread, 8.1.x is long out of support and nobody in the community
is likely to investigate bug reports against it for free.
If the OP is sufficiently desperate, he could probably hire one of
the various PG support companies to investigate, or at least help
him with data recovery.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Huong Dangminh | 2017-03-28 00:25:37 | Failed with build PostgreSQL in Windows ("--with-perl" option) |
Previous Message | John R Pierce | 2017-03-27 18:06:41 | Re: BUG #14598: Duplicate values found when reindexing unique index |