From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER INDEX .. SET STATISTICS ... behaviour |
Date: | 2017-06-04 04:34:58 |
Message-ID: | CAA4eK1LgUs8t7AGdAMUubNWLr272+i-BU9b8dcqmxKgZ9jp7VA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 1, 2017 at 6:40 PM, Alexander Korotkov
<a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> On Wed, May 31, 2017 at 7:18 PM, Alexander Korotkov
> <a(dot)korotkov(at)postgrespro(dot)ru> wrote:
>>
>>>
>>> Don't like either of those particularly, but what about just targeting
>>> a column by column number, independently of whether it's an expression?
>>>
>>> ALTER INDEX myindex ALTER COLUMN 4 SET STATISTICS 1000;
>>
>>
>> I completely agree with that.
>> If no objections, I will write a patch for that.
>
>
> Please, find it in attached patch.
>
> I decided to forbid referencing columns by numbers for tables, because those
> numbers could contain gaps. Also, I forbid altering statistics target for
> non-expression index columns, because it has no effect.
>
In order to avoid losing track of this patch, I think it is better to
add it in open items list for 10.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-06-04 04:41:11 | Re: ALTER INDEX .. SET STATISTICS ... behaviour |
Previous Message | Rafia Sabih | 2017-06-04 03:56:11 | Re: Default Partition for Range |