postgres-xc-general

[Postgres-xc-general] Strange select behavior when using order by

[Adam M. <ada...@gm...>]

I'm evaluating XC to store geo data across multiple servers, but I'm seeing
strange behavior in early testing.

xc_storage=# select id from geo_store where id in (19700858, 19983820);
    id
----------
 19983820
 19700858
(2 rows)

xc_storage=# select id from geo_store where id in (19700858, 19983820)
order by id;
    id
----------
 19700858
 19983820
(2 rows)

Logs from one data node

2013-01-04 15:01:44 CST [19733]: [193-1] LOG:  duration: 0.000 ms
 statement: SELECT id FROM geo_store WHERE (id = ANY (ARRAY[19700858,
19983820]))

2013-01-04 15:02:15 CST [19733]: [194-1] LOG:  duration: 0.000 ms
 statement: SELECT id, user_ref, geo_data, distance, created_date,
updated_date, uuid FROM ONLY geo_store WHERE (id = ANY
('{19700858,19983820}'::integer[]))

Why does the addition of the order by statement result in a select of all
columns in the geo_store table on the data node? Any way around this?

Thanks,

--
Adam McManus

Re: [Postgres-xc-general] Strange select behavior when using order by

[Abbas B. <abb...@en...>]

I tried your test case on latest head and found that the query sent to the
data node does not contain any extra columns.
I think this might be attributed to this commit
35a6dee96d84c70f4984a7dd5ea67d91d591546e
Are you testing the version that contains this commit or not?

I think XC version 1.0 or 1.0.1 does not contain this commit.

Regards


On Sat, Jan 5, 2013 at 2:11 AM, Adam McManus <ada...@gm...> wrote:

> I'm evaluating XC to store geo data across multiple servers, but I'm
> seeing strange behavior in early testing.
>
> xc_storage=# select id from geo_store where id in (19700858, 19983820);
>     id
> ----------
>  19983820
>  19700858
> (2 rows)
>
> xc_storage=# select id from geo_store where id in (19700858, 19983820)
> order by id;
>     id
> ----------
>  19700858
>  19983820
> (2 rows)
>
> Logs from one data node
>
> 2013-01-04 15:01:44 CST [19733]: [193-1] LOG:  duration: 0.000 ms
>  statement: SELECT id FROM geo_store WHERE (id = ANY (ARRAY[19700858,
> 19983820]))
>
> 2013-01-04 15:02:15 CST [19733]: [194-1] LOG:  duration: 0.000 ms
>  statement: SELECT id, user_ref, geo_data, distance, created_date,
> updated_date, uuid FROM ONLY geo_store WHERE (id = ANY
> ('{19700858,19983820}'::integer[]))
>
> Why does the addition of the order by statement result in a select of all
> columns in the geo_store table on the data node? Any way around this?
>
> Thanks,
>
> --
> Adam McManus
>
>
> ------------------------------------------------------------------------------
> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
> much more. Get web development skills now with LearnDevNow -
> 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122812
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>


-- 
--
Abbas
Architect
EnterpriseDB Corporation
The Enterprise PostgreSQL Company

Phone: 92-334-5100153

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.

Re: [Postgres-xc-general] Strange select behavior when using order by

[Ashutosh B. <ash...@en...>]

Hi Adam,
This has been fixed in the current head and will be available in the
next release.

On Sat, Jan 5, 2013 at 2:41 AM, Adam McManus <ada...@gm...> wrote:
> I'm evaluating XC to store geo data across multiple servers, but I'm seeing
> strange behavior in early testing.
>
> xc_storage=# select id from geo_store where id in (19700858, 19983820);
>     id
> ----------
>  19983820
>  19700858
> (2 rows)
>
> xc_storage=# select id from geo_store where id in (19700858, 19983820) order
> by id;
>     id
> ----------
>  19700858
>  19983820
> (2 rows)
>
> Logs from one data node
>
> 2013-01-04 15:01:44 CST [19733]: [193-1] LOG:  duration: 0.000 ms
> statement: SELECT id FROM geo_store WHERE (id = ANY (ARRAY[19700858,
> 19983820]))
>
> 2013-01-04 15:02:15 CST [19733]: [194-1] LOG:  duration: 0.000 ms
> statement: SELECT id, user_ref, geo_data, distance, created_date,
> updated_date, uuid FROM ONLY geo_store WHERE (id = ANY
> ('{19700858,19983820}'::integer[]))
>
> Why does the addition of the order by statement result in a select of all
> columns in the geo_store table on the data node? Any way around this?
>
> Thanks,
>
> --
> Adam McManus
>
> ------------------------------------------------------------------------------
> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
> much more. Get web development skills now with LearnDevNow -
> 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122812
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>



-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Enterprise Postgres Company