Re: [Postgres-xc-developers] prepare statement bug

[Andrei.Martsinchyk <and...@en...>]

Hi Benny,

Thanks for pointing this out. I tested with a program using Postgres C
library and extended query protocol.
For you and anyone else who want to test I am attaching the test
program and simple Makefile.
I fixed the segmentation fault (updated patch is attached), but
anyway, PREPARE / EXECUTE commands do not work properly.
The problem with it of the same kind as reported by you (sending
begin;command;).
We are using original SQL statement to build up statement for
datanodes. In some cases pure command text is not available - it
contains garbage, like neighbour statement or ouiter command (PREPARE
... AS).
Postgres parser does not split command, it just produces multiple
Query trees, or inner Query.
We want the command being sent to datanodes is built up based on the
Query produced by parser, taking into account planner info. We are
working on this.

2010/12/1 xiong wang <wan...@gm...>:
> Dears,
>
> template1=# prepare a(int) as insert into t values($1);
> LOG:  statement: prepare a(int) as insert into t values($1);
>
> server closed the connection unexpectedly
>  This probably means the server terminated abnormally
>  before or while processing the request.
> The connection to the server was lost. Attempting reset: LOG:  server
> process (PID 26936) was terminated by signal 11: Segmentation fault
> LOG:  terminating any other active server processes
> WARNING:  terminating connection because of crash of another server process
> DETAIL:  The postmaster has commanded this server process to roll back the
> current transaction and exit, because another server process exited
> abnormally and possibly corrupted shared memory.
> HINT:  In a moment you should be able to reconnect to the database and
> repeat your command.
> WARNING:  terminating connection because of crash of another server process
> DETAIL:  The postmaster has commanded this server process to roll back the
> current transaction and exit, because another server process exited
> abnormally and possibly corrupted shared memory.
> HINT:  In a moment you should be able to reconnect to the database and
> repeat your command.
> Failed.
>
> Regards,
> Benny
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>



-- 
Andrei Martsinchyk

EntepriseDB Corporation
The Enterprise Postgres Company

Website: www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb

This e-mail message (and any attachment) is intended for the use of
the individual or entity to whom it is addressed. This message
contains information from EnterpriseDB Corporation that may be
privileged, confidential, or exempt from disclosure under applicable
law. If you are not the intended recipient or authorized to receive
this for the intended recipient, any use, dissemination, distribution,
retention, archiving, or copying of this communication is strictly
prohibited. If you have received this e-mail in error, please notify
the sender immediately by reply e-mail and delete this message.