| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
| Cc: | Dave Rolsky <autarch(at)urth(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist |
| Date: | 2013-07-10 15:06:18 |
| Message-ID: | CAFj8pRC+eaifgXvm9RmLZjuxxT72KZUAFm0yxki+3RcOP57r4A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Yes, I wrote a separate patch for next commitfest.
Dne 10.7.2013 16:54 "Josh Kupershmidt" <schmiddy(at)gmail(dot)com> napsal(a):
> On Fri, Jul 5, 2013 at 12:16 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
>
> > I am sending a patch that removes strict requirements for DROP IF
> > EXISTS statements. This behave is similar to our ALTER IF EXISTS
> > behave now.
>
> +1 for this idea. But this patch should be treated as a separate issue
> from the use of IF EXISTS in pg_dump/pg_restore, right? If so, I
> suggest starting a new thread about this patch to make reviewing
> easier.
>
> Josh
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pg noob | 2013-07-10 15:14:07 | Re: BUG #8290: broken/unexpected locking behavior |
| Previous Message | Josh Kupershmidt | 2013-07-10 14:54:10 | Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Kupershmidt | 2013-07-10 15:17:06 | Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist |
| Previous Message | Merlin Moncure | 2013-07-10 14:55:54 | Re: Millisecond-precision connect_timeout for libpq |