| From: | "Dann Corbit" <DCorbit(at)connx(dot)com> | 
|---|---|
| To: | "Jason M(dot) Felice" <jfelice(at)cronosys(dot)com>, <pgsql-hackers(at)postgresql(dot)org> | 
| Cc: | <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: No merge sort? | 
| Date: | 2003-04-07 20:39:20 | 
| Message-ID: | D90A5A6C612A39408103E6ECDD77B8294CDACC@voyager.corporate.connx.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
> -----Original Message-----
> From: Jason M. Felice [mailto:jfelice(at)cronosys(dot)com] 
> Sent: Monday, April 07, 2003 1:10 PM
> To: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] No merge sort?
> 
> 
> On Mon, Apr 07, 2003 at 03:36:10PM -0400, Greg Stark wrote:
> > "Ron Peacetree" <rjpeace(at)earthlink(dot)net> writes:
> > 
> > > AFAIK, there are only 3 general purpose internal sorting 
> techniques 
> > > that have O(n) behavior:
> > 
> > Strictly speaking there are no sorting algorithms that have 
> worst-case 
> > time behaviour better than O(nlog(n)). Period.
> > 
> 
> Not true.
> 
http://www.elsewhere.org/jargon/html/entry/bogo-sort.html
He said "better than" not "worse than".
For comparison based sorting it is _provably_ true that you cannot sort
faster than log(n!) which is O(n*(log(n))).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2003-04-07 20:50:03 | Re: No merge sort? | 
| Previous Message | Dann Corbit | 2003-04-07 20:34:27 | Re: No merge sort? |