pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: adam@labkey.com
Subject: BUG #17034: Creating aggregate function based on array_append now results in "function does not exist" error
Date: Tue, 25 May 2021 22:58:31 +0000
Message-ID: <17034-065ef2f6a560c7cb@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      17034
Logged by:          Adam Rauch
Email address:      adam@labkey.com
PostgreSQL version: 14beta1
Operating system:   Windows 10
Description:        

The DDL below has executed correctly on every PostgreSQL version through
13.x. In 14 beta 1, it produces: "ERROR:  function array_append(anyarray,
anyelement) does not exist  SQL state: 42883"

CREATE AGGREGATE core.array_accum (anyelement)
(
  sfunc = array_append,
  stype = anyarray,
  initcond = '{}'
);

We long ago stopped using this aggregate function (switched to built-in
functions array_agg and string_agg), so we can simply remove this DDL (i.e.,
we don't care if it's fixed or not). But other systems may be affected by
this change. If nothing else, a mention in the release notes would be
helpful.



view thread (2+ messages)  latest in thread

Message-ID: <17034-065ef2f6a560c7cb@postgresql.org>
Permalink:  ../17034-065ef2f6a560c7cb@postgresql.org/
Also on:    postgresql.org/message-id/17034-065ef2f6a560c7cb@postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, adam@labkey.com
  Subject: Re: BUG #17034: Creating aggregate function based on array_append now results in "function does not exist" error
  In-Reply-To: <17034-065ef2f6a560c7cb@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox