Skip site navigation (1) Skip section navigation (2)

Re: Reducing stats collection overhead

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Reducing stats collection overhead
Date: 2007-04-29 11:36:15
Message-ID: 87bqh7za34.fsf@oxford.xeocode.com (view raw or flat)
Thread:
Lists: pgsql-hackers
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> So I think that complicating the design with, say, a timeout counter to
> force out the stats after a sleep interval is not necessary. Doing so would
> add a couple of kernel calls to every client interaction so I'd really
> rather avoid that.
>
> Any thoughts, better ideas?

If we want to have an idle_in_statement_timeout then we'll need to introduce a
select loop instead of just directly blocking on recv anyways. Does that mean
we may as well bite the bullet now?

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com


In response to

Responses

pgsql-hackers by date

Next:From: Dawid KuroczkoDate: 2007-04-29 11:43:58
Subject: Re: Feature freeze progress report
Previous:From: Stefan KaltenbrunnerDate: 2007-04-29 11:36:00
Subject: Re: Feature freeze progress report

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group