| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Matt Van Mater <matt(dot)vanmater(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: psql vs perl prepared inserts |
| Date: | 2005-04-13 14:31:11 |
| Message-ID: | 20050413143111.GA7225@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 13, 2005 at 09:57:09 -0400,
Matt Van Mater <matt(dot)vanmater(at)gmail(dot)com> wrote:
>
> Also, I forgot to mention earlier that I tried using transactions to
> speed things up, but since I expect to see certain inserts fail I
> would need to rework my code so the whole transaction doesn't fail if
> one insert goes bad. This is somewhat contrary to the purpose of
> transactions so I'm not sure how to accomplish this. I saw roughly a
> 20% speed improvement by turning autocommit off and only committing at
> the end of parsing each file.
You might get a small benefit using savepoints in version 8.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Robinson | 2005-04-13 14:50:16 | Re: Composite type versus Domain constraints. |
| Previous Message | Matt Van Mater | 2005-04-13 13:57:09 | Re: psql vs perl prepared inserts |