NotificationsYou must be signed in to change notification settings
Fork49
Star705

PGPRO-6864: do not use the function pg_atoi if possible#40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

MarinaPolyakova merged 1 commit intomasterfromPGPRO-6864

Jul 12, 2022

Merged

PGPRO-6864: do not use the function pg_atoi if possible#40

MarinaPolyakova merged 1 commit intomasterfromPGPRO-6864

Jul 12, 2022

Conversation

Copy link

Contributor

MarinaPolyakova commentedJul 1, 2022

In PostgreSQL version 12 or higher it's more effecient to use the function
pg_strtoint32 instead (see the commit 86eaf208ea048936df6be77276a246d3f92e9620).
And in PostgreSQL 15 the function pg_atoi was removed altogether (see the commit
73508475d69e90f98ebd9b7e1a5933a26a49c5e9). Therefore if possible use the
function pg_strtoint32 instead.

PGPRO-6864: do not use the function pg_atoi if possible

e45ff38

In PostgreSQL version 12 or higher it's more effecient to use the functionpg_strtoint32 instead (see the commit 86eaf208ea048936df6be77276a246d3f92e9620).And in PostgreSQL 15 the function pg_atoi was removed altogether (see the commit73508475d69e90f98ebd9b7e1a5933a26a49c5e9). Therefore if possible use thefunction pg_strtoint32 instead.