Обсуждение: CREATE OR REPLACE AGGREGATE -- NOT!
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?
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?
Regards
David M Bennett FACS
Andl - A New Database Language - andl.org
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?
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?
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.