Re: lbound1 default in buildint2vector/buildoidvector

From: Kohei KaiGai <kaigai(at)heterodb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: lbound1 default in buildint2vector/buildoidvector
Date: 2018-11-15 12:16:46
Message-ID: CAOP8fzbixeFZ_xdzmqK8jU=--E-BGnfFJ8B1+XdSq_WGrnJ6Lg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2018年11月15日(木) 12:41 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> Kohei KaiGai <kaigai(at)heterodb(dot)com> writes:
> > I noticed buildint2vector / buildoidvector assigns lbound1=0 as default
> > value, but array type shall have lbound1=1 in the default.
> > Is there some reasons for the difference?
>
> Backwards compatibility.
>
Ah, yes, I got the point.

--
HeteroDB, Inc / The PG-Strom Project
KaiGai Kohei <kaigai(at)heterodb(dot)com>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2018-11-15 12:30:25 Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock
Previous Message John Naylor 2018-11-15 12:13:51 Re: doc fix for pg_stat_activity.backend_type