| From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "Sabin Coanda" <sabin(dot)coanda(at)deuromedia(dot)ro> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: long transaction |
| Date: | 2008-08-11 19:03:10 |
| Message-ID: | b42b73150808111203l14df2d2dicd4350f04d64e838@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Aug 11, 2008 at 2:53 AM, Sabin Coanda
<sabin(dot)coanda(at)deuromedia(dot)ro> wrote:
> No, I cannot use VACUUM inside the transaction, and it seems this is the
> problem, although autovacuum is set.
>
> However I checked the following scenario to find a solution. I call the
> 30000 statements without transaction. The performance it not changed. But
> when I add VACUUM command after each 20 statement set, I got the linear
> performance that I want. Unfortunatelly this is not possible inside a
> transaction.
>
> Do you know how could I solve my problem, keeping the 30000 statements
> inside a single transaction ?
long running transactions can be evil. is there a reason why this has
to run in a single transaction?
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sabin Coanda | 2008-08-12 08:17:12 | Re: long transaction |
| Previous Message | Craig James | 2008-08-11 16:03:58 | Re: Using PK value as a String |