| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, David Steele <david(at)pgmasters(dot)net>, Cary Huang <cary(dot)huang(at)highgo(dot)ca>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_rewind copies |
| Date: | 2022-04-05 08:11:17 |
| Message-ID: | B7F370F6-9CF8-4759-9E69-52EC8A366C21@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 4 Apr 2022, at 15:08, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> We use snprintf() like that countless times, and approximately none of them check for overflow. So while you are right, this might not be the place to start a new policy.
Fair enough, I'll remove these hunks before committing and will look a bigger
picture patch to address these across the codebase later.
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-04-05 08:18:57 | Re: standby recovery fails (tablespace related) (tentative patch and discussion) |
| Previous Message | Nikita Malakhov | 2022-04-05 07:58:59 | Re: Pluggable toaster |