Re: Path question

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hans-Jürgen Schönig <hs(at)cybertec(dot)at>, Greg Stark <gsstark(at)mit(dot)edu>, Boszormenyi Zoltan <zb(at)cybertec(dot)at>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Path question
Date: 2010-09-25 02:23:07
Message-ID: AANLkTimL+WYk_5mOsqJCoU+4vO7B7ffM7anGXcVQf8pN@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 24, 2010 at 5:05 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It's not that hard if you just tweak equivclass.c to make the order of
> equivalence-class lists different, viz
[...]
> Since the order of equivalence-class member lists isn't supposed to be
> semantically significant, I claim that the code in createplan has to
> be able to deal with this.
[...]
> That's not a reason for it not to handle
> the case, though.

I'm not disputing that those tests are correct. All I'm saying is
that I can't figure out a way to write regression tests that fail if
they are removed.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-09-25 03:11:34 Re: pgsql: git_topo_order script, to match up commits across branches.
Previous Message Robert Haas 2010-09-25 02:20:54 Re: pgsql: git_topo_order script, to match up commits across branches.