On Sun, Sep 09, 2018 at 01:25:49PM +0700, John Naylor wrote:
> I'm interested in this feature, so I've signed up to help review.
> Given the above, I thought it appropriate to mark the patch Waiting on
> Author.
I find this feature interesting as well. The patch has been waiting on
author input f
On 7/12/18, Yugo Nagata wrote:
> On Wed, 11 Jul 2018 14:26:03 +0300
> Alexander Korotkov wrote:
>> However, since multicolumn index may contain multiple expression, I
>> think we should support specifying columns for ANALYZE index clause.
>> We could support specifying columns by their numbers in
On 11/07/18 11:04, Yugo Nagata wrote:
> A usecase I suppose is that when a new expression index is created and that
> we need only the statistics for the new index.
I wonder if this shouldn't just be done automatically.
--
Vik Fearing +33 6 46 75 15 36
htt
all the
> > indexes
> > is usually fast because ANALYZE uses a random sampling of the table rows,
> > ANALYZE
> > on the specific index may be still useful if there are other index whose
> > "statistics
> > target" is large and/or whose expression ta
ZE
> on the specific index may be still useful if there are other index whose
> "statistics
> target" is large and/or whose expression takes time to compute, for example.
>
> Attached is the WIP patch to allow to specify a index name as ANALYZE
> parameter.
> Any do
large and/or whose expression takes time to compute, for example.
Attached is the WIP patch to allow to specify a index name as ANALYZE parameter.
Any documatation is not yet included. I would appreciate any feedback!
Regards,
--
Yugo Nagata
diff --git a/src/backend/commands/analyze.c b/s
