From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
Cc: | Chapman Flack <chap(at)anastigmatix(dot)net>, Erik Wienhold <ewie(at)ewie(dot)name>, Vik Fearing <vik(at)postgresfriends(dot)org>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: to_regtype() Raises Error |
Date: | 2024-02-02 20:23:48 |
Message-ID: | CAKFQuwZSMPMLbe06B8ak_8Db5jUbAKnmSse=5TdacvcbyZjapA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 29, 2024 at 8:45 AM David E. Wheeler <david(at)justatheory(dot)com>
wrote:
> Hey there, coming back to this. I poked at the logs in the master branch
> and saw no mention of to_regtype; did I miss it?
>
With no feedback regarding my final suggestion I lost interest in it and
never produced a patch.
> On Sep 17, 2023, at 10:58 PM, David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> > Parses a string of text, extracts a potential type name from it, and
> translates that name into an OID. Failure to extract a valid potential
> type name results in an error while a failure to determine that the
> extracted name is known to the system results in a null output.
> >
> > I take specific exception to describing your example as a “textual type
> name”.
>
> More docs seem like a reasonable compromise. Perhaps it’d be useful to
> also describe when an error is likely and when it’s not.
>
>
Seems like most just want to leave well enough alone and deal with the rare
question for oddball input on the mailing list. If you are interested
enough to come back after 4 months I'd suggest you write up and submit a
patch. I'm happy to review it and see if that is enough to get a committer
to respond.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2024-02-02 20:33:51 | Re: to_regtype() Raises Error |
Previous Message | Tom Lane | 2024-02-02 20:20:13 | Re: Correct SQLSTATE for ENOMEM in file access |