Yes!
Thanks. It pointed me out to File system level backup. And there I
found a very important hint... you have to restore the whole database
cluster. I suppose this means that I have to transfer all databases in
my postgresql...
What is actually a pity because there is a db on the production site
that will be lost... well, I can backup this one without ptoblems and
reinsert it after.
Thanks again.
Javier.
On 8/16/06, Jeff Davis <[EMAIL PROTECTED]> wrote:
On Wed, 2006-08-16 at 20:04 +0200, Javier de la Torre wrote:
> I am working right now in an strategy to improve the performance on my
> server. The situation is this:
>
> I have a very large database that it is only update once a month, but
> when is updated I have to process a lot of things on the data to
> create caches, aditional tables, etc.
>
> The processing of the data can take up to 2 days in my machine so I
> was considering the following strategy.
>
> I have another machine that takes the new data, process it and when is
> done I replace the files from the production server with the ones of
> the processing server.
>
Start out here:
http://www.postgresql.org/docs/8.1/static/backup-online.html
You might also look into Slony-I:
http://www.slony.info
Do those seem like they will solve your problem?
Regards,
Jeff Davis
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
