Re: BUG #14953: pg_blocking_pids / array_length inconsistency

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: steven(dot)winfield(at)cantabcapital(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14953: pg_blocking_pids / array_length inconsistency
Date: 2017-12-07 15:27:24
Message-ID: 5161.1512660444@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

steven(dot)winfield(at)cantabcapital(dot)com writes:
> It seems as though pg_blocking_pids() can return a zero-length,
> one-dimensional array whereas users can only create NULL-length,
> zero-dimensional arrays (even though the type suggests it is one
> dimensional: 'integer[]')

This has been fixed recently in HEAD:
https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=716ea626a

but we decided not to back-patch the change.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bernd Helmle 2017-12-07 15:47:18 PostgreSQL crashes with SIGSEGV
Previous Message Steven Winfield 2017-12-07 15:13:01 RE: BUG #14953: pg_blocking_pids / array_length inconsistency