| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, Hannu Krosing <hannu(at)skype(dot)net>, pgsql-hackers(at)postgresql(dot)org, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: VLDB Features |
| Date: | 2007-12-15 06:12:58 |
| Message-ID: | 6430.1197699178@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> There's no way we can do a transactionless load, then? I'm thinking of the
> load-into-new-partition which is a single pass/fail operation. Would
> ignoring individual row errors in for this case still cause these kinds of
> problems?
Given that COPY fires triggers and runs CHECK constraints, there is no
part of the system that cannot be exercised during COPY. So I think
supposing that we can just deal with some simplified subset of reality
is mere folly.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-12-15 07:24:21 | Re: Negative LIMIT and OFFSET? |
| Previous Message | Neil Conway | 2007-12-15 05:10:35 | Re: EXPLAIN ANALYZE printing logical and hardware I/O per-node |