Robert Haas <robertmh...@gmail.com> writes:
> Ugh, really? Are we sure that the current behavior is anything other
> than a bug? The idea that VACUUM foo (a) implies ANALYZE doesn't
> really sit very well with me in the first place. I'd be more inclined
> to reject that with an ERROR complaining that the column list can't be
> specified except for ANALYZE.
Yeah, that's probably more sensible. I think the rationale was "if you
specify columns you must want the ANALYZE option, so why make you type
that in explicitly?". But I can see the argument that it's likely to
confuse users who might have a weaker grasp of the semantics.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
