| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Quan Zongliang <quanzongliang(at)gmail(dot)com> |
| Cc: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: Import: I need help |
| Date: | 2009-02-13 09:43:23 |
| Message-ID: | 937d27e10902130143l68caf6ew68f54daf26a8c167@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Fri, Feb 13, 2009 at 9:21 AM, Quan Zongliang <quanzongliang(at)gmail(dot)com> wrote:
> And more one question:
> I think the import work should get a new PGconn instance before it starts.
> in document: http://www.postgresql.org/docs/8.3/static/libpq-copy.html said:
> It is not possible to execute other SQL commands using the same connection
> while the COPY operation is in progress.
>
> How about the INSERT command?
> When them start work within a new transaction. It seems to fall into same situation.
Yes, - you should certainly use a new connection to avoid any conflict
with the main browser. What would be really cool (later, not now)
would be to divide the workload amongst a user-defined number of
parallel connections.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Quan Zongliang | 2009-02-13 09:55:53 | Patch: when select bit varying type, column length can be inputted |
| Previous Message | Quan Zongliang | 2009-02-13 09:36:15 | Re: Import: I need help |