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

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com>, Tomas Vondra <tv(at)fuzzy(dot)cz>, PostgreSQL Hackers <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-21 07:35:35
Message-ID: CAFj8pRBtY8ayyVYKLhSFJHL68-QdDJxFAFQ_Cm7H+3AN663RnQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Hello

2013/11/19 Robert Haas <robertmhaas(at)gmail(dot)com>

> On Tue, Nov 19, 2013 at 3:53 AM, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
> wrote:
> > 1). Keep the existing syntax:
> >
> > DROP TRIGGER [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ];
> >
> > but make it tolerate a non-existent table when "IF EXISTS" is specified.
>
> I don't love this option, but I like it better than the other proposals.
>

we are in agreement, so we want this feature. How we can decide about
syntax?

I am feeling, so almost all people prefer

DROP TRIGGER [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ];

Can we live with it?

Regards

Pavel

> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Oliver Munyao 2013-11-21 15:29:08 pgdump not dumping my database
Previous Message eduardoa 2013-11-20 19:35:12 BUG #8612: Truncate did not release disk space

Browse pgsql-hackers by date

  From Date Subject
Next Message Szymon Guz 2013-11-21 08:07:12 Re: new unicode table border styles for psql
Previous Message Pavel Stehule 2013-11-21 07:09:05 new unicode table border styles for psql