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

From Peter Eisentraut
Subject Re: [HACKERS] Shouldn't duplicate addition to publication be a no-op?
Date
Msg-id c871da7b-a727-8d20-f966-f61e2ccf0d3d@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] Shouldn't duplicate addition to publication be a no-op?  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: [HACKERS] Shouldn't duplicate addition to publication be a no-op?  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List 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 by date:

Previous
From: Rod Taylor
Date:
Subject: Re: [HACKERS] Row Level Security UPDATE Confusion
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Allowing extended stats on foreign and partitionedtables