Further thoughts about lo_export/lo_import error handling: if one of
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 14 Jun 2006 17:49:25 +0000 (17:49 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 14 Jun 2006 17:49:25 +0000 (17:49 +0000)
commit015c5a0b6b96ede6f59c45b370506e077d34d6e6
treef93c83ea4f993a4fbf0b459061c0d4f830931b5b
parente555fc7adf14276ad16f22e4551821a10946d38d
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.
src/interfaces/libpq/fe-lobj.c