On Wed, Aug 13, 2008 at 2:07 AM, Sabin Coanda
<[EMAIL PROTECTED]> wrote:
>>
>> have you considered importing to a temporary 'holding' table with
>> copy, then doing 'big' sql statements on it to check constraints, etc?
>>
>
> Yes I considered it, but the problem is the data is very tight related
>
>
> have you considered importing to a temporary 'holding' table with
> copy, then doing 'big' sql statements on it to check constraints, etc?
>
Yes I considered it, but the problem is the data is very tight related
between different tables and is important to keep the import order of each
entit
On Tue, Aug 12, 2008 at 4:17 AM, Sabin Coanda
<[EMAIL PROTECTED]> wrote:
>> long running transactions can be evil. is there a reason why this has
>> to run in a single transaction?
>
> This single transaction is used to import new information in a database. I
> need it because the database cannot b
> long running transactions can be evil. is there a reason why this has
> to run in a single transaction?
This single transaction is used to import new information in a database. I
need it because the database cannot be disconected from the users, and the
whole new data has to be consistently. T
On Mon, Aug 11, 2008 at 2:53 AM, Sabin Coanda
<[EMAIL PROTECTED]> 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
> 3 statements without transacti
age
news:[EMAIL PROTECTED]
> have you use VACUMM?
>
> --- On Fri, 7/18/08, Sabin Coanda <[EMAIL PROTECTED]> wrote:
>
>> From: Sabin Coanda <[EMAIL PROTECTED]>
>> Subject: [PERFORM] long transaction
>> To: pgsql-performance@postgresql.org
>> Date: Friday,
have you use VACUMM?
--- On Fri, 7/18/08, Sabin Coanda <[EMAIL PROTECTED]> wrote:
> From: Sabin Coanda <[EMAIL PROTECTED]>
> Subject: [PERFORM] long transaction
> To: pgsql-performance@postgresql.org
> Date: Friday, July 18, 2008, 3:34 PM
> Hi there,
>
> I h
Hi there,
I have a script which includes 3 called functions within a single
transaction.
At the beginning, the functions runs fast enough (about 60 ms each). In
time, it begins to run slower and slower (at final about one per 2 seconds).
I check the functions that runs slowly outside the s
