Re: Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Tomas Vondra <tv(at)fuzzy(dot)cz>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist
Date: 2013-11-11 01:13:05
Message-ID: 9280.1384132385@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> 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 ]

Works for me.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-11-11 01:57:15 Re: BUG #8532: postgres fails to start with timezone-data >=2013e
Previous Message digoal 2013-11-11 00:20:58 Re: BUG #8531: systemtap probe mark(checkpoint__done) error when i read the parameters

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-11-11 04:00:07 Re: Another bug(?) turned up by the llvm optimization checker
Previous Message Tom Lane 2013-11-11 01:06:30 Relax table alias conflict rule in 9.3?