Re: Add Postgres module info - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: Add Postgres module info
Date
Msg-id 35f29bde-ccc7-41b3-8c13-6ff30c196a93@gmail.com
Whole thread Raw
In response to Re: Add Postgres module info  (Yurii Rashkovskii <yrashk@omnigres.com>)
Responses Re: Add Postgres module info
List pgsql-hackers
On 12/24/24 10:42, Yurii Rashkovskii wrote:
> On Mon, Dec 16, 2024 at 12:02 PM Andrei Lepikhov <lepihov@gmail.com 
> I've reviewed the patch, and it is great that you support more flexible 
> versioning now. I am just wondering a bit about the case where `minfo- 
>  >name` can be `NULL` but `minfo->version` isn't, or where both are 
> `NULL` – should we skip any of these?
Depends. I wrote code that way so as not to restrict a maintainer by 
initialising all the fields; remember, it may grow in the future.
But I am open to changing that logic. Do you have any specific rule on 
which fields may be empty and that must be initialised? Do you think all 
fields maintainer must fill with non-zero-length constants?

Also, I've added this patch to commitfest:
https://commitfest.postgresql.org/51/5465/

-- 
regards, Andrei Lepikhov



pgsql-hackers by date:

Previous
From: Andrei Lepikhov
Date:
Subject: Re: Add Postgres module info
Next
From: Bruce Momjian
Date:
Subject: Re: Support for unsigned integer types