Re: contrib/pg_stat_statements 1226 - Mailing list pgsql-hackers

From Alex Hunsaker
Subject Re: contrib/pg_stat_statements 1226
Date
Msg-id 34d269d40812300859x49c1e40fmfb834d67f06cfd66@mail.gmail.com
Whole thread Raw
In response to Re: contrib/pg_stat_statements 1226  ("Alex Hunsaker" <badalex@gmail.com>)
Responses Re: contrib/pg_stat_statements 1226  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Dec 29, 2008 at 15:46, Alex Hunsaker <badalex@gmail.com> wrote:
> On Thu, Dec 25, 2008 at 23:04, ITAGAKI Takahiro
> <itagaki.takahiro@oss.ntt.co.jp> wrote:
>> Here is an updated version of contrib/pg_stat_statements patch.
>
> Im going to do some more testing, give the typedef Chunk stuff another
> look (you did fix the race/not protected by a spinlock  you found
> earlier right?) .  And if all looks good mark it as ready for
> commiter.  (Assuming I find time tonight :))

Ok i ran a portion of tpc-h with 4 simultaneous clients doing the same
query on a 32bit dual core machine about a hundred times (lets call
this A).  I then compared the # of calls, # of gets and # rows from
pg_stat_statements view to a single run (lets cal this B) to make sure
they matched (i.e. made sure A.gets = A.calls * B.gets), that part all
looks good.  So I think if there was a race you squashed it.  My only
nit this time around was patch complaining about (Stripping trailing
CRs from patch.) but that's no big deal.  So Im going to mark it as
ready for commmiter.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: about truncate
Next
From: Tom Lane
Date:
Subject: Re: TODO items for window functions