From: | G u i d o B a r o s i o <gbarosio(at)uolsinectis(dot)com(dot)ar> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: TOAST tables, cannot truncate |
Date: | 2004-09-07 11:12:58 |
Message-ID: | 20040907111258.23BA56C4EA@honorio.sinectis.com.ar |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
Ok, problem solved.
A previous ALTER TABLE DROP COLUMN over this table was performed.
By some reason, truncate didn't work then. Would like to know why...it does not seems to be a very frequent problem, due to the fact I only found one chat on the mailing lists talking about this issue, and was hard to find :( !
A dump of the table schema, passed to the psql command
(cat table_dump.sql | psql xxx) worked fine.
TRUNCATE is now available.
Thanks.
Guido
> Sorry for crossposting, didn't know where to post.
>
> Any hint/help on this?!
>
> db_postgres1=# truncate ref_v2_drs_valid_product ;
> ERROR: expected both swapped tables to have TOAST tables
>
> I need to truncate this table, this is the first time I see this error.
>
> Regards,
> Guido
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
From | Date | Subject | |
---|---|---|---|
Next Message | Goulet, Dick | 2004-09-07 12:21:39 | Re: Asignasr permisos a usuarios |
Previous Message | Christian Hache | 2004-09-07 11:07:18 | Asignasr permisos a usuarios |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-09-07 13:47:47 | Re: The usual sequential scan, but with LIMIT ! |
Previous Message | G u i d o B a r o s i o | 2004-09-07 10:41:07 | TOAST tables, cannot truncate |