Re: CLUSTER not in multi-command string? - Mailing list pgsql-admin

From Alvaro Herrera
Subject Re: CLUSTER not in multi-command string?
Date
Msg-id 20090430015117.GF6316@alvh.no-ip.org
Whole thread Raw
In response to Re: CLUSTER not in multi-command string?  (Michael Monnerie <michael.monnerie@is.it-management.at>)
List pgsql-admin
Michael Monnerie wrote:
> On Mittwoch 29 April 2009 Alvaro Herrera wrote:

> > Multi-table cluster (i.e. the one where you don't specify one table
> > to cluster) cannot be used in a transaction block, function, etc, and
> > the FM does mention it:

> Ah, found this now, in the docs 8.1-8.3. But strange thing is..
>
> [I sent this mail this morning at 07:08 local time but it didn't make it
> through, without me getting any note:]

The lists have been dead slow today; I think we have a problem with the
antispam setup, and the admin is off in a trip.  (This is why it's a
good idea to CC people on replies.)

> I looked further now: Above error was from Postgres 8.3.5 on openSUSE
> 11.1, but it works on Postgres 8.1.11 from openSUSE 10.2. Why did
> it become worse?

Well, it became more consistent with what happens when you submit stuff
on several requests versus a single request (IIRC psql -c always submit the
string as a single request).  The 8.3 release notes have:

# Commands rejected in transaction blocks are now also rejected in
  multiple-statement query strings (Tom)
    For example, "BEGIN; DROP DATABASE; COMMIT" will now be rejected
    even if submitted as a single query message.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-admin by date:

Previous
From: Michael Monnerie
Date:
Subject: Re: Rather large Postgres directory
Next
From: Alvaro Herrera
Date:
Subject: Re: CLUSTER not in multi-command string?