Re: Please correct/improve wiki page about abbreviated keys bug

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Josh berkus <josh(at)agliodbs(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Please correct/improve wiki page about abbreviated keys bug
Date: 2016-03-31 20:38:19
Message-ID: CAM3SWZStgwpCEOggiXAhAYnkn1Om4R5zeKho22EB+6-XCDzrxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 30, 2016 at 6:23 PM, Josh berkus <josh(at)agliodbs(dot)com> wrote:
> Based on that concept, I wrote a query which is now on the wiki page.
> Please fix it if it's not showing what we want it to show.

Sorry, I got caught up with something last night. I did this this
morning Pacific time.

I've made a number of passes over this. I've listed more non-affected
cases, since there are a number of non-obvious cases that are not at
risk, and fixed-up the SQL query, which didn't seem to be doing the
right thing about default collations or domains. I also made it
explicit that non-leading column indexes are not affected (although
that's just mentioned in passing when discussing the SQL query, as
it's a bit esoteric).

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2016-03-31 20:39:26 Re: So, can we stop supporting Windows native now?
Previous Message Alvaro Herrera 2016-03-31 20:34:07 Re: improving GROUP BY estimation