Horton

Thread

Commits

  1. Fix format if entry in wait_event_names.txt

  1. Fix an entry in wait_event_names.txt

    Bertrand Drouvot <bertranddrouvot.pg@gmail.com> — 2023-08-17T05:49:29Z

    Hi hackers,

While working on [1] it has been noticed by Masahiro-san that the description field
in the new pg_wait_event view contains 2 blanks for one row.

It turns out that it comes from wait_event_names.txt (added in fa88928).

Attached a tiny patch to fix this entry in wait_event_names.txt (I did check that no
other entries are in the same case).

[1]: https://www.postgresql.org/message-id/735fbd560ae914c96faaa23cc8d9a118%40oss.nttdata.com

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

  2. Re: Fix an entry in wait_event_names.txt

    Masahiro Ikeda <ikedamsh@oss.nttdata.com> — 2023-08-17T06:25:27Z

    On 2023-08-17 14:49, Drouvot, Bertrand wrote:
> Hi hackers,
> 
> While working on [1] it has been noticed by Masahiro-san that the
> description field
> in the new pg_wait_event view contains 2 blanks for one row.
> 
> It turns out that it comes from wait_event_names.txt (added in 
> fa88928).
> 
> Attached a tiny patch to fix this entry in wait_event_names.txt (I did
> check that no
> other entries are in the same case).
> 
> [1]:
> https://www.postgresql.org/message-id/735fbd560ae914c96faaa23cc8d9a118%40oss.nttdata.com
> 
> Regards,

+1. Thanks!

Regards,
-- 
Masahiro Ikeda
NTT DATA CORPORATION

  3. Re: Fix an entry in wait_event_names.txt

    Michael Paquier <michael@paquier.xyz> — 2023-08-17T23:19:14Z

    On Thu, Aug 17, 2023 at 03:25:27PM +0900, Masahiro Ikeda wrote:
> +1. Thanks!

Applied.
--
Michael