Dear Tom,
thanks for your information.
Where can I learn more about the explain and analyze??
One view that is giving a lot of problems is vkardex_3
which is used most of the time...
The explain analyze I sent is one of the views that
conform this one.
Thanks in advance.
Carlos Lopez Linares
---
Carlos Lopez <[EMAIL PROTECTED]> writes:
> This is one of the queries that work,and is the first
> in a 4 level nested query
Do you really need UNION (as opposed to UNION ALL) in this query?
The EXPLAIN shows that almost half the runtime is going into the
sort/uniq to eliminate duplicates ...
This is one of the queries that work,and is the first
in a 4 level nested query
where do I find how to interpret explains???
thanks in advance,
Carlos.
mate=# explain analyze select * from vdocinvdpre;
On Sat, 06 Nov 2004 11:52:15 -0800, Carlos Lopez wrote:
> I have migrated a database from MS SQL to a
> postgresSQL database, but when running it, the results
> are very slow (and unusable) which is the only reason
> we don't entirely move to postgresSQL.
Have you run ANALYZE lately? (See manual.
On Sat, 2004-11-06 at 12:52, Carlos Lopez wrote:
> I have migrated a database from MS SQL to a
> postgresSQL database, but when running it, the results
> are very slow (and unusable) which is the only reason
> we don't entirely move to postgresSQL.
> The problem is that there are many nested views
On Sat, 2004-11-06 at 19:52, Carlos Lopez wrote:
> The problem is that there are many nested views which
> normally join tables by using two fields, one
> character and other integer.
PostgreSQL has difficulty with some multi-column situations, even though
in general it has a particularly good que
On Sat, 06 Nov 2004 11:52:15 -0800, Carlos Lopez wrote:
> I have migrated a database from MS SQL to a postgresSQL database, but
> when running it, the results are very slow (and unusable) which is the
> only reason we don't entirely move to postgresSQL.
I have migrated a database from MS SQL to a
postgresSQL database, but when running it, the results
are very slow (and unusable) which is the only reason
we don't entirely move to postgresSQL.
The problem is that there are many nested views which
normally join tables by using two fields, one
charact
