Re: Typos in the code and README

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: Typos in the code and README
Date: 2026-01-04 23:02:22
Message-ID: aVrxfhi_wzWNmsFM@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 01, 2026 at 10:00:00AM +0200, Alexander Lakhin wrote:
> READ_WRITE_PARSE_PLAN_TREES -> WRITE_READ_PARSE_PLAN_TREES
> DEFAULT_DEBUG_READ_WRITE_PARSE_PLAN_TREES -> DEFAULT_DEBUG_WRITE_READ_PARSE_PLAN_TREES

I thought that this was a bug first, but we also use this name for the
default value.

> replace_s(..., int * adjustment) -> replace_s(..., int * adjptr)

Updating this one contradicts with the upstream sources, see
b464e51ab32f that has done the opposite switch.

> There is also
> extern int        pgwin32_recv(SOCKET s, char *buf, int len, int flags);
> vs
> pgwin32_recv(SOCKET s, char *buf, int len, int f)
> but I've left at as-is; probably the change should be made in the
> implementation...

Using "flags" would be confusing I think as things stand, the code
casts a DWORD with the same name.

> Orphan entities:
> HAVE_ATOMIC_H, HAVE_MBARRIER_H -> remove (per 25f36066d)

Indeed.. It seems slightly cleaner to remove these separately. Will
do so.

> #ifdef BS_DEBUG in contrib/ltree/ltxtquery_io.c -> remove (introduced with 1dedbf2da)

I am wondering if BS stands for what it means or if it's something
else..
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2026-01-04 23:08:56 Re: Checking join outer relation uniqueness to prevent unnecessary memoization
Previous Message Michael Paquier 2026-01-04 22:23:23 Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem)