Andrus wrote:
> Richard,
>
>> Use scp. Open port 22 and allow only connections from the backup machine
>> with a specified user (e.g. "pgbackup").
>>
>> Alternatively, you might try dumping in a text-format and using rsync to
>> transfer changes.
>
> I really do'nt want to open separate port for backup only.
> Pelase, can you recomment a solution which uses port 5432 owned by Postgres
> ?
No.
You seem dead set on making your life harder than it needs to be. If you
really don't want to have the ssh port open then set the backup to run
from a cron-job on the main server and have it scp the result over to
the backup server. That way only the backup server needs ssh open.
>>> pg_read_file() can read only text files and is restricted only to
>>> superusers.
>>>
>>> How to add a function pg_read_backup() to Postgres which creates and
>>> returns backup file with download speed ?
>>> This problably requires implementing some file download protocol.
>> Just don't try and do it within PG - use the tools the system provides.
>
> How to force postmaster to run the tool which system provides when it
> receives backup request instead of postgres child process ?
Don't. You're just making life difficult for yourself. Use the standard
Unix solution for such things - ssh.
How are you installing updates without ssh access to the server?
--
Richard Huxton
Archonet Ltd
