Re: Surprising results from array concatenation

From: Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Surprising results from array concatenation
Date: 2017-04-25 18:23:14
Message-ID: CANPAkgsoqbRQ9mhZKF=OrL42qT9tdYqym8-=OpMHtAKhGEcwkg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Apr 25, 2017 at 12:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Yeah. The core problem here is that the parser has to disambiguate the
> || operator: is it "anyarray || anyelement" or "anyarray || anyarray"?
>
​<...>​

> Peeking at the contents of the literal would make the behavior very
> unpredictable/data-dependent, so we don't.

​Fair enough.

Would a note in that section of the docs pointing out this behavior be
worthwhile?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jerry Sievers 2017-04-25 18:56:28 Re: Questionaire: Common WAL write rates on busy servers.
Previous Message Tom Lane 2017-04-25 17:53:17 Re: Surprising results from array concatenation