Re: pg_restore error message during ENOSPC with largeobj

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: pg_restore error message during ENOSPC with largeobj
Date: 2020-10-18 16:27:36
Message-ID: 224575.1603038456@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-10-18 17:20:12 Non-configure build of thread_test has been broken for awhile
Previous Message Noah Misch 2020-10-18 12:51:47 Re: public schema default ACL