Re: Add null termination to string received in parallel apply worker

From: Peter Smith <smithpb2250(at)gmail(dot)com>
To: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: Add null termination to string received in parallel apply worker
Date: 2023-10-11 09:11:15
Message-ID: CAHut+PtTSue+gkurguEyXC=XSf64AW3=Xtf+YBciKUzpeBcN+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Hou-san.

+ /*
+ * Note that the data received via the shared memory queue is not
+ * null-terminated. So we use the StringInfo API to store the
+ * string so as to maintain the convention that StringInfos has a
+ * trailing null.
+ */

"... that StringInfos has a trailing null."

Probably should be either "StringInfo has" or "StringInfos have"

======
Kind Regards.
Peter Smith.
Fujitsu Australia

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2023-10-11 09:19:37 Re: Problem, partition pruning for prepared statement with IS NULL clause.
Previous Message Sergei Glukhov 2023-10-11 09:09:36 Re: Problem, partition pruning for prepared statement with IS NULL clause.