| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Matthias Leisi <matthias(at)leisi(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: "Compressed data is corrupt" |
| Date: | 2012-03-01 21:50:29 |
| Message-ID: | 18379.1330638629@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Matthias Leisi <matthias(at)leisi(dot)net> writes:
> I have a behaviour of Postgres which I do not understand (and thus can
> not fix...). When inserting into a log-like table, I get the error
> message "compressed data is corrupt" for certain (rare) combination of
> values. When I re-create the same table structure from scratch and
> insert the same data in to that table, the error does not appear.
The most obvious theory for this is a corrupted index entry in the pkey
index. Does the issue go away if you REINDEX?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lonni J Friedman | 2012-03-01 22:01:31 | pg_upgrade + streaming replication ? |
| Previous Message | Tom Lane | 2012-03-01 21:47:43 | Re: 2 x duplicate key value violation: which exception comes first ? |