Horton

Re: pg_restore error message during ENOSPC with largeobj

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@postgresql.org, Peter Eisentraut <peter_e@gmx.net>
Date: 2020-10-18T16:27:36Z
Lists: pgsql-hackers 
I wrote:
> Isn't the real problem that lo_write returns int, not size_t?

After looking at it some more, I decided that we'd just been lazy
to begin with: we should be handling this as a regular SQL error
condition.  Pushed at 929c69aa19.

			regards, tom lane

Commits

  1. In pg_restore's dump_lo_buf(), work a little harder on error handling.

  2. Enable large file support.