On Thu, May 18, 2017 at 12:06 AM, Bossart, Nathan <bossa...@amazon.com> wrote: > I agree with you here, too. I stopped short of allowing customers to > explicitly provide per-table options, so the example you provided wouldn’t > work here. This is more applicable for something like the following: > > VACUUM (FREEZE, VERBOSE) foo, bar (a); > > In this case, the FREEZE and VERBOSE options are used for both tables. > However, we have a column list specified for ‘bar’, and the ANALYZE option is > implied when we specify a column list. So when we process ‘bar’, we need to > apply the ANALYZE option, but we do not need it for ‘foo’. For now, that is > all that this per-table options variable is used for.
Hm. One argument can be made here: having a column list defined in one of the tables implies that ANALYZE is enforced for all the relations listed instead of doing that only on the relations listing columns. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
