forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit929c69a
committed
In pg_restore's dump_lo_buf(), work a little harder on error handling.
Failure to write data to a large object during restore led to an uglyand uninformative error message. To add insult to injury, it thenfatal'd out, where other SQL-level errors usually result in pressing on.Report the underlying error condition, rather than just giving not-very-useful byte counts, and use warn_or_exit_horribly() so as to adhere topg_restore's general policy about whether to continue or not.Also recognize that lo_write() returns int not size_t.Per report from Justin Pryzby, though I didn't use his patch.Given the lack of comparable complaints, I'm not sure this isworth back-patching.Discussion:https://postgr.es/m/20201018010232.GF9241@telsasoft.com1 parent7d00a6b commit929c69a
1 file changed
+7
-6
lines changedLines changed: 7 additions & 6 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
1637 | 1637 |
| |
1638 | 1638 |
| |
1639 | 1639 |
| |
1640 |
| - | |
| 1640 | + | |
1641 | 1641 |
| |
1642 | 1642 |
| |
1643 |
| - | |
1644 |
| - | |
| 1643 | + | |
| 1644 | + | |
1645 | 1645 |
| |
1646 |
| - | |
| 1646 | + | |
| 1647 | + | |
1647 | 1648 |
| |
1648 |
| - | |
1649 |
| - | |
| 1649 | + | |
| 1650 | + | |
1650 | 1651 |
| |
1651 | 1652 |
| |
1652 | 1653 |
| |
|
0 commit comments
Comments
(0)