From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: System Query hit to Database |
Date: | 2016-02-11 14:55:01 |
Message-ID: | CADK3HH+ywAJVPHE8C7bp6JayBG9ZWBNWzNYq4A47NEgB1v=nCA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Depends on the size of the catalogs. There are some db's with 1000's of
tables and columns, which can end up being a very slow query
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
On 11 February 2016 at 02:26, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 2/10/2016 9:02 PM, dhaval jaiswal wrote:
>
>> I am getting lot of following queries on my Database. I need your help
>> to stop hitting this kind of queries to database.
>>
>
> I ran that query on a pg server I manage and it took 2.3 milliseconds. on
> another instance on the same server, it took 2.00 ms. you'd have to do
> that 400-500 times a second continuously to use up one cpu core. ooh,
> on a couple older servers it took 4.4ms and 5.0ms, so 200/s.
>
> I'm just saying... If 'lot of queries' means a dozen per second
> continuously, thats not much performance wise.
>
>
>
>
> --
> john r pierce, recycling bits in santa cruz
>
>
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>
From | Date | Subject | |
---|---|---|---|
Next Message | dhaval jaiswal | 2016-02-13 10:53:13 | Re: System Query hit to Database |
Previous Message | John R Pierce | 2016-02-11 07:26:48 | Re: System Query hit to Database |