Re: pg_restore error message during ENOSPC with largeobj
Justin Pryzby <[hidden email]> writes:
> I overflowed my homedir while testing with pg_reload, and got:
> |pg_restore: error: could not write to large object (result: 18446744073709551615, expected: 30)
> I guess casting to long was the best option c. 2002 (commit 6faf8024f) but I
> gather the modern way is with %z.
Isn't the real problem that lo_write returns int, not size_t?
AFAICT, every other call site stores the result in an int,
it's just this one that's out in left field.