From: | Thor Tall <tall_thor(at)yahoo(dot)com> |
---|---|
To: | Alexandre Leclerc <alexandre(dot)leclerc(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Slow delete/insert. |
Date: | 2006-08-24 13:02:08 |
Message-ID: | 20060824130209.47857.qmail@web50303.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
The messages are split on the client side and PQexec
are called with INSERT/DELETE statements.
I have seen that I could use PQprepare and
PQexecPrepared but I doubt that it would help a lot to
use those functions?
/Thor
--- Alexandre Leclerc <alexandre(dot)leclerc(at)gmail(dot)com>
wrote:
> 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
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alexandre Leclerc | 2006-08-24 13:32:37 | Re: Slow delete/insert. |
Previous Message | Gary Stainburn | 2006-08-24 12:43:00 | yum update now gives me UNICODE errors |