Horton

Re: Allow escape in application_name

Kyotaro Horiguchi <horikyota.ntt@gmail.com>

View thread View on postgr.es
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: sawada.mshk@gmail.com
Cc: masao.fujii@oss.nttdata.com, kuroda.hayato@fujitsu.com, houzj.fnst@fujitsu.com, ikedamsh@oss.nttdata.com, pgsql-hackers@lists.postgresql.org, tgl@sss.pgh.pa.us
Date: 2022-01-04T05:03:57Z
Lists: pgsql-hackers 
At Tue, 4 Jan 2022 12:36:32 +0900, Masahiko Sawada <sawada.mshk@gmail.com> wrote in 
> On Tue, Jan 4, 2022 at 12:05 PM Kyotaro Horiguchi
> <horikyota.ntt@gmail.com> wrote:
> > pg_terminate_backend returns just after kill() returns. So I'm afraid
> > that there's a case where the next access to ft6 happens before the
> > old connection actually ends on slow machines or under heavy load.
> 
> The test does pg_terminate_backend() with a timeout, and in this case,
> don't we wait for the backend to end after sending the signal?

Oops! I missed that part. I agree that it works. Thanks!

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

Commits

  1. postgres_fdw: Add regression test for postgres_fdw.application_name GUC.

  2. postgres_fdw: Allow postgres_fdw.application_name to include escape sequences.

  3. doc: Add note about postgres_fdw.application_name.

  4. postgres_fdw: Revert unstable tests for postgres_fdw.application_name.

  5. postgres_fdw: Allow application_name of remote connection to be set via GUC.