postgres-xc-developers Mailing List for Postgres-XC

Michael,

Can you remind me regarding statement_timestamp()? From the commit log:

     This commit supports global timestamp values for now(), 
statement_timestamp,
     transaction_timestamp,current_date, current_time, current_timestamp,
     localtime, local_timestamp and now().

     clock_timestamp and timeofday make their calculation based
     on the local server clock so they get their results from the local 
node where it is run.
     Their use could lead to inconsistencies if used in a transaction 
involving several Datanodes.


For statement_timestamp() do we perform a separate operation through 
GTM, or do we do a delta similar to clock_timestamp()?

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.

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.
> ........(holding)
> log on postgres-xc coordinator:
> LOG:  statement: begin;select * from tt;
> ERROR:  Unexpected response from the data nodes for 'T' message, 
> current request type 1
> STATEMENT:  begin;select * from tt;
> WARNING:  Consuming data node messages after error.
> log on postgres-xc datanode:
> LOG:  statement: BEGIN
> LOG:  statement: begin;select * from tt;
> WARNING:  there is already a transaction in progress

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 will add it to the SF bug tracker.

Thanks,

Mason

> I verified the statement on postgreSQL. It's ok.
> 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
>    


-- 
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.

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.
........(holding)

log on postgres-xc coordinator:
LOG:  statement: begin;select * from tt;
ERROR:  Unexpected response from the data nodes for 'T' message, current
request type 1
STATEMENT:  begin;select * from tt;
WARNING:  Consuming data node messages after error.

log on postgres-xc datanode:
LOG:  statement: BEGIN
LOG:  statement: begin;select * from tt;
WARNING:  there is already a transaction in progress


I verified the statement on postgreSQL. It's ok.

Regards,
Benny