| From: | Josh berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Please correct/improve wiki page about abbreviated keys bug |
| Date: | 2016-03-31 01:23:49 |
| Message-ID: | 56FC7C25.50302@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/30/2016 02:47 PM, Josh berkus wrote:
> On 03/29/2016 07:43 PM, Peter Geoghegan wrote:
>> Do you think it would be okay if the SQL query to detect potentially
>> affected indexes only considered the leading attribute? Since that's
>> the only attribute that could use abbreviated keys, it ought to be
>> safe to not require users to REINDEX indexes that happen to have a
>> second-or-subsequent text/varchar(n) attribute that doesn't use the C
>> locale. Maybe it's not worth worrying about.
>
> I think that's a great idea.
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.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-03-31 01:38:31 | Re: Please correct/improve wiki page about abbreviated keys bug |
| Previous Message | Ian Barwick | 2016-03-31 01:15:21 | Correction for replication slot creation error message in 9.6 |