> I very much doubt pg_dump would be seeking or telling on stdout, as it may
> be a pipe, a tty, a socket, etc., so you can skip the cat and just do
> pg_dump > dumpfile.sql.
>
> Oh, and cat doesn't need to be largefile-enabled as it never seeks in
> files, as neither does pg_dump, as it doesn't, or shouldn't (I see no need
> for), seek in the output file.
no and no, this will *not* work; the file has to be opened with the flag
O_LARGEFILE, otherwise the kernel will refuse to write files larger than
2GB. Really.
Regards
--
Helge Bahmann <bahmann@math.tu-freiberg.de> /| \__
The past: Smart users in front of dumb terminals /_|____\
_/\ | __)
$ ./configure \\ \|__/__|
checking whether build environment is sane... yes \\/___/ |
checking for AIX... no (we already did this) |