| From: | Yang Zhang <yanghatespam(at)gmail(dot)com> | 
|---|---|
| To: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> | 
| Cc: | Frank Heikens <frankheikens(at)mac(dot)com>, pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: Sorting performance vs. MySQL | 
| Date: | 2010-02-22 18:36:48 | 
| Message-ID: | 9066fa251002221036w223fef8bqe780113bee2875b1@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
On Mon, Feb 22, 2010 at 1:30 PM, Richard Broersma
<richard(dot)broersma(at)gmail(dot)com> wrote:
> On Mon, Feb 22, 2010 at 10:17 AM, Frank Heikens <frankheikens(at)mac(dot)com> wrote:
>
>> There is no index on the column transactionid in your PostgreSQL-table, as
>> there is in your MySQL-table. This explains the difference.
>>
>> CREATE INDEX i_transactionid ON public.metarelcloud_transactionlog
>> (transactionid);
>
> Does an index help a sort operation in PostgreSQL?
I also share the same doubt. An external merge-sort needs to make
complete passes over the entire dataset, with no index-directed
accesses.
-- 
Yang Zhang
http://www.mit.edu/~y_z/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jignesh Shah | 2010-02-22 18:39:17 | Re: Questions regarding SET option. | 
| Previous Message | flashbangpop | 2010-02-22 18:36:18 | Re: Complex SELECT Statement help needed |