From: Andres Freund <andres@anarazel.de>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: tgl@sss.pgh.pa.us
Cc: alvherre@2ndquadrant.com
Cc: michael@paquier.xyz
Cc: thomas.munro@gmail.com
Cc: tomas.vondra@2ndquadrant.com
Cc: a.zakirov@postgrespro.ru
Cc: ah@cybertec.at
Cc: magnus@hagander.net
Cc: robertmhaas@gmail.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: shared-memory based stats collector
Date: Mon, 9 Mar 2020 20:34:20 -0700
Message-ID: <20200310033420.g4ev7eng4aoh3rss@alap3.anarazel.de> (raw)
In-Reply-To: <20200310.122725.1482409768204993835.horikyota.ntt@gmail.com>
References: <20200309184754.yvrgzqpzs3iynszq@alap3.anarazel.de>
<8668.1583780663@sss.pgh.pa.us>
<20200309192539.ulqo26ydld5lkpip@alap3.anarazel.de>
<20200310.122725.1482409768204993835.horikyota.ntt@gmail.com>
On 2020-03-10 12:27:25 +0900, Kyotaro Horiguchi wrote:
> That's true, but I have the same concern with Tom. The archive bacame
> too-tightly linked with other processes than actual relation.
What's the problem here? We have a number of helper processes
(checkpointer, bgwriter) that are attached to shared memory, and it's
not a problem.
> We may need the second static shared memory segment apart from the
> current one.
That seems absurd to me. Solving a non-problem by introducing complex
new infrastructure.
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andres@anarazel.de, horikyota.ntt@gmail.com, tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, michael@paquier.xyz, thomas.munro@gmail.com, tomas.vondra@2ndquadrant.com, a.zakirov@postgrespro.ru, ah@cybertec.at, magnus@hagander.net, robertmhaas@gmail.com
Subject: Re: shared-memory based stats collector
In-Reply-To: <20200310033420.g4ev7eng4aoh3rss@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