| From: | Naomi Walker <nwalker(at)eldocomp(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Simone Tellini <tellini(at)areabusiness(dot)it>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: restore woes |
| Date: | 2002-02-11 16:46:11 |
| Message-ID: | 4.2.2.20020211094333.00acad70@ecint.ecinet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
>
>
>Adding options to the COPY command is no help either, because the COPY
>may be embedded in a multi-gigabyte dump file that you can't edit
>conveniently. (And what of pg_restore, or other applications that
>generate COPY commands?) My approach of using a GUC variable is better
>because it can be set from outside the dump script --- in
>postgresql.conf, if necessary.
Speaking of COPY, is there a way to tell copy not to barf on errors (and
set how many errors are acceptable)?
Can I tell copy to commit every X rows?
--
Naomi Walker
Chief Information Officer
Eldorado Computing, Inc.
602-604-3100 ext 242
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Naomi Walker | 2002-02-11 16:51:11 | Fwd: Administrative Processing for csitech: getrows |
| Previous Message | Oliver Elphick | 2002-02-11 16:43:34 | Re: Re-nameing a database? |