From: | Linos <info(at)linos(dot)es> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: savepoint problems |
Date: | 2008-08-01 22:38:25 |
Message-ID: | 48939061.1050500@linos.es |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane escribió:
> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>> On Fri, Aug 01, 2008 at 06:30:36PM +0200, Linos wrote:
>>> i have migrated from Maxdb to Postgresql recently and i am having a
>>> speed problem in large transactions over slow links because of autorollback
>
>> If the goal is to reduce latency costs, the best way could be:
>> [ move it to the server side ]
>
> Or move the logic into a server-side function, if you prefer to stick
> with your existing procedural approach.
>
> regards, tom lane
>
when you say move the logic into a server-side function do you mean send the data in a
copy command (or many inserts) to a temporary table and load from here with a server-side
functions like David or Martijn or are you telling me other way to do it, could you
elaborate this please? Thanks.
Regards,
Miguel Angel.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-08-02 01:07:08 | Re: [SQL] Savepoints and SELECT FOR UPDATE in 8.2 |
Previous Message | Linos | 2008-08-01 22:36:24 | Re: savepoint problems |