Thread: Change < to -f in examples with input files
Folks, Please find enclosed a patch, per Dennis Björklund, that uses -f for input files rather than <. This makes error messages, &c. more expressive. Cheers, D -- David Fetter david@fetter.org http://fetter.org/ phone: +1 510 893 6100 mobile: +1 415 235 3778 Remember to vote!
Attachment
David Fetter wrote: > Please find enclosed a patch, per Dennis Björklund, that uses -f for > input files rather than <. This makes error messages, &c. more > expressive. To be portable, options must be before non-option arguments, so you need to rearrange the command-line arguments in the examples if you want to make that change. -- Peter Eisentraut http://developer.postgresql.org/~petere/
David Fetter wrote: > > Please find enclosed a patch, per Dennis Bj<C3><B6>rklund, that uses -f for > input files rather than <. This makes error messages, &c. more > expressive. Uh, how is it more expressive? The only difference I see is the line numbers. Is that it? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
On Mon, Feb 21, 2005 at 02:18:31PM -0500, Bruce Momjian wrote: > David Fetter wrote: > > > > Please find enclosed a patch, per Dennis Bj<C3><B6>rklund, that > > uses -f for input files rather than <. This makes error messages, > > &c. more expressive. > > Uh, how is it more expressive? The only difference I see is the > line numbers. Is that it? That could be a very big deal in case of error on a large file, so yes. Cheers, D -- David Fetter david@fetter.org http://fetter.org/ phone: +1 510 893 6100 mobile: +1 415 235 3778 Remember to vote!
>>Uh, how is it more expressive? The only difference I see is the >>line numbers. Is that it? > > > That could be a very big deal in case of error on a large file, so > yes. In IRC, I always recommend that ppl use -f, since it's so much more useful :) Chris
David Fetter wrote: > Please find enclosed a patch, per Dennis Bj<C3><B6>rklund, that uses -f > for input files rather than <. This makes error messages, &c. more > expressive. > > David Fetter Applied. Thanks. (I reordered the arguments as Peter suggested.) -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 Index: doc/src/sgml/backup.sgml =================================================================== RCS file: /projects/cvsroot/pgsql/doc/src/sgml/backup.sgml,v retrieving revision 2.55 diff -c -r2.55 backup.sgml *** doc/src/sgml/backup.sgml 22 Jan 2005 22:56:35 -0000 2.55 --- doc/src/sgml/backup.sgml 20 Feb 2005 20:45:07 -0000 *************** *** 177,183 **** </synopsis> The resulting dump can be restored with <application>psql</>: <synopsis> ! psql template1 < <replaceable class="parameter">infile</replaceable> </synopsis> (Actually, you can specify any existing database name to start from, but if you are reloading in an empty cluster then <literal>template1</> --- 177,183 ---- </synopsis> The resulting dump can be restored with <application>psql</>: <synopsis> ! psql -f <replaceable class="parameter">infile</replaceable> template1 </synopsis> (Actually, you can specify any existing database name to start from, but if you are reloading in an empty cluster then <literal>template1</> *************** *** 1210,1216 **** gmake install initdb -D /usr/local/pgsql/data postmaster -D /usr/local/pgsql/data ! psql template1 < backup </programlisting> See <xref linkend="runtime"> about ways to start and stop the --- 1210,1216 ---- gmake install initdb -D /usr/local/pgsql/data postmaster -D /usr/local/pgsql/data ! psql -f backup template1 </programlisting> See <xref linkend="runtime"> about ways to start and stop the