Re: Yet another "drop table vs delete" question - Mailing list pgsql-general

From Tom Lane
Subject Re: Yet another "drop table vs delete" question
Date
Msg-id 11492.1240345231@sss.pgh.pa.us
Whole thread Raw
In response to Re: Yet another "drop table vs delete" question  (Christophe <xof@thebuild.com>)
Responses Re: Yet another "drop table vs delete" question  (Christophe <xof@thebuild.com>)
List pgsql-general
Christophe <xof@thebuild.com> writes:
> On Apr 21, 2009, at 12:28 PM, Peter Eisentraut wrote:
>> Yes, but if you are asking that question, you probably really want
>> to use TRUNCATE.

> The advantage of DROP TABLE being, of course, that DROP TABLE is
> transactionally-safe, while TRUNCATE is not.

The above is complete nonsense.  They're both going to drop data that
might conceivably be visible in the snapshot of some concurrent
transaction that hasn't yet touched the table (else it would have lock)
but might wish to do so later.

If you use DELETE, you'll be transactionally safe, but the cost is
concomitantly a lot higher than either DROP or TRUNCATE.

            regards, tom lane

pgsql-general by date:

Previous
From: David Fetter
Date:
Subject: Re: PostgreSQL versus MySQL for GPS Data
Next
From: Steve Crawford
Date:
Subject: Re: COPY 'invalid byte sequence for encoding "UTF8": 0xff'