Date: Thu, 13 May 2021 10:43:03 +0800
From: Julien Rouhaud <rjuju123@gmail.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: magnus@hagander.net, masao.fujii@oss.nttdata.com, michael@paquier.xyz,
	andres@anarazel.de, tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org,
	sfrost@snowman.net, bruce@momjian.us, myon@debian.org,
	peter.eisentraut@enterprisedb.com,
	pgsql-hackers@lists.postgresql.org
Subject: Re: compute_query_id and pg_stat_statements
Message-ID: <20210513024303.e5ddm54f6hc6pdff@nol>
References: <20210513.095943.2029736808766317326.horikyota.ntt@gmail.com>
 <20210513.105152.1649475530581175603.horikyota.ntt@gmail.com>
 <20210513020245.wjswdvzmasfxrbqs@nol>
 <20210513.112629.407758843298621458.horikyota.ntt@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210513.112629.407758843298621458.horikyota.ntt@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/20210513024303.e5ddm54f6hc6pdff%40nol>
Precedence: bulk

On Thu, May 13, 2021 at 11:26:29AM +0900, Kyotaro Horiguchi wrote:
> 
> I believe any "real"
> alternative query-id provider is supposed to be hooked "before"
> pg_stat_statements. (It is a kind of magic to control the order of
> plugins, though..

Indeed, you have to configure shared_preload_libraries depending on whether
each module calls the previous post_parse_analyze_hook before or after its own
processing, and that's the main reason why I think a dedicated entry point
would be better.