From: | Ruben Blanco <rubenblan(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Heavy queries not run by user application |
Date: | 2011-02-14 10:15:40 |
Message-ID: | AANLkTi=t5tyi5F5JRw4Q5Vm=suy1hi1_1MFitd4AUY+G@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks a lot, guys. There were two users running Navicat, and these killer
queries are indeed run by this program.
Rubén.
2011/2/13 John R Pierce <pierce(at)hogranch(dot)com>
> On 02/12/11 5:11 PM, Ruben Blanco wrote:
>
>> Hi:
>>
>> I'm running a Postgres database with a total disk occupation of 100Gb,
>> largest and most used table up to 40Gb (about 30.000.000 tuples).
>>
>> Overall performance degrades sometimes due to some queries that are not
>> run by the final user app. I guess they are run by Postgres itself. They use
>> to take up to 100% of CPU and delay user queries substantially.
>>
>> From 'pg_stat_activity', you can see this pattern in "current_query"
>> column for these queries:
>>
>> SELECT * FROM "public"."tablename" ORDER BY "column1", "column2"...
>> LIMIT 1000 OFFSET 144000
>>
>> Sometimes with 'SET DATESTYLE = "ISO"'; before the SELECT.
>>
>>
>
>
> there's nothing like that run by postgres itself automagically, it must be
> some software at your end you're not aware of.
>
> in pg_stat_activity, check usename, client_addr and client_port, and match
> this up against netstat or whatever activity to determine what application
> is making these queries.
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alessandro Candini | 2011-02-14 13:41:48 | Embedded C function returning a set of rows |
Previous Message | Basil Bourque | 2011-02-14 09:48:03 | Re: Upgrading to 9.0 on Mac OS X |