Re: proposal - function string_to_table
Peter Smith <smithpb2250@gmail.com>
From: Peter Smith <smithpb2250@gmail.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: "movead.li@highgo.ca" <movead.li@highgo.ca>,
Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-08-24T23:19:02Z
Lists: pgsql-hackers
Hi. I have re-checked the string_to_table_20200824.patch. ==== On Tue, Aug 25, 2020 at 2:34 AM Pavel Stehule <pavel.stehule@gmail.com> wrote: >> COMMENT (help text) >> >> + Splits the <parameter>string</parameter> at occurrences >> + of <parameter>delimiter</parameter> and forms the remaining data >> + into a table with one <type>text</type> type column. >> + If <parameter>delimiter</parameter> is <literal>NULL</literal>, >> + each character in the <parameter>string</parameter> will become a >> + separate element in the array. >> >> Seems like here is a cut/paste error from the string_to_array help text. >> >> "separate element in the array" should say "separate row of the table" > > > fixed > No. You wrote "separate row of table". Should say "separate row of the table". ==== QUESTION (pg_proc.dat) I noticed the oids of the functions are modified in this latest patch. They seem 1000's away from the next nearest oid. I was curious about the reason for those particular numbers (8432, 8433)? ==== Kind Regards, Peter Smith. Fujitsu Australia
Commits
-
Add string_to_table() function.
- 66f163068030 14.0 landed