| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martin Marques <martin(at)marquesminen(dot)com(dot)ar> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Archive_command |
| Date: | 2008-05-05 14:25:18 |
| Message-ID: | 28758.1209997518@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martin Marques <martin(at)marquesminen(dot)com(dot)ar> writes:
> I have a question related to the archive_command option of postgresql.conf.
> In the documentation[1] I found examples that add a "< /dev/null" at the
> end of the cp command. I know what the redirection from /dev/null does
> (send an EOF), but is it really needed?
The examples that have that are using "cp -i", and the point of the
redirect is to ensure that cp doesn't eat any input intended for someone
else if it actually does see a conflict (and try to prompt the user).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2008-05-05 14:33:30 | Re: operator varchar = integer |
| Previous Message | Martin Marques | 2008-05-05 14:18:29 | Archive_command |