| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | ktr(at)goldin-rudahl(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org> |
| Subject: | Re: BUG #15023: problem with pg_statistic |
| Date: | 2018-01-22 01:01:47 |
| Message-ID: | 20180122010147.GB22690@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, Jan 21, 2018 at 06:10:15PM +0100, Tomas Vondra wrote:
> In any case, this seems like a case of data corruption, possibly due to
> a bug (not sure which PostgreSQL version you're using) hardware failure
> or misconfiguration (e.g. system not handling fsync correctly).
Duplicated rows could be caused by the freeze-the-dead bug as well,
which is not released yet (doesn't fix duplicated existing rows
anyway). It may be possible to get rid of this problem by removing
manually duplicated rows by tid matching.
> If that's the case, I'd suspect there are other corrupted tables.
That's likely possible, and impossible to say with this amount of
information. In this case, what you should do first is stop your server,
take a deep breath, and then read the following guidelines:
https://wiki.postgresql.org/wiki/Corruption
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Clough | 2018-01-22 10:41:45 | RE: BUG #15020: download to CSV button does nothing |
| Previous Message | Michael Paquier | 2018-01-22 00:55:17 | Re: BUG #15024: I am a beginer and in learning face |