Re: CREATE OR REPLACE AGGREGATE -- NOT!

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: CREATE OR REPLACE AGGREGATE -- NOT!
Дата
Msg-id CAKFQuwarFbF4-SdWek8Z26oykn_EF3Rw-XrU7aq67DxAsVd1AA@mail.gmail.com
обсуждение исходный текст
Ответ на CREATE OR REPLACE AGGREGATE -- NOT!  ("dandl" <david@andl.org>)
Ответы Re: CREATE OR REPLACE AGGREGATE -- NOT!  ("dandl" <david@andl.org>)
Список 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 по дате отправления:

Предыдущее
От: rob stone
Дата:
Сообщение: Re: Debian and Postgres
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: Debian and Postgres