Re: UPDATEDs slowing SELECTs in a fully cached database

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Ivan Voras" <ivoras(at)freebsd(dot)org>,"lars" <lhofhansl(at)yahoo(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: UPDATEDs slowing SELECTs in a fully cached database
Date: 2011-07-12 19:26:29
Message-ID: 4E1C5995020000250003F258@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

lars <lhofhansl(at)yahoo(dot)com> wrote:

> select count(*) from test where tenant = $1 and created_date = $2

Thinking about this some more, it would be interesting to know your
PostgreSQL configuration. I seem to remember you mentioning some
settings up-thread, but I'm not sure whether it was comprehensive.
Could you paste the result of running the query on this Wiki page?:

http://wiki.postgresql.org/wiki/Server_Configuration

It might be that if you generate your queries with literals rather
than using server-side prepared statements, and tweak a couple
configuration settings, this problem will evaporate.

-Kevin

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Clem Dickey 2011-07-12 19:55:14 Re: Planner choosing NestedLoop, although it is slower...
Previous Message Kevin Grittner 2011-07-12 19:08:35 Re: UPDATEDs slowing SELECTs in a fully cached database