On Fri, Jun 5, 2015 at 2:54 PM, Sheena, Prabhjot <
prabhjot.si...@classmates.com> wrote:
> explain analyze SELECT max(last_update_date) AS last_update_date FROM
> btdt_responses WHERE registration_id = 8718704208 AND response != 4;
>
>
> QUERY PLAN
>
>
> ---
On 06/05/2015 12:28 PM, Steve Crawford wrote:
On 06/05/2015 11:38 AM, Sheena, Prabhjot wrote:
When I run vacuum analyze it fixes the problem but after 1 or 2 days
the problem comes back
Is autovacuum running and using what settings?
(select name, setting from pg_settings where name ~ 'aut
On 06/05/2015 11:38 AM, Sheena, Prabhjot wrote:
When I run vacuum analyze it fixes the problem but after 1 or 2 days
the problem comes back
Is autovacuum running and using what settings?
(select name, setting from pg_settings where name ~ 'autovacuum' Konsole
output or name ~ 'statistics'
From: Sheena, Prabhjot [mailto:prabhjot.si...@classmates.com]
Sent: Friday, June 05, 2015 2:38 PM
To: Igor Neyman; pgsql-gene...@postgresql.org; pgsql-performance@postgresql.org
Subject: RE: Query running slow for only one specific id. (Postgres 9.3) version
When I run vacuum analyze it fixes th
When I run vacuum analyze it fixes the problem but after 1 or 2 days the
problem comes back
Here is the table structure
Column |Type |
Modifiers | Storage | Stats target | Description
-
On 06/05/2015 10:54 AM, Sheena, Prabhjot wrote:
Postgresql 9.3 Version
Guys
Here is the issue that I’m facing for couple of weeks now.
I have table (size 7GB)
*If I run this query with this specific registration id it is using
the wrong execution plan and takes more than a minu
From: pgsql-performance-ow...@postgresql.org
[mailto:pgsql-performance-ow...@postgresql.org] On Behalf Of Sheena, Prabhjot
Sent: Friday, June 05, 2015 1:55 PM
To: pgsql-gene...@postgresql.org; pgsql-performance@postgresql.org
Subject: [PERFORM] Query running slow for only one specific id. (Postg
Postgresql 9.3 Version
Guys
Here is the issue that I'm facing for couple of weeks now. I have
table (size 7GB)
If I run this query with this specific registration id it is using the wrong
execution plan and takes more than a minute to complete. Total number of rows
for this registr
