Commit98bd4c7

committed

pg_dump: Have _EndLO report errno after CFH->write_func() failure

Other callers of that function do things this way, but this one didn'tget the memo.

1 parent69c4306 commit98bd4c7Copy full SHA for 98bd4c7

File tree

-1

lines changed

-1

lines changed

Lines changed: 7 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -697,7 +697,13 @@ _EndLO(ArchiveHandle AH, TocEntry te, Oid oid)`
`697`	`697`	`/* register the LO in blobs.toc */`
`698`	`698`	`len=snprintf(buf,sizeof(buf),"%u blob_%u.dat\n",oid,oid);`
`699`	`699`	`if (!CFH->write_func(buf,len,CFH))`
`700`		`-pg_fatal("could not write to LOs TOC file");`
	`700`	`+{`
	`701`	`+/* if write didn't set errno, assume problem is no disk space */`
	`702`	`+if (errno==0)`
	`703`	`+errno=ENOSPC;`
	`704`	`+pg_fatal("could not write to LOs TOC file: %s",`
	`705`	`+CFH->get_error_func(CFH));`
	`706`	`+}`
`701`	`707`	`}`
`702`	`708`
`703`	`709`	`/*`

Comments

(0)