From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: jack <datactrl@tpg.com.au>
Cc: pgsql-sql@postgresql.org
Subject: Re: problem on truncate for v.7.3.2
Date: Thu, 20 Feb 2003 10:13:39 -0500
Message-ID: <22177.1045754019@sss.pgh.pa.us> (raw)
In-Reply-To: <200302192214.24999.josh@agliodbs.com>
References: <002b01c2d8a3$53f10b10$1400a8c0@jac>
<200302192214.24999.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
>> 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.
Note however that TRUNCATE has been reimplemented to be transaction-safe
in 7.4, and so the restriction has gone away again.
regards, tom lane
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: tgl@sss.pgh.pa.us, josh@agliodbs.com, datactrl@tpg.com.au
Subject: Re: problem on truncate for v.7.3.2
In-Reply-To: <22177.1045754019@sss.pgh.pa.us>
* 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