Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils. - Mailing list pgsql-committers

From Simon Riggs
Subject Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils.
Date
Msg-id 1216280938.19656.477.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils.  (Nikhils <nikkhils@gmail.com>)
Responses Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils.  ("Dave Page" <dpage@pgadmin.org>)
List pgsql-committers
On Thu, 2008-07-17 at 11:16 +0530, Nikhils wrote:


> I presented a simple psql version here. I was actually processing
> multiple relations in my C library in which truncate was invoked on
> all the involved relations. I was passing a list of these rels to
> ExecuteTruncate which barfed when the same rel was mentioned twice in
> that list. Its really an implementation issue as Tom mentioned.

So you think we should change Postgres rather than your program?
Many people think that on list, and are ignored.

Why no bug report, proposal or patch? Why during a commit fest?

--
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support


pgsql-committers by date:

Previous
From: Nikhils
Date:
Subject: Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils.
Next
From: "Dave Page"
Date:
Subject: Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils.