]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f3164c0) | patch
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)
commit2193beb76104507acc3ecd7c2cc2394d092d0706
tree34953fbe628e09d7fc3ec36acf8863a59d0c9ad1tree | snapshot
parentf3164c020028de70e4cd991ccbd3d696c9060709commit | diff
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 diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.