Postgres Pro
Downloads
Home   >   mailing lists

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

From dandl
Subject Re: CREATE OR REPLACE AGGREGATE -- NOT!
Date
Msg-id 007901d1a732$042a9d00$0c7fd700$@andl.org
Whole thread Raw
In response to Re: CREATE OR REPLACE AGGREGATE -- NOT!  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
Tree view

Thanks. Much as I expected.

 

No, I don’t think it would be hard to do. Maybe if I ever feel a pressing need to learn how to submit a patch it might be something to start with.

 

Regards

David M Bennett FACS

Andl - A New Database Language - andl.org

 

 

From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of David G. Johnston
Sent: Thursday, 5 May 2016 2:06 PM
To: dandl <david@andl.org>
Cc: Postgres General <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] CREATE OR REPLACE AGGREGATE -- NOT!

 

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: "drum.lucas@gmail.com"
Date:
Subject: Re: Function PostgreSQL 9.2
Next
From: Eric Ridge
Date:
Subject: Re: How to manually force a transaction wraparound