From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #13852: SQL Select Slow Issues |
Date: | 2016-01-13 01:31:28 |
Message-ID: | 5695A8F0.1060603@catalyst.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 07/01/16 09:42, eugeneymail(at)ymail(dot)com wrote:
>
> The general and major complains I can summarize is the "SELECT" statement
> returns results too slow, as compared to the commercialized products such as
> Oracle and MS SQL Server.
>
A self contained example would be good, otherwise noone can really help
you much :-(
e.g common reasons why Postgres might look slower than (say) MSSQL:
- Postgres config default/untuned/mistuned
- Postgres table stats non-existent
- Postgres running on a slower/smaller machine than MSSQL
- Postgres machine on a slower network (or further away)
....
clearly one could go on, note all of these above mean that assuming
'Postgres is just slow' is misunderstanding the issue.
regards
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-01-13 01:36:58 | Re: BUG #13861: Database dump does not load when both plpython2u and plpython3u functions are used |
Previous Message | roman.vanicek | 2016-01-12 19:42:25 | BUG #13861: Database dump does not load when both plpython2u and plpython3u functions are used |