From: | Bricklen Anderson <BAnderson(at)PresiNET(dot)com> |
---|---|
To: | |
Cc: | Joel Fradkin <jfradkin(at)wazagua(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: MSSQL versus Postgres timing |
Date: | 2005-02-01 17:25:41 |
Message-ID: | 41FFBB95.3090306@PresiNET.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Michael Fuhr wrote:
> On Tue, Feb 01, 2005 at 11:54:11AM -0500, Joel Fradkin wrote:
>
>>A table with 645,000 records for associates has view (basically select *
>>from tblassociates where clientnum = 'test')
>>
>>This is taking 13 seconds in postgres and 3 seconds in MSSQL.
>
>
> Please post the EXPLAIN ANALYZE output for the slow query, once
> with enable_seqscan on and once with it off. For example:
>
> SET enable_seqscan TO on; -- if not already on
> EXPLAIN ANALYZE SELECT * FROM tblassociates WHERE clientnum = 'test';
>
> SET enable_seqscan TO off;
> EXPLAIN ANALYZE SELECT * FROM tblassociates WHERE clientnum = 'test';
>
>
>>Be glad to provide the view and tables etc.
>
>
> Please do -- it might help us spot something that could be improved.
> What version of PostgreSQL are you using?
>
Also, is clientnum a string datatype, or are you doing implicit type conversion?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-02-01 18:36:14 | Re: case sensitive/insensitive confusion |
Previous Message | Michael Fuhr | 2005-02-01 17:06:54 | Re: MSSQL versus Postgres timing |