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