Re: CREATE OR REPLACE AGGREGATE -- NOT! - Mailing list pgsql-general

From David G. Johnston
Subject Re: CREATE OR REPLACE AGGREGATE -- NOT!
Date
Msg-id CAKFQuwarFbF4-SdWek8Z26oykn_EF3Rw-XrU7aq67DxAsVd1AA@mail.gmail.com
Whole thread Raw
In response to CREATE OR REPLACE AGGREGATE -- NOT!  ("dandl" <david@andl.org>)
Responses Re: CREATE OR REPLACE AGGREGATE -- NOT!
List pgsql-general
On Wednesday, May 4, 2016, dandl <david@andl.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.

pgsql-general by date:

Previous
From: rob stone
Date:
Subject: Re: Debian and Postgres
Next
From: Adrian Klaver
Date:
Subject: Re: Debian and Postgres