On Jul 16, 2019, at 3:30 AM, Fabien COELHO <coelho@cri.ensmp.fr> wrote:
>> Cool. I'm not exactly sure when we should include 'pg_' in identifier
>> names. It seems to be used for functions/macros that wrap or replace
>> something else with a similar name, like pg_pwrite(),
>> pg_attribute_noreturn(), ... In this case it's just our own code that
>> we're moving, so I'm wondering if we should just call it scanint8().
>
> I added the pg_ prefix as a poor man's namespace because the function can be used by external tools (eg contribs), so
asto avoid potential name conflicts.
Yeah, I think if we are going to expose it to front end code there is a good argument for some kind of prefix that
makesit sound PostgreSQL-related.
...Robert
