This used to work in 8.2:

psql postgres -c "VACUUM table1; SELECT now()"

But in cvs head it throws an error:
ERROR: VACUUM cannot be executed from a function or multi-command string

This must be because of the recent changes to PreventTransactionChain.

Should we try to keep the old behavior for backwards-compatibility? The
change will break some people's scripts, that's the way I noticed it.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

Search Discussions

  • Heikki Linnakangas at Apr 4, 2007 at 8:57 am
    This used to work in 8.2:

    psql postgres -c "VACUUM table1; SELECT now()"

    But in cvs head it throws an error:
    ERROR: VACUUM cannot be executed from a function or multi-command string

    This must be because of the recent changes to PreventTransactionChain.

    Should we try to keep the old behavior for backwards-compatibility? The
    change will break some people's scripts, that's the way I noticed it.

    --
    Heikki Linnakangas
    EnterpriseDB http://www.enterprisedb.com
  • Tom Lane at Apr 4, 2007 at 2:32 pm

    Heikki Linnakangas writes:
    This used to work in 8.2:
    psql postgres -c "VACUUM table1; SELECT now()"
    But in cvs head it throws an error:
    ERROR: VACUUM cannot be executed from a function or multi-command string
    That's intentional. It "worked" only for rather small values of "work".

    regards, tom lane

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppgsql-hackers @
categoriespostgresql
postedApr 4, '07 at 8:44a
activeApr 4, '07 at 2:32p
posts3
users2
websitepostgresql.org...
irc#postgresql

2 users in discussion

Heikki Linnakangas: 2 posts Tom Lane: 1 post

People

Translate

site design / logo © 2022 Grokbase