, can I do
something else to fix this?
Thank you.
-- Original Message --
From: "Pavel Stehule"
To: "Sterpu Victor"
Cc: "Fırat Güleç" ; "Pgsql Performance"
Sent: 2019-11-22 2:59:11 PM
Subject: Re: Re[2]: Postgresql planning time too high
stic(test 3
can be only deterministic as as setted this way the postgres server).
Anyway, in the end the deterministic planner is much more effective at
planning this query that the generic one(test 3 is with generic planner
turned off).
------ Original Message --
From: "Pa
focg).
-- Original Message --
From: "Sterpu Victor"
To: "Fırat Güleç"
Cc: pgsql-performance@lists.postgresql.org
Sent: 2019-11-22 1:44:51 PM
Subject: Re[2]: Postgresql planning time too high
No rows should be returned, DB is empty.
I'm testing now on a empty DB try
I'm sorry, I messed up between a lot of queries . there is no
difference after running "VACUUM ANALYZE".
I guess this was to be expected as the database was just restored from
backup.
-- Original Message --
From: "Fırat Güleç"
To: "Sterpu
nd the
problem was not solved there by this command on the 9.5.
I guess I should update the production server.
Is there another way?
Thank you
-- Original Message --
From: "Fırat Güleç"
To: "Sterpu Victor"
Cc: pgsql-performance@lists.postgresql.org
Sent: 2019
I did runned "VACCUM FULL" followed by "VACUUM" but no difference.
-- Original Message --
From: "Fırat Güleç"
To: "Sterpu Victor"
Cc: pgsql-performance@lists.postgresql.org
Sent: 2019-11-22 1:35:15 PM
Subject: RE: Postgresql planning time too h
fine like this.
-- Original Message --
From: "Fırat Güleç"
To: "Sterpu Victor"
Cc: pgsql-performance@lists.postgresql.org
Sent: 2019-11-22 1:35:15 PM
Subject: RE: Postgresql planning time too high
Hello Sterpu,
First, please run vaccum for your Postgresql DB.
No rows returne
Hello
I'm on a PostgreSQL 12.1 and I just restored a database from a backup.
When I run a query I get a big execution time: 5.482 ms
After running EXPLAIN ANALYZE I can see that the "Planning Time:
5165.742 ms" and the "Execution Time: 6.244 ms".
The database is new(no need to vacuum) and i'm th
