Re: vacuumdb error

On Fri, Oct 16, 2009 at 6:39 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> Thom Brown wrote:
>> This is either a bug in vacuumdb with it not using the correct order,
>> or postgres shouldn't be paying attention to the order of the
>> keywords. =A0In any case, it doesn't work. =A0I've searched the postgres
>> FAQs, TODO and mailing list archives, but can't find a mention of
>> this.
>
> Thanks, fixed. We had the same bug with FREEZE and ANALYZE combination,
> which was fixed in April, but the order between FREEZE and VERBOSE was
> still incorrect.

The fact that this is order-sensitive is just a trap for the unwary
anyway.  I wonder if we ought to implement a flexible options syntax
like we did for EXPLAIN and COPY, though since I don't know of any new
options that are needed here maybe it's not worth it.

...Robert