Re: Collect frequency statistics for arrays
Alvaro Herrera <alvherre@commandprompt.com>
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Nathan Boley <npboley@gmail.com>, Alexander Korotkov <aekorotkov@gmail.com>, Noah Misch <noah@leadboat.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-03-01T22:12:39Z
Lists: pgsql-hackers
Excerpts from Tom Lane's message of jue mar 01 18:51:38 -0300 2012: > > Alvaro Herrera <alvherre@commandprompt.com> writes: > > Excerpts from Robert Haas's message of jue mar 01 12:00:08 -0300 2012: > >> On Wed, Feb 29, 2012 at 5:43 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > >> I confess I am nervous about ripping this out. I am pretty sure we > >> will get complaints about it. Performance optimizations that benefit > >> group A at the expense of group B are always iffy, and I'm not sure > >> the case of using an array as a path indicator is as uncommon as you > >> seem to think. > > > Maybe we should keep it as an option. > > How would we make it optional? There's noplace I can think of to stick > such a knob ... Uhm, attoptions? "alter table foo alter column bar set extended_array_stats to on" or something like that? -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support