From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils. |
Date: | 2008-07-16 20:39:38 |
Message-ID: | 1216240778.19656.419.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Yes,
TRUNCATE foo;
TRUNCATE foo;
works well.
So why do we need
TRUNCATE foo, foo;
---------------------------------------------------------------------------
On Wed, 2008-07-16 at 16:24 -0400, Bruce Momjian wrote:
> Logically, you should be able to truncate a table twice.
>
> ---------------------------------------------------------------------------
>
> Simon Riggs wrote:
> >
> > On Wed, 2008-07-16 at 16:54 +0000, Bruce Momjian wrote:
> > > Log Message:
> > > -----------
> > > Allow TRUNCATE foo, foo to succeed, per report from Nikhils.
> >
> > What's the use case for this?
> >
> > It's not compatibility, is it? Why would you ever do that? If you did,
> > why would you expect it to work? Seems more likely to be a user error
> > than a real request.
> >
> > Should it throw one trigger call, or two?
> >
> > BTW, create index foo_idx on foo (col1, col1) fails also with a strange
> > error message. Should we silently merge columns and ignore that also?
> >
> > ERROR: duplicate key value violates unique constraint
> > "pg_attribute_relid_attnam_index"
> >
> > Seems easier to throw errors for weird DDL like this.
> >
> > e.g. create index concurrently on foo (col1); creates an index called
> > "concurrently" on foo, while holding locks...
> >
> > --
> > Simon Riggs www.2ndQuadrant.com
> > PostgreSQL Training, Services and Support
>
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-07-16 21:03:45 | pgsql: Add URL for: * Implement SQL:2003 window functions > > |
Previous Message | Bruce Momjian | 2008-07-16 20:24:00 | Re: pgsql: Allow TRUNCATE foo, foo to succeed, per report from Nikhils. |
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Urbański | 2008-07-16 20:56:55 | avoid recasting text to tsvector when calculating selectivity |
Previous Message | Bruce Momjian | 2008-07-16 20:35:45 | Re: Message-ID should surely not be shown as a mailto: URL |