| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Banck <michael(dot)banck(at)credativ(dot)de> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Press Release Draft - 2016-02-09 Cumulative Update |
| Date: | 2017-02-07 17:36:52 |
| Message-ID: | 20170207173652.qic57zsowepj2d5v@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Banck wrote:
> Hi,
>
> Am Dienstag, den 07.02.2017, 10:37 -0500 schrieb Jonathan S. Katz:
>
> > Below is the draft of the press release for the update this Thursday:
>
> About the CREATE INDEX CONCURRENTLY issue, I wonder whether Peter's
> amcheck extension[1] would catch that (for B-Tree indexes at least), and
> if that is the case, whether we could mention that to our users as
> guidance for how to check for index corruption?
"it does not verify that the target index is consistent with its heap
relation"
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-02-07 17:41:18 | Re: Cache Hash Index meta page. |
| Previous Message | Joel Jacobson | 2017-02-07 17:33:41 | Re: Idea on how to simplify comparing two sets |