Re: Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist
От | Andres Freund |
---|---|
Тема | Re: Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist |
Дата | |
Msg-id | 20131110235703.GJ32665@awork2.anarazel.de обсуждение исходный текст |
Ответ на | Re: Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist
|
Список | pgsql-hackers |
On 2013-11-10 18:42:11 -0500, Tom Lane wrote: > Andres Freund <andres@2ndquadrant.com> writes: > > ... So we'd get approximately one line further unless we fix this for DROP > > DEFAULT and DROP CONSTRAINT as well. Turns out that's bogus - ALTER TABLE has two levels of NOT EXISTS. Maybe we should just do the same for DROP TRIGGER? DROP TRIGGER [ IF EXISTS ] name ON table_name [ IF EXISTS ] [ CASCADE | RESTRICT ] > However, the server-side approach has the benefit that it'll > likely make life easier for other applications besides pg_dump. I am unconvinced that that's the case when using the existing IF EXISTS for DROP TRIGGER, but my complaints would be completely addressed by making it a separate flag. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: