Skip site navigation (1) Skip section navigation (2)

Re: Drop table vs begin/end transaction

From: Francisco Reyes <lists(at)natserv(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pgsql Novice <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Drop table vs begin/end transaction
Date: 2001-11-18 21:01:52
Message-ID: 20011118160004.B70739-100000@zoraida.natserv.net (view raw or flat)
Thread:
Lists: pgsql-novice
On Sun, 18 Nov 2001, Tom Lane wrote:

> Francisco Reyes <lists(at)natserv(dot)com> writes:
> > My alternative is to use delete from <table>. Besides been slower I wonder
> > if this would not make my "vacuum analyze" run much slower.
>
> Consider TRUNCATE TABLE

Thanks for the info. Didn't know about truncate table

> so the drop/create/fill might be a better bet if you are worried
> about bad data during the fill.

I just had such a case. The table I was importing had a '\' and postgreSQL
didn't like it. I guess it must have some special meaning.


In response to

Responses

pgsql-novice by date

Next:From: Francisco ReyesDate: 2001-11-18 21:12:50
Subject: When is it worth it to drop indexes on bulk loads?
Previous:From: Tom LaneDate: 2001-11-18 05:37:34
Subject: Re: Drop table vs begin/end transaction

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group