| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | "Dr(dot) Andreas Kunert" <kunert(at)cms(dot)hu-berlin(dot)de>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15597: possible bug in amcheck/amcheck_next (or corrupted index?) |
| Date: | 2019-02-07 00:18:55 |
| Message-ID: | CAH2-WzmabSZTS7ANDvpS3hoAOQF-uzM9yMM+wzbOkKo-bzXuLA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Jan 25, 2019 at 9:57 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> I have a draft patch that fixes this, but I haven't quite decided if I
> want to commit to the approach I've taken to normalizing TOASTed
> tuples. I will definitely fix the externally maintained version
> (amcheck_next) once this is settled. Thanks for the report.
I pushed a fix for this to contrib/amcheck, and to the externally
maintained amcheck_next codebase. There will be new set of point
releases of Postgres on February 14th, 2019. I'll see to cutting a new
release of amcheck_next shortly as well.
Thanks for the report!
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-02-07 07:29:47 | Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure |
| Previous Message | Tom Lane | 2019-02-06 19:15:55 | Re: BUG #15613: Bug in PG Planner for Foreign Data Wrappers |