Re: pg_restore error message during ENOSPC with largeobj - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_restore error message during ENOSPC with largeobj
Date
Msg-id 153809.1602988903@sss.pgh.pa.us
Whole thread Raw
In response to pg_restore error message during ENOSPC with largeobj  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: pg_restore error message during ENOSPC with largeobj
List pgsql-hackers
Justin Pryzby <pryzby@telsasoft.com> 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)

Bleah.

> 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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "Hou, Zhijie"
Date:
Subject: RE: Parallel copy
Next
From: Alvaro Herrera
Date:
Subject: Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?