| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Thom Brown <thombrown(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: vacuumdb error |
| Date: | 2009-10-16 13:32:20 |
| Message-ID: | 603c8f070910160632t66723f25ma09182e8ed85025e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 16, 2009 at 6:39 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)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. In any case, it doesn't work. I'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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-10-16 13:45:55 | Re: BUG #5123: bug in window function "last_value" |
| Previous Message | Thom Brown | 2009-10-16 13:07:18 | Re: vacuumdb error |