From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: pg_backup symlink? |
Date: | 2000-07-10 22:41:19 |
Message-ID: | 200007102241.SAA04975@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> At 00:24 11/07/00 +0200, Peter Eisentraut wrote:
> >Philip Warner writes:
> >
> >> Does anyone have a philosophical objection to a symlink from pg_dump to
> >> (new) pg_backup?
> >
> >Yes. The behaviour of a program should not depend on the name used to
> >invoke it. You can use shell aliases or scripts for that.
>
> OK, I suppose I was thinking of the pg_dump symlink as a tool for
> compatibility.
>
> Is there a good solution? It dumps to text for compatibility with the old
> pg_dump, but I will most often use 'pg_dump -Fc --blob'. Is there a
> recommended 'correct' approach?
The BSD way is to define an environment variable that is used to supply
additional arguments to the command. For example, BLOCKSIZE controls if
blocks are reported in 512 or 1k sizes by commands like du.
--
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 | Ed Loehr | 2000-07-10 22:44:02 | Re: Slashdot discussion |
Previous Message | Bruce Momjian | 2000-07-10 22:39:21 | Re: Slashdot discussion |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Mount | 2000-07-10 22:41:46 | Re: postgres fe/be protocol |
Previous Message | Bruce Momjian | 2000-07-10 22:39:21 | Re: Slashdot discussion |