From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Roadmap for a Win32 port |
Date: | 2002-06-08 15:57:07 |
Message-ID: | 200206081557.g58Fv7B12506@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> >> Also, it seems Win32 doesn't need these scripts, except initdb.
>
> > The utility of these programs is independent of the platform. If we think
> > pg_dumpall is not useful, then let's remove it.
>
> I have been seriously considering converting pg_dumpall to C anyway,
> because it's already *very* messy, and I don't see any reasonable
> way to make it support dumping per-database and per-user config
> settings. (Do you really want to try to parse array values in a
> shell script?)
>
> (I'd actually consider making pg_dumpall a part of the pg_dump
> executable; then it could invoke pg_dump as a subroutine call...)
>
> If Peter's got the time/energy to convert 'em all, I'm for it.
Yea, shame it will now take 15 lines of C code to do what we could do in
1 line of shell script but I don't see any other option.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-06-08 16:03:07 | Re: [HACKERS] Schemas: status report, call for developers |
Previous Message | Tom Lane | 2002-06-08 15:52:50 | Re: Question whether this is a known problem in 7.1.2 |