| From: | Daniel Farina <daniel(at)heroku(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Pre-set Hint bits/VACUUM FREEZE on data load..? |
| Date: | 2011-03-25 08:05:42 |
| Message-ID: | AANLkTimU-wJarzLBMs23a-e5jBUYi-qFhqMceFG80qWs@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 25, 2011 at 1:00 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-03-25 08:09:42 | Re: Pre-set Hint bits/VACUUM FREEZE on data load..? |
| Previous Message | Heikki Linnakangas | 2011-03-25 08:00:50 | Re: Pre-set Hint bits/VACUUM FREEZE on data load..? |