| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(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-01-29 15:45:01 |
| Message-ID: | 810B544F-500F-41E3-BC19-67FAFA410526@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
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.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | reid.thompson | 2024-01-29 15:54:52 | Re: Refactoring backend fork+exec code |
| Previous Message | Ronan Dunklau | 2024-01-29 15:42:27 | Re: scalability bottlenecks with (many) partitions (and more) |