On Fri, Mar 25, 2011 at 1:00 AM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > 1. The table has been created or truncated in the same transaction > 2. We are not in a subtransaction (or the table was created and truncated in > the same subtransaction) > 3. There are no open portals > 4. Executing the COPY doesn't need to run any "unsafe" code that might > access the same table. This includes triggers, check constraints and input > functions. An expression is safe if it is immutable.
It sounds like these cases would, at the very least, be met by some forms of pg_restore...that's a highly desirable property, I feel. -- fdr -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
