pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: pgstat: store statistics in shared memory.
Date: Thu, 7 Apr 2022 00:31:49 -0700
Message-ID: <20220407073149.qsxf74oept7o435x@alap3.anarazel.de> (raw)
In-Reply-To: <20220407063527.jdf642iuhv7vemz2@alap3.anarazel.de>
References: <E1ncJtG-000gDK-1G@gemulon.postgresql.org>
	<Yk6AFxydXbIbYIJ5@paquier.xyz>
	<20220407063527.jdf642iuhv7vemz2@alap3.anarazel.de>

Hi,

On 2022-04-06 23:35:27 -0700, Andres Freund wrote:
> On 2022-04-07 15:09:27 +0900, Michael Paquier wrote:
> > On Thu, Apr 07, 2022 at 04:37:02AM +0000, Andres Freund wrote:
> > > pgstat: store statistics in shared memory.
> > > 
> > > Previously the statistics collector received statistics updates via UDP and
> > > shared statistics data by writing them out to temporary files regularly. These
> > > files can reach tens of megabytes and are written out up to twice a
> > > second. This has repeatedly prevented us from adding additional useful
> > > statistics.
> > 
> > rorqual, that uses --disable-spinlocks and --disable-atomics, is
> > unhappy after this commit:
> > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rorqual&dt=2022-04-07%2005%3A47%3A03
> > 
> > test_decoding is the one complaining here, and I can reproduce the
> > issue locally once I build the code with those switches.
> 
> Yea, saw that too. About to push the fix...

And rorqual seems happy again.

Greetings,

Andres Freund





view thread (5+ messages)  latest in thread

Message-ID: <20220407073149.qsxf74oept7o435x@alap3.anarazel.de>
Permalink:  ../20220407073149.qsxf74oept7o435x@alap3.anarazel.de/
Also on:    postgresql.org/message-id/20220407073149.qsxf74oept7o435x@alap3.anarazel.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-committers@postgresql.org
  Cc: andres@anarazel.de, michael@paquier.xyz
  Subject: Re: pgsql: pgstat: store statistics in shared memory.
  In-Reply-To: <20220407073149.qsxf74oept7o435x@alap3.anarazel.de>
  References: <E1ncJtG-000gDK-1G@gemulon.postgresql.org> <Yk6AFxydXbIbYIJ5@paquier.xyz> <20220407063527.jdf642iuhv7vemz2@alap3.anarazel.de> <20220407073149.qsxf74oept7o435x@alap3.anarazel.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox