I am ok with the changes in the test. It worked fine for me.
On Mon, Apr 22, 2013 at 3:10 PM, Ashutosh Bapat <
ash...@en...> wrote:
> Hi All,
> The testcase was failing because of change in the query plans (because of
> LIMIT optimization) and queries returning unpredictable results (because of
> lack of order by clause). I have corrected the plans and added order by
> clause to the queries.
>
> There is only one query (multiple instances) which needed order by clause.
> It's
> select * from patest0 join (select f1 from int4_tbl limit 1) ss on id = f1
> Since the first row inserted in int4_tbl has f1 = 0, the subquery "select
> f1 from int4_tbl limit 1" returns 0 in PG, whereas that may not be true in
> XC, hence we need to add order by and where clause to make sure that the
> subquery returns 0.
>
> I found that inherit.out and inherit_1.out had more than differences
> necessary (only differences expected were those because of tableoid). I
> have removed those differences.
> --
> Best Wishes,
> Ashutosh Bapat
> EntepriseDB Corporation
> The Postgres Database Company
>
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>
--
--
*Abbas*
Architect
Ph: 92.334.5100153
Skype ID: gabbasb
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB
Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>
|
