Re: [HACKERS] Vacuum in multi-statement

2007-04-04 Thread Tom Lane 
Heikki Linnakangas <[EMAIL PROTECTED]> 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

---(end of broadcast)---
TIP 6: explain analyze is your friend

[HACKERS] Vacuum in multi-statement

2007-04-04 Thread Heikki Linnakangas 

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

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings

[HACKERS] Vacuum in multi-statement

2007-04-04 Thread Heikki Linnakangas 

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

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
  choose an index scan if your joining column's datatypes do not
  match