pgsql: Further thoughts about lo_export/lo_import error handling: if one

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Further thoughts about lo_export/lo_import error handling: if one
Date: 2006-06-14 17:49:25
Message-ID: 20060614174925.B7AE09F9FE3@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Further thoughts about lo_export/lo_import error handling: if one of
the lower-level large object functions fails, it will have already set
a suitable error message --- probably something from the backend ---
and it is not useful to overwrite that with a generic 'error while
reading large object' message. So remove redundant messages.

Modified Files:
--------------
pgsql/src/interfaces/libpq:
fe-lobj.c (r1.57 -> r1.58)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-lobj.c.diff?r1=1.57&r2=1.58)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2006-06-14 17:51:55 pgsql: Add entry: > * Allow user-defined types to accept 'typmod'
Previous Message User Dezelin 2006-06-14 17:45:02 pgguid - pgguid: initial not compilable version