Re: Avoid parallel full and right join paths.

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: Avoid parallel full and right join paths.
Date: 2016-04-21 01:52:06
Message-ID: CAM3SWZTRwt3hEwVvhUfZGyHBgUZoN53NWGKvLrAshfn3M+sz5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 20, 2016 at 6:43 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> The brin.sql test does that ...

I actually copied brin.sql when creating regression tests for external
sorting, primarily because I wanted to test a variety of collations,
without having any control of what they happen to be on the target.
Those went into amcheck's regression tests, and so have yet to be
committed.

I think that your approach there has plenty to recommend it, at least
where requirements are more complicated.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2016-04-21 01:57:35 Re: Typos/Questions in bloom documentation
Previous Message Noah Misch 2016-04-21 01:50:52 Re: VS 2015 support in src/tools/msvc