From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Andrus <eetasoft(at)online(dot)ee> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to implement backup protocol |
Date: | 2006-11-28 18:03:26 |
Message-ID: | 1164737006.7773.105.camel@dogma.v10.wvs |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 2006-11-28 at 19:34 +0200, Andrus wrote:
> > You could use an *un*trusted procedural language to create a
> > function to binary-read the backup from disk and return it
> > as a bytea field. Not sure how efficient that is, though.
> >
> > You could then simply do
> >
> > select get_backup();
> >
> > If you allow for parameters you could make it return certain
> > backups based on, perhaps, timestamp of creation.
>
>
> Karsten,
>
> This id good idea but it forces to use Postgres protocol for downloading.
> This protocol has some timeouts which are too small for large file download.
> Postgres protocol has also a lot of overhead added to downloadable data.
> It also requires that whole downloadable file must fit into memory.
You could backup to a postgresql large object, and then transmit that.
Would that be more efficient? It would be kind of strange, but it might
work if you can't open any other ports.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2006-11-28 18:23:35 | Re: How to implement backup protocol |
Previous Message | novnov | 2006-11-28 18:01:06 | Re: Editing contrib modules which are loaded by default? |