| From: | Marko Kreen <marko(at)l-t(dot)ee> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Restoring large tables with COPY |
| Date: | 2001-12-11 17:25:51 |
| Message-ID: | 20011211172551.GA5065@l-t.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 11, 2001 at 10:55:30AM -0500, Tom Lane wrote:
> Marko Kreen <marko(at)l-t(dot)ee> writes:
> > Maybe I am missing something obvious, but I am unable to load
> > larger tables (~300k rows) with COPY command that pg_dump by
> > default produces.
>
> I'd like to find out what the problem is, rather than work around it
> with such an ugly hack.
Hmm, the problem was more 'interesting' than I thought.
Basically:
1) pg_dump of 7.1.3 dumps constraints and primary keys
with table defs in this case, so they are run during COPY.
2) I have some tricky CHECK contraints.
Look at the attached Python script, it reproduces the problem.
Sorry, cannot test on 7.2 at the moment.
--
marko
| Attachment | Content-Type | Size |
|---|---|---|
| xx.py | text/plain | 659 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Serguei Mokhov | 2001-12-11 17:29:07 | Re: Restoring large tables with COPY |
| Previous Message | Marko Kreen | 2001-12-11 16:19:36 | Re: Restoring large tables with COPY |