| From: | "Winter Loo" <winterloo(at)126(dot)com> |
|---|---|
| To: | "Daniel Gustafsson" <daniel(at)yesql(dot)se> |
| Cc: | "Laurenz Albe" <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re:Re: may be a buffer overflow problem |
| Date: | 2024-06-14 10:48:29 |
| Message-ID: | 5d3e503.a1f5.190165cf47e.Coremail.winterloo@126.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>Thanks for looking! I will apply it backpatched all the way down as this has
>been wrong since 2006.
>
>> I wonder how Winter Loo got to see that warning...
>
I was compiling source code of postgres version 13 and the building flags is changed in my development environment.
>And it would be interesting to know if that was the only warning, since error.c >in ECPG performs the exact same string copy.
>
Yes, that was the only warning. I searched all `sqlstate` words in ecpg directory, there's no other dubious problems.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2024-06-14 10:54:45 | Re: Conflict Detection and Resolution |
| Previous Message | Shubham Khanna | 2024-06-14 10:38:49 | Re: Pgoutput not capturing the generated columns |