| From: | Hervé Piedvache <herve(at)elma(dot)fr> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: DELETE TABLE xx do not erase index file after a vacuum full ? |
| Date: | 2004-07-02 07:50:56 |
| Message-ID: | 200407020950.56490.herve@elma.fr |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom,
Le jeudi 1 Juillet 2004 19:22, Tom Lane a écrit :
> =?iso-8859-15?q?Herv=E9_Piedvache?= <herve(at)elma(dot)fr> writes:
> > I have done a :
> > DELETE from my_table;
>
> TRUNCATE would serve you a lot better.
Impossible for this table because it's used by another table with a
referential integrity ... so truncate is refused ...
> For major reductions in table size VACUUM FULL is not the best tool;
> you really want to reconstruct the indexes from scratch. Consider
> REINDEX, CLUSTER, or (in this case) TRUNCATE.
>
OK Thanks REINDEX is perfect ! ;o)
regards,
--
Hervé Piedvache
Elma Ingénierie Informatique
6 rue du Faubourg Saint-Honoré
F-75008 - Paris - France
Pho. 33-144949901
Fax. 33-144949902
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shridhar Daithankar | 2004-07-02 09:03:38 | Re: Enough RAM for entire Database.. cost aside, is this |
| Previous Message | Dennis Gearon | 2004-07-02 06:22:32 | administrating permisions, groups, owners |