Re: pg_dump 'die_on_errors'

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump 'die_on_errors'
Date: 2004-08-11 16:31:09
Message-ID: 10830.1092241869@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> The default setting of 'false' is a pain. And the fact it can't be changed
> by an option is even more of a pain. Any objections to adding an option to
> pg_restore to allow 'die_on_errors' to be set to 'true'?

If you like, but that change was deliberate and the result of
considerable experience that says die_on_errors is NOT the right
behavior for pg_restore.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2004-08-11 16:33:00 Re: pg_dump 'die_on_errors'
Previous Message Philip Warner 2004-08-11 16:09:16 pg_restore (libpq? parser?) bug in 8

Browse pgsql-patches by date

  From Date Subject
Next Message Fabien COELHO 2004-08-11 16:33:00 Re: pg_dump 'die_on_errors'
Previous Message Andreas Pflug 2004-08-11 16:15:11 Re: GUC variables invisible to contrib/ modules