st 31. 10. 2018 v 8:55 odesÃlatel Michael Paquier
napsal:
> On Wed, Oct 31, 2018 at 08:38:27AM +0100, Pavel Stehule wrote:
> > ok. Unfortunatelly it is not mentioned in release notes - in not
> compatible
> > changes.
> >
> > This change can hit lot of users. It is small nonsense, but lot of
On Wed, Oct 31, 2018 at 08:38:27AM +0100, Pavel Stehule wrote:
> ok. Unfortunatelly it is not mentioned in release notes - in not compatible
> changes.
>
> This change can hit lot of users. It is small nonsense, but lot of people
> use it.
Please just look at the order of the words in the
On Wed, Oct 31, 2018 at 08:19:35AM +0100, Pavel Stehule wrote:
> I have report of one customer. Some scripts stopped on 11 because VACUUM
> ANALYZE VERBOSE doesn't work now.
>
> postgres=# vacuum analyze verbose;
> ERROR: syntax error at or near "verbose"
> LINE 1: vacuum analyze verbose;
>
st 31. 10. 2018 v 8:34 odesÃlatel Sergei Kornilov napsal:
> Hi
>
> At least this is documented behavior:
> > When the option list is surrounded by parentheses, the options can be
> written in any order. Without parentheses, options must be specified in
> exactly the order shown above.
>
Hi
At least this is documented behavior:
> When the option list is surrounded by parentheses, the options can be written
> in any order. Without parentheses, options must be specified in exactly the
> order shown above.
https://www.postgresql.org/docs/current/static/sql-vacuum.html
Previously
Hi
I have report of one customer. Some scripts stopped on 11 because VACUUM
ANALYZE VERBOSE doesn't work now.
postgres=# vacuum analyze verbose;
ERROR: syntax error at or near "verbose"
LINE 1: vacuum analyze verbose;
^
vacuum verbose analyze is working.
Regards
Pavel
