Horton
Menu

Re: pg_stat_statements: calls under-estimation propagation

Magnus Hagander <magnus@hagander.net>

View thread
From: Magnus Hagander <magnus@hagander.net>
To: Peter Geoghegan <pg@heroku.com>
Cc: Peter Eisentraut <peter_e@gmx.net>, Fujii Masao <masao.fujii@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Sameer Thakur <samthakur74@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2013-12-08T11:01:33Z
Lists: pgsql-hackers 
On Sun, Dec 8, 2013 at 1:00 AM, Peter Geoghegan <pg@heroku.com> wrote:

> On Sat, Dec 7, 2013 at 3:50 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> > 32-bit buildfarm members are having problems with this patch.
>
> This should fix that problem. Thanks.
>

Applied.

I also noted on
http://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=frogmouth&dt=2013-12-08%2007%3A30%3A01&stg=make-contrib
that
there are compiler warnings being generated in pgss. But from a quick look
that looks like something pre-existing and not caused by the latest patch.

-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Improve management of "sticky" entries in contrib/pg_stat_statements.