From: Josh Berkus <josh@agliodbs.com>
To: jack <datactrl@tpg.com.au>
To: pgsql-sql@postgresql.org
Subject: Re: problem on truncate for v.7.3.2
Date: Wed, 19 Feb 2003 22:14:24 -0800
Message-ID: <200302192214.24999.josh@agliodbs.com> (raw)
In-Reply-To: <002b01c2d8a3$53f10b10$1400a8c0@jac>
References: <002b01c2d8a3$53f10b10$1400a8c0@jac>
Jack,
> On version 7.3.2, 'truncate' can not be executed from pl/pgsql. But it
> isn't stated on change notes. Is it a bug?
No, it's a fix.
TRUNCATE, VACUUM, ANALYZE, and REINDEX all perform COMMIT statements as part
of their operation. If called within a function, this could cause part of
the function to be committed while the rest failed, or even cause a fatal
error.
As such, these statements have been deliberately disabled within PL/pgSQL and
SQL functions.
--
Josh Berkus
Aglio Database Solutions
San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, datactrl@tpg.com.au
Subject: Re: problem on truncate for v.7.3.2
In-Reply-To: <200302192214.24999.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox