error and do update instead
update...
...more stuff...
commit;
Also, the blunder-on-regardless approach is popular in pg_dump, or so I'm
told ;-).
Philip Warner| __---_
Albatross Consulting Pty. Ltd
.
Philip Warner| __---_
Albatross Consulting Pty. Ltd. |/ - \
(A.B.N. 75 008 659 498) | /(@) __---_
Tel: (+61) 0500 83 82 81 | _ \
Fax: (+61) 03 5330 3172 | ___ |
Http
them. Or a statement count.
Philip Warner| __---_
Albatross Consulting Pty. Ltd. |/ - \
(A.B.N. 75 008 659 498) | /(@) __---_
Tel: (+61) 0500 83 82 81
-}.
Philip Warner| __---_
Albatross Consulting Pty. Ltd. |/ - \
(A.B.N. 75 008 659 498) | /(@) __---_
Tel: (+61) 0500 83 82 81 | _ \
Fax: (+61) 03 5330 3172
At 01:22 AM 19/08/2004, Tom Lane wrote:
Philip Warner [EMAIL PROTECTED] writes:
If the patch is not kosher, then I'd vote for adding a do not parse flag
on the TOC entries when dumping them. Or a statement count.
Unless you plan to abandon compatibility with existing dump files,
this doesn't
At 02:32 PM 12/08/2004, Philip Warner wrote:
At 01:27 PM 12/08/2004, Bruce Momjian wrote:
Set client_min_messages to WARNING?
Sounds like a plan.
Attached patch sets client_min_messages as above and gives some
context to errors messages, eg:
pg_restore: [archiver (db)] Error from TOC Entry 19
...
Philip Warner| __---_
Albatross Consulting Pty. Ltd. |/ - \
(A.B.N. 75 008 659 498) | /(@) __---_
Tel: (+61) 0500 83 82 81 | _ \
Fax: (+61) 03 5330 3172 | ___ |
Http
that the
tag chars are valid. If so, it processes the $-quote.
Tested against local DBs and regression DB.
Philip Warner| __---_
Albatross Consulting Pty. Ltd. |/ - \
(A.B.N. 75 008 659 498
At 12:59 PM 21/07/2004, Bruce Momjian wrote:
Yes, no need for it. We discourage that.
Might be polite, not to mention legally required, to check with the author
of the patch first.
Philip Warner
