Re: idea for concurrent seqscans

From: Jeff Davis <jdavis-pgsql(at)empires(dot)org>
To: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: idea for concurrent seqscans
Date: 2005-02-26 00:30:17
Message-ID: 1109377818.4089.183.camel@jeff
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2005-02-25 at 18:03 -0600, Jim C. Nasby wrote:
> On Fri, Feb 25, 2005 at 01:30:57PM -0500, Tom Lane wrote:
> > Jeff Davis <jdavis-pgsql(at)empires(dot)org> writes:
> > > I didn't consider that. Is there a reason the regression tests assume
> > > the results will be returned in a certain order (or a consistent order)?
> >
> > We use diff as the checking tool.
>
> Doesn't the SQL spec specifically state that the only time you'll get
> results in a deterministic order is if you use ORDER BY? Assuming
> otherwise seems a bad idea (though at least in the case of testing it
> makes the test more strenuous rather than less...)

True, that was my reasoning when I proposed synchronized scanning.

Keep in mind that this is a criticism of only the regression tests, not
the RDBMS itself.

I don't know much about the regression tests, so maybe it's impractical
to not assume consistent order. I'm sure the developers will vote one
way or the other. I hate to throw away a potential performance boost,
but I also hate to burden the developers with rewriting a lot of
regression tests when their time could be better spent elsewhere.

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-02-26 01:51:40 Re: idea for concurrent seqscans
Previous Message Jim C. Nasby 2005-02-26 00:11:30 Re: Modifying COPY TO