Plain strdup() in frontend code

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Plain strdup() in frontend code
Date: 2019-04-29 11:47:27
Message-ID: Y0y9xenfoBPc-Tufsr2Zg-MmkrJslm0Tw_CMg4p_j58-k_PXNC0klMdkKQkg61BkXC9_uWo-DcUzfxnHqpkpoR5jjVZrPHqKYikcHIiONhg=@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Reading code I noticed that we in a few rare instances use strdup() in frontend
utilities instead of pg_strdup(). Is there a reason for not using pg_strdup()
consistently as per the attached patch?

cheers ./daniel

Attachment Content-Type Size
frontend_strdup.patch application/octet-stream 3.3 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-04-29 13:01:26 Re: Plain strdup() in frontend code
Previous Message Justin Pryzby 2019-04-29 10:28:51 Re: Cleanup/remove/update references to OID column