Re: PublicationActions - use bit flags.
| От | Peter Eisentraut |
|---|---|
| Тема | Re: PublicationActions - use bit flags. |
| Дата | |
| Msg-id | 6b8191a0-e0f6-b204-e6c0-f7f1a5f349c0@enterprisedb.com обсуждение исходный текст |
| Ответ на | Re: PublicationActions - use bit flags. (Greg Nancarrow <gregn4422@gmail.com>) |
| Ответы |
Re: PublicationActions - use bit flags.
|
| Список | pgsql-hackers |
On 21.01.22 01:05, Greg Nancarrow wrote:
> On Tue, Dec 21, 2021 at 12:55 PM Greg Nancarrow <gregn4422@gmail.com> wrote:
>>
>> On Tue, Dec 21, 2021 at 11:56 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>>
>>> Removing this is not good:
>>>
>>> if (relation->rd_pubactions)
>>> - {
>>> pfree(relation->rd_pubactions);
>>> - relation->rd_pubactions = NULL;
>>> - }
>>>
>>> If the subsequent palloc fails, you've created a problem where
>>> there was none before.
>>>
>>
>> Oops, yeah, I got carried away; if palloc() failed and called exit(),
>> then it would end up crashing when trying to use/pfree rd_pubactions
>> again.
>> Better leave that line in ...
>>
>
> Attaching an updated patch to fix that oversight.
> This patch thus fixes the original palloc issue in a minimal way,
> keeping the same relcache structure.
Why can't GetRelationPublicationActions() have the PublicationActions as
a return value, instead of changing it to an output argument?
В списке pgsql-hackers по дате отправления: