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

From marek.patrzek@gmail.com
Subject Yet another "drop table vs delete" question
Date
Msg-id 1df90e99-0a4f-461b-80b1-1daa3b111360@c12g2000yqc.googlegroups.com
Whole thread Raw
Responses Re: Yet another "drop table vs delete" question
Re: Yet another "drop table vs delete" question
List pgsql-general
I was wondering if dropping a table is more efficient in PostgreSQL
8.x in comparison to deleting it's content ?

To put you in the picture - I want to schedule via cron job some daily
data materialization. With the resource I got there are only those two
ways:

1) DROP statement:
a) DROP TABLE tmp;
b) CREATE TABLE tmp AS select * from ....;

2) DELETE statement:
a) DELETE FROM tmp;
b) INSERT INTO tmp SELECT * from ....;

tmp table doesn't have any index nor constraints.

The thing is, postgresql may leave some invalid content behind in both
situations. The real question is - which of those two options leaves
less garbage to be vaccumed ? At this point I don't relay care about
cost based efficiency but cutting down pg background work.

pgsql-general by date:

Previous
From: Chris Worley
Date:
Subject: Re: COPY 'invalid byte sequence for encoding "UTF8": 0xff'
Next
From: Robert Morton
Date:
Subject: Re: round behavior differs between 8.1.5 and 8.3.7