Re: [HACKERS] PG10 Partitioned tables and relation_is_updatable() - Mailing list pgsql-hackers

From Dean Rasheed
Subject Re: [HACKERS] PG10 Partitioned tables and relation_is_updatable()
Date
Msg-id CAEZATCU_6_iRpTB9RQPdo=tbFTt_4tSvvx2eE5pVv4pYTT2dYQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] PG10 Partitioned tables and relation_is_updatable()  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
List pgsql-hackers
On 13 June 2017 at 05:50, Ashutosh Bapat
<ashutosh.bapat@enterprisedb.com> wrote:
> On Tue, Jun 13, 2017 at 12:03 AM, Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
>> My initial thought, looking at the patch, is that it might be better
>> to have all the macros in one file to make them easier to maintain.
>
> Right now the macros are listed just below relkind enum in pg_class.h.
> Is that a good place or do you think, we should list them in a
> separate file?
>

Yeah, I wondered about putting them in a separate file, but I think
just below the relkind enum is probably the best place, so that people
changing that enum immediately see the first set of related things to
be updated.

>> Barring objections, I'll push my original patch and work up patches
>> for the other couple of issues I found.
>
> No objections, the patch is good to go as is. Sorry for high-jacking
> this thread.
>

No worries. I missed that other thread initially, so it was useful to
link the 2 threads together.

Regards,
Dean



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: [HACKERS] RTE_NAMEDTUPLESTORE, enrtuples and comments
Next
From: Masahiko Sawada
Date:
Subject: [HACKERS] Refreshing subscription relation state inside a transaction block