Re: Unexpected array_remove results - Mailing list pgsql-general

From Tom Lane
Subject Re: Unexpected array_remove results
Date
Msg-id 25825.1426859895@sss.pgh.pa.us
Whole thread Raw
In response to Unexpected array_remove results  (Matija Lesar <matija.lesar@gmail.com>)
Responses Re: Unexpected array_remove results  (Matija Lesar <matija.lesar@gmail.com>)
List pgsql-general
Matija Lesar <matija.lesar@gmail.com> writes:
> should not in example below array_remove return same results?

AFAICS, array_remove keeps the existing lower bound number.  I don't
see anything particularly wrong with that definition.

Even if we didn't care about backwards compatibility, it would require
nontrivial effort to change it --- for example, there are several
early-exit cases that return the original array unmodified, and that would
be wrong if we were to adopt some other definition such as "force the
lower bound to 1".

            regards, tom lane


pgsql-general by date:

Previous
From: Matija Lesar
Date:
Subject: Unexpected array_remove results
Next
From: Vladimir Borodin
Date:
Subject: Re: [pgadmin-support] Issue with a hanging apply process on the replica db after vacuum works on primary