Re: CREATE OR REPLACE AGGREGATE -- NOT!

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: dandl <david(at)andl(dot)org>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: CREATE OR REPLACE AGGREGATE -- NOT!
Date: 2016-05-05 04:06:29
Message-ID: CAKFQuwarFbF4-SdWek8Z26oykn_EF3Rw-XrU7aq67DxAsVd1AA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wednesday, May 4, 2016, dandl <david(at)andl(dot)org> wrote:

> I was surprised to discover that
>
> · CREATE OR REPLACE AGGREGATE is not allowed, but
>
> · CREATE OR REPLACE FUNCTION works just fine
>
>
>
> Is this an oversight, or is there some reason I missed?
>
>
Its not an oversight: but whether it is easily accomplished, or worthy of
the effort, is a different matter.

> Yes, I know I can do:
>
> DROP AGGREGATE IF EXISTS
>
> CREATE AGGREGATE
>
>
>
> But this triggers a NOTICE. Is there any convenient way to replace a
> (possibly) existing aggregate function without triggering a NOTICE?
>
>
Set client_min_messages = warning;

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2016-05-05 04:08:59 Re: Debian and Postgres
Previous Message rob stone 2016-05-05 02:40:40 Re: Debian and Postgres