| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Heikki Linnakangas *EXTERN* <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: problem with archive_command as suggested by documentation |
| Date: | 2009-01-26 12:06:45 |
| Message-ID: | 497DA755.8060807@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
> I don't think that particular example is a good one since the whole
> point of the archive is that it should be off-server. If we're going to
> be exact about the example then we should give a more realistic one,
> like using scp. Unfortunately, there is no secure-remote-move command,
> so doing the above with scp would resend the whole file 3 times. I think
> it's better to write a script...
The problem is that most people do copy the stuff straight out of the
documentation. And for those that do write a separate script, there are
still a lot of possibilities to get it wrong.
There are only about a handful of transportation protocols appearing in
practice, so it would be very helpful to provide carefully reviewed
scripts or recipes for these.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-01-26 12:30:42 | Re: [PATCH] reloptions - RELOPT_KIND_ALL |
| Previous Message | Dave Page | 2009-01-26 11:53:33 | Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules) |