From: | Steven Winfield <Steven(dot)Winfield(at)cantabcapital(dot)com> |
---|---|
To: | Marko Tiikkaja <marko(at)joh(dot)to> |
Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | RE: BUG #14953: pg_blocking_pids / array_length inconsistency |
Date: | 2017-12-07 15:13:01 |
Message-ID: | E9FA92C2921F31408041863B74EE4C2001A46B3347@CCPMAILDAG03.cantab.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Thanks - I hadn’t spotted that, even though it was added in 9.4.
Steven.
From: Marko Tiikkaja [mailto:marko(at)joh(dot)to]
Sent: 07 December 2017 15:07
To: Steven Winfield
Cc: Pg Bugs
Subject: Re: BUG #14953: pg_blocking_pids / array_length inconsistency
On Thu, Dec 7, 2017 at 3:40 PM, <steven(dot)winfield(at)cantabcapital(dot)com<mailto:steven(dot)winfield(at)cantabcapital(dot)com>> wrote:
For what it's worth, I think having array_length('{}'::integer[], 1) = 0 is
far more sensible, and
making differently-dimensioned empty arrays compare equal (as mentioned
previously[1]) is quite confusing.
I'm not saying this isn't a bug, but you might want to start using the cardinality() function for comparisons like this.
.m
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-12-07 15:27:24 | Re: BUG #14953: pg_blocking_pids / array_length inconsistency |
Previous Message | Marko Tiikkaja | 2017-12-07 15:07:27 | Re: BUG #14953: pg_blocking_pids / array_length inconsistency |