Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils.

From: Neil Conway <neilc(at)samurai(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: 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-16 21:59:56
Message-ID: 1216245596.13533.7.camel@goldbach
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Wed, 2008-07-16 at 21:39 +0100, Simon Riggs wrote:
> TRUNCATE foo;
> TRUNCATE foo;
>
> works well.
>
> So why do we need
>
> TRUNCATE foo, foo;

For the sake of completeness? Having "TRUNCATE foo, foo" fail would be
rather inconsistent.

-Neil

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2008-07-16 23:06:10 Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils.
Previous Message Bruce Momjian 2008-07-16 21:03:45 pgsql: Add URL for: * Implement SQL:2003 window functions > >

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2008-07-16 22:53:12 Re: [GENERAL] Fragments in tsearch2 headline
Previous Message Jan Urbański 2008-07-16 20:56:55 avoid recasting text to tsvector when calculating selectivity