| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, 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-12-05 10:03:35 |
| Message-ID: | CAFj8pRD9n9O_jtu9msvieqN8g-cKy-zdc88+4kKxSx1YDo5chQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Hello
2013/12/5 Peter Eisentraut <peter_e(at)gmx(dot)net>
> Can someone in this thread clarify the commit fest situation? I see two
> entries that appear to be the same:
>
> https://commitfest.postgresql.org/action/patch_view?id=1174
> https://commitfest.postgresql.org/action/patch_view?id=1175
>
> I think the first one is a duplicate or obsolete.
>
no, both are valid, and every solve different issue.
https://commitfest.postgresql.org/action/patch_view?id=1175
it implements fully fault tolerant DROP IF EXISTS statements. This patch is
prerequisite for second patch
https://commitfest.postgresql.org/action/patch_view?id=1174
This is a implementation of new pg_dump option --if-exists. This option
ensure using fault tolerant DROPs statement by dump.
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2013-12-05 10:06:22 | Re: Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist |
| Previous Message | Andres Freund | 2013-12-05 09:59:49 | Re: BUG #8647: Backend process hangs and becomes unkillable when SSL client looses connection |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2013-12-05 10:06:22 | Re: Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist |
| Previous Message | Simon Riggs | 2013-12-05 09:57:50 | Re: Time-Delayed Standbys |