| From: | Thom Brown <thombrown(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: vacuumdb error |
| Date: | 2009-10-16 13:48:11 |
| Message-ID: | bddc86150910160648y118089bapa6069c9bf03944c1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
2009/10/16 Robert Haas <robertmhaas(at)gmail(dot)com>:
> 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
>
I'd personally prefer options that could be used in any order as it
means you only have to remember the keywords, not also the order of
them as specified in the documentation. As long as the order doesn't
affect the functioning of the command, I don't see the harm. It just
makes it easier to use.
Thom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-10-16 13:49:54 | Re: BUG #5122: Subqueries - inner select statement bug |
| Previous Message | Heikki Linnakangas | 2009-10-16 13:45:55 | Re: BUG #5123: bug in window function "last_value" |