Bruce Momjian <[EMAIL PROTECTED]> writes:
> If people want this, can I get some wording?
* Make pg_restore continue after errors, so it acts more like pg_dump scripts
regards, tom lane
---(end of broadcast)---
TIP 1: subscri
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > If people want this, can I get some wording?
>
> * Make pg_restore continue after errors, so it acts more like pg_dump scripts
Added.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED]
Fabien COELHO wrote:
>
> > Fabien COELHO <[EMAIL PROTECTED]> writes:
> > > It would make sense to ignore some alter/drop errors in pg_restore.
> >
> > [...]
> >
> > This issue has been on the radar screen for awhile, but no one has
> > gotten around to making it happen...
>
> Maybe it could be ap
> Fabien COELHO <[EMAIL PROTECTED]> writes:
> > It would make sense to ignore some alter/drop errors in pg_restore.
>
> [...]
>
> This issue has been on the radar screen for awhile, but no one has
> gotten around to making it happen...
Maybe it could be appended to the "todo" list, so as not to b
Fabien COELHO <[EMAIL PROTECTED]> writes:
> It would make sense to ignore some alter/drop errors in pg_restore.
For the most part I think pg_restore should ignore *all* SQL errors and
try to keep plugging. This would more nearly emulate the behavior of
pg_dump SQL scripts, which is the older and
Hello,
I think I have found a feature of pg_restore that may be a bug.
If the --clean option AND --dbname=database option are used with an
initially empty database, the restoration fails, although the very same
options with a "| psql database" works fine.
The internal psql with --dbname option
