| From: | Erik Rijkers <er(at)xs4all(dot)nl> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| 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:33:32 |
| Message-ID: | 97f7b1ac0edf2a550c33f437b7aa08c4@xs4all.nl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On 2020-12-20 14:18, Alexander Korotkov 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.
Sorry, you're right, of course. I misread my output.
It occurs only without --enable-cassert
>
> ------
> Regards,
> Alexander Korotkov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2020-12-20 13:37:48 | Re: pgsql: Multirange datatypes |
| Previous Message | Alexander Korotkov | 2020-12-20 13:31:13 | Re: pgsql: Multirange datatypes |