From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
---|---|
To: | Erik Rijkers <er(at)xs4all(dot)nl> |
Cc: | Alexander Korotkov <akorotkov(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pgsql: Multirange datatypes |
Date: | 2020-12-20 13:31:13 |
Message-ID: | CAPpHfdsKy6Lu6UYMocxi=kWPpcf1qwy9nOL3Mt0K1WS8_5n5aA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Sun, Dec 20, 2020 at 4:18 PM Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
> On Sun, Dec 20, 2020 at 9:06 AM Erik Rijkers <er(at)xs4all(dot)nl> wrote:
> > On 2020-12-20 05:21, Alexander Korotkov wrote:
> > > Multirange datatypes
> > >
> > > Multiranges are basically sorted arrays of non-overlapping ranges with
> > > set-theoretic operations defined over them.
> > >
> >
> > With --enable-cassert gcc 10.1.0 gives me:
> >
> > typecmds.c: In function ‘DefineRange’:
> > typecmds.c:1367:16: warning: variable ‘mltrngaddress’ set but not used
> > [-Wunused-but-set-variable]
> > 1367 | ObjectAddress mltrngaddress;
> > | ^~~~~~~~~~~~~
>
> Thank you. But are you sure that happened with --enable-cassert?
> I've reproduced this only without --enable-cassert. And that seems
> reasonable, because there is an assert, which uses this variable.
Warning arising without --enable-cassert should be fixed by
11072e8693. Let me know if the problem persists for you.
------
Regards,
Alexander Korotkov
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Rijkers | 2020-12-20 13:33:32 | Re: pgsql: Multirange datatypes |
Previous Message | Alexander Korotkov | 2020-12-20 13:29:48 | pgsql: Fix compiler warning introduced in 6df7a9698b |