Re: Draft release notes for next week's releases

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Draft release notes for next week's releases
Date: 2016-03-31 22:05:38
Message-ID: CAM3SWZQAwLmHMkJYz4zzX4FLy6YVTGPcxg7tmSXT1WBAmZ4OsA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 31, 2016 at 2:59 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Well, too late for 9.5.2 anyway. It still makes sense to correct that
> text for future releases. I'm inclined to wait a little bit though and
> see what other improvements become apparent. For instance, I think the
> point about non-first index columns not being affected is of greater
> weight than you seem to place on it.

The SQL query on the Wiki page does the right thing there now, so
users will have the benefit of not unnecessarily reindexing when text
was not the leading/first pg_index attribute. We have that covered, I
suppose, because everyone will look to the Wiki page for guidance.

I also noted quite a few non-obvious safe cases on the Wiki page, as
pointed out already over on the other thread.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-03-31 22:21:12 Re: Speed up Clog Access by increasing CLOG buffers
Previous Message Tom Lane 2016-03-31 21:59:52 Re: Draft release notes for next week's releases