Re: [Postgres-xc-developers] bug:Sending begin;commad

[Mason S. <mas...@en...>]

On 11/29/10 9:10 PM, xiong wang wrote:
> Dears,
> >>On 11/29/10 4:32 AM, xiong wang wrote:
> >> Dears,
> >> step as follows:
> >>./psql -Upostgres -p 5432 -c 'create table tt(a int);'
> >> CREATE TABLE
> >> ./psql -Upostgres -c 'begin;select * from tt;';
> >> WARNING:  Consuming data node messages after error.
>
> >We send a begin down to the data nodes implicitly. It looks like if the
> >first statement is a BEGIN we should suppress that (but send a valid
> >response).
>
> I should describe the bug a little more.
> It seems that postgres-XC can't process the statement combined 
> by mutiple statements seperated by semicolon
> for example
> 1.
> ./psql -Upostgres -d template1 -p 5432 -c 'checkpoint;select * from t'
> WARNING:  Consuming data node messages after error.
> (note:all nodes(coordinator and datanodes) logs are similar with the bug)
> 2.
> template1=# \d t
>        Table "public.t"
>  Column |  Type   | Modifiers
> --------+---------+-----------
>  a      | integer |
> template1=# \d t1
>       Table "public.t1"
>  Column |  Type   | Modifiers
> --------+---------+-----------
>  a      | integer |
>  b      | integer |
> template1=# select * from t;
>  a
> ---
>  1
> (1 row)
> template1=# select * from t1;
>  a | b
> ---+---
>  1 | 1
> (1 row)
> ./psql -Upostgres -d template1 -c 'select * from t;select * from t1;'
> unexpected field count in "D" message
> ERROR:  Tuple does not match the descriptor
> 3.
> template1=# create table t2(a int);
> CREATE TABLE
> template1=# insert into t2 values(2);
> INSERT 0 1
> template1=# \q
> ./psql -Upostgres -d template1 -p 5432 -c 'select * from t2;select * 
> from t'
>  a
> ---
>  2
>  1
> (2 rows)
Thanks, I updated the case. Feel free also to just add comments directly 
there in the future.

Thanks,

Mason

-- 
Mason Sharp
EnterpriseDB Corporation
The Enterprise Postgres Company


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.