Re: Memory error in src/backend/replication/logical/origin.c - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: Memory error in src/backend/replication/logical/origin.c
Date
Msg-id 91DFFD71-4D34-488B-B49A-B9F863CB976A@gmail.com
Whole thread Raw
In response to Re: Memory error in src/backend/replication/logical/origin.c  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On Nov 26, 2017, at 10:28 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> Mark Dilger <hornschnorter@gmail.com> writes:
>>        bool        nulls[Natts_pg_replication_origin];
>>            memset(&nulls, 0, sizeof(nulls));
> 
>> around lines 277 through 303.  Patch below.
> 
> AFAIK this is not a bug, though I agree that dropping the "&" is probably
> better style.  The reason is that applying "&" to an undecorated array
> name is basically a no-op, because without "&" the array name would decay
> to a pointer anyway.  With "&", the address-taking is explicit, but you
> still get a pointer to the array, not a pointer to some pointer to the
> array.  Ain't C fun?

Thanks for the refresher on C madness.

mark


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] More stats about skipped vacuums
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Bug in ExecModifyTable function and trigger issues for foreign tables