Re: [HACKERS] Shouldn't duplicate addition to publication be a no-op?
| От | Amit Langote |
|---|---|
| Тема | Re: [HACKERS] Shouldn't duplicate addition to publication be a no-op? |
| Дата | |
| Msg-id | 65e0e78f-5b0c-8cd6-c5eb-326a9e36a302@lab.ntt.co.jp обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Shouldn't duplicate addition to publication be a no-op? (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
| Ответы |
Re: [HACKERS] Shouldn't duplicate addition to publication be a no-op?
|
| Список | pgsql-hackers |
On 2017/04/15 8:53, Peter Eisentraut wrote: > 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. Hmm, okay. So I guess the grammar support will be added later. By the way, Petr said in the other thread that it could be made a no-op (presumably without requiring IF NOT EXISTS) on the grounds that membership of table in publication is "soft object" or "property" rather than real object. Thanks, Amit
В списке pgsql-hackers по дате отправления: