Excerpts from Andy Colson's message of vie dic 03 00:37:17 -0300 2010:
> Ok, forget the time thing. Has nothing to do with it. (Which everyone already assumed I imagine).
>
> Its truncate.
>
> Create unloged table, fill it, truncate it, fill it again, restart pg, and the data will still be there.
Hmm, presumably the table rewrite thing in truncate is not preserving
the unlogged state (perhaps it's the swap-relfilenode business). Does
CLUSTER have a similar effect? What about VACUUM FULL? If so you know
where the bug is.
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support