Re: [HACKERS] Shouldn't duplicate addition to publication be a no-op?

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: [HACKERS] Shouldn't duplicate addition to publication be a no-op?
Дата
Msg-id c871da7b-a727-8d20-f966-f61e2ccf0d3d@2ndquadrant.com
обсуждение исходный текст
Ответ на [HACKERS] Shouldn't duplicate addition to publication be a no-op?  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Ответы Re: [HACKERS] Shouldn't duplicate addition to publication be a no-op?
Список pgsql-hackers
On 4/13/17 06:23, Amit Langote wrote:
> create table bar (a int);
> create publication mypub for table bar;
> alter publication mypub add table bar;
> ERROR:  relation "bar" is already member of publication "mypub"
> 
> 2nd command should be a no-op, IMHO.

We generally require a IF NOT EXISTS in those situations.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Rod Taylor
Дата:
Сообщение: Re: [HACKERS] Row Level Security UPDATE Confusion
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: [HACKERS] Allowing extended stats on foreign and partitionedtables