How about departing into the same number if insert statements as there are nodes? That way we just send one insert to each.
I think if the user/app uses this, they may be concerned about efficiency and performance, so I think passing in just a single statement to the data nodes is a good idea.
Regards,
Mason
Sent from my IPhone
On Dec 7, 2010, at 8:56 AM, xiong wang <wan...@gm...> wrote:
> Dears,
>
> I have two solutions to resolve the bug#3013562.
>
> 1. I will rewrite insert statement if it is an mutiple insert. I will
> deparse the mutiple insert statement into single insert statements
> which count is the same as values_list in function pg_rewrite_query.
> 2. I would like to use prepare statement to replace an mutiple insert.
> In other word, during a mutiple insert statement executing, I will use
> a prepare statement node to replace the mutiple insert statement node.
>
> The main idea of all above solutions is divided mutiple insert into
> single insert. I don't know whether two methods are feasible or which
> one will be better. Could you give me some suggestions?
>
> If you have other idea, please don't hesitate to tell me.
>
> Thanks.
>
> Regards,
> Benny
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
|
