Andrew Dunstan <[email protected]> writes:
> Now, we could decide that we always want to do a safe truncate in a
> parallel restore (i.e. if we have created the table in the same
> restore), even if archive_mode is on. Then this switch would be
> redundant, and we might avoid some confusion. I'm inclined to do that
> right now. In that case we could leave for consideration for 8.5 a
> switch providing for a TRUNCATE CASCADE on tables before loading them.
+1. I'm not at all clear on the use-case for a user visible switch
of this sort anyway; it seems more like a foot-gun than something
really helpful.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
