| From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: COPY command details |
| Date: | 2007-03-29 20:25:09 |
| Message-ID: | 460C20A5.1050909@cox.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/29/07 14:51, Benjamin Arai wrote:
> I would prefer not to drop the index because the database is several
> hundred gigs. I would prefer to incrementally add to the index.
Some RDBMSs (well, one that I know of) has the ability to defer
index updates during data load, and it actually works very well.
The down side is that if there's a unique value constraint failure,
you don't know which record it failed on.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGDCClS9HxQb37XmcRAo0pAKCwqYwXOAPIXK25L9zhWhtGMFi/hwCgtA+x
zgc5Bz8wrVQ5UGocGe5v3s4=
=aFmR
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Toke Høiland-Jørgensen | 2007-03-29 20:52:16 | Re: Btree indexes, large numbers and <= comparisons |
| Previous Message | Bruce Momjian | 2007-03-29 20:22:44 | Re: COPY command details |