Re: Slow delete/insert.

From: "Alexandre Leclerc" <alexandre(dot)leclerc(at)gmail(dot)com>
To: "Thor Tall" <tall_thor(at)yahoo(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Slow delete/insert.
Date: 2006-08-24 12:08:40
Message-ID: 1dc7f0e30608240508t49a208acnbe26769e1b6f669d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

All this is prety straight forward.

As for the transaction you are crating, is the process of 'split
message' actually do on the DB side or are you doing this process on
you side? Maybe this is the actual work of splitting the message by
the DB that is very slow.

/Maybe/ if you do this data-processing on your side, then sending that
to the DB will save you time. If you really want that job being done
on the server side, you could build yourself an extension module
adding a special function that you would call to do the job. Maybe you
could win couple cycles...

But all that could be confirmed or not by someone else which knows
more about PG internals.

Best regards.

--
Alexandre Leclerc

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Gary Stainburn 2006-08-24 12:43:00 yum update now gives me UNICODE errors
Previous Message Thor Tall 2006-08-24 08:24:31 Re: Slow delete/insert.