Re: -f <output file> option for pg_dumpall

From: "Dave Page" <dpage(at)postgresql(dot)org>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: -f <output file> option for pg_dumpall
Date: 2007-01-06 08:51:10
Message-ID: 200701060851100000@494532763
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> ------- Original Message -------
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> To: Dave Page <dpage(at)postgresql(dot)org>
> Sent: 1/5/07, 10:48:17 PM
> Subject: Re: [HACKERS] -f <output file> option for pg_dumpall
>
>
> Wouldn't it be easier/better to re-point stdout at the -f file, and not
> touch pg_dump at all?

First thing I tried, but using virtually identical code to that which we use with pg_dump it just hangs. The debugger tells me there's a deadlock - my best guess is that stdin/out/err of the child shell & pg_dump processes don't get redirected along with their parents. I'm testing on Windows btw - dunno if *nix would be different.

/D

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2007-01-06 08:55:19 Re: -f <output file> option for pg_dumpall
Previous Message Andrew Dunstan 2007-01-06 05:02:32 Re: ideas for auto-processing patches