Horton

Re: [HACKERS] TRUNCATE TABLE with IDENTITY

Simon Riggs <simon@2ndquadrant.com>

View thread View on postgr.es
From: Simon Riggs <simon@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Neil Conway <neilc@samurai.com>, Zoltan Boszormenyi <zb@cybertec.at>, List pgsql-patches <pgsql-patches@postgresql.org>, Decibel! <decibel@decibel.org>, Steve Crawford <scrawford@pinpointresearch.com>, pgsql-hackers@postgresql.org
Date: 2008-05-17T08:58:10Z
Lists: pgsql-hackers 
On Fri, 2008-05-16 at 21:50 -0400, Tom Lane wrote:
> Neil Conway <neilc@samurai.com> writes:
> > Ugh. The fact that the RESTART IDENTITY part of TRUNCATE is
> > non-transactional is a pretty unsightly wort.
> 
> Actually, I agree.  Shall we just revert that feature?  The ALTER
> SEQUENCE part of this patch is clean and useful, but I'm less than
> enamored of the TRUNCATE part.

Perhaps, but we should also take into account that TRUNCATE is not and
never will be MVCC compliant, so its not something you'd expect to run
except as a maintenance action. If we do keep it, I would suggest that
we add a WARNING so that the effects are clearly recorded.

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