| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Nikhils <nikkhils(at)gmail(dot)com> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils. |
| Date: | 2008-07-17 07:48:58 |
| Message-ID: | 1216280938.19656.477.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2008-07-17 08:00:53 | Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils. |
| Previous Message | Nikhils | 2008-07-17 05:46:40 | Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2008-07-17 08:00:53 | Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils. |
| Previous Message | David Fetter | 2008-07-17 07:28:59 | Re: introduction of WIP window function patch |