pgsql: Further thoughts about lo_export/lo_import error handling: if one - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Further thoughts about lo_export/lo_import error handling: if one
Date
Msg-id 20060614174925.B7AE09F9FE3@postgresql.org
Whole thread Raw
List 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)

pgsql-committers by date:

Previous
From: dezelin@pgfoundry.org (User Dezelin)
Date:
Subject: pgguid - pgguid: initial not compilable version
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Add entry: > * Allow user-defined types to accept 'typmod'