Re: Suppressing occasional failures in copy2 regression test

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Fetter <david(at)fetter(dot)org>
Cc: Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Suppressing occasional failures in copy2 regression test
Date: 2009-06-15 15:34:38
Message-ID: 16805.1245080078@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Fetter <david(at)fetter(dot)org> writes:
> * It's going to a lot of trouble to allow for the possibility of both
> unordered results and of duplicate lines. If we disallow duplicate
> lines in unordered result sets, we can get a big speed gain by using
> hash-based comparisons.

Why not just sort the lines and compare?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2009-06-15 16:30:37 Re: Suppressing occasional failures in copy2 regression test
Previous Message David Fetter 2009-06-15 15:31:03 Re: Suppressing occasional failures in copy2 regression test