From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: John Naylor <john.naylor@enterprisedb.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Add index OID macro argument to DECLARE_INDEX
Date: Tue, 29 Jun 2021 08:17:11 +0200
Message-ID: <ea33c0db-a1dc-2c1b-d52a-1ad852a5b095@enterprisedb.com> (raw)
In-Reply-To: <CAFBsxsEV94d82G1+mxAW6_T=MFupgtuXQc3nfO_JTinEU=TmoQ@mail.gmail.com>
References: <ccef1e46-a404-25b1-9b4c-85f2c08e1f28@enterprisedb.com>
<CAFBsxsEV94d82G1+mxAW6_T=MFupgtuXQc3nfO_JTinEU=TmoQ@mail.gmail.com>
On 21.06.21 13:53, John Naylor wrote:
> > This patch changes places like this
> >
> > DECLARE_UNIQUE_INDEX_PKEY(pg_aggregate_fnoid_index, 2650, on
> > pg_aggregate using btree(aggfnoid oid_ops));
> > #define AggregateFnoidIndexId 2650
> >
> > to this
> >
> > DECLARE_UNIQUE_INDEX_PKEY(pg_aggregate_fnoid_index, 2650,
> > AggregateFnoidIndexId, on pg_aggregate using btree(aggfnoid oid_ops));
>
> +1, and the patch looks good to me.
committed, thanks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@enterprisedb.com, john.naylor@enterprisedb.com
Subject: Re: Add index OID macro argument to DECLARE_INDEX
In-Reply-To: <ea33c0db-a1dc-2c1b-d52a-1ad852a5b095@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox