Re: Pre-set Hint bits/VACUUM FREEZE on data load..? - Mailing list pgsql-hackers

From Daniel Farina
Subject Re: Pre-set Hint bits/VACUUM FREEZE on data load..?
Date
Msg-id AANLkTimU-wJarzLBMs23a-e5jBUYi-qFhqMceFG80qWs@mail.gmail.com
Whole thread Raw
In response to Re: Pre-set Hint bits/VACUUM FREEZE on data load..?  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Fri, Mar 25, 2011 at 1:00 AM, Heikki Linnakangas
<heikki.linnakangas@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


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Pre-set Hint bits/VACUUM FREEZE on data load..?
Next
From: Heikki Linnakangas
Date:
Subject: Re: Pre-set Hint bits/VACUUM FREEZE on data load..?