| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Debian 12 gcc warning |
| Date: | 2023-08-29 01:00:37 |
| Message-ID: | ZO1DNWNSu/bSUCHv@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 28, 2023 at 07:10:38PM -0400, Bruce Momjian wrote:
> On Tue, Aug 29, 2023 at 07:30:15AM +0900, Michael Paquier wrote:
> > On Mon, Aug 28, 2023 at 03:37:20PM -0400, Bruce Momjian wrote:
> > > I don't see a clean way of avoiding the warning except by initializing
> > > the array, which seems wasteful.
> >
> > Or just initialize the array with a {0}?
>
> Uh, doesn't that set all elements to zero? See:
>
> https://stackoverflow.com/questions/2589749/how-to-initialize-array-to-0-in-c
FYI, that does stop the warning.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2023-08-29 01:04:24 | Re: Wrong usage of pqMsg_Close message code? |
| Previous Message | Jimmy Yih | 2023-08-29 00:58:56 | Re: Should the archiver process always make sure that the timeline history files exist in the archive? |