Re: Pains in upgrading to 8.3

From: Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com>
To:
Cc: Postgres General List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Pains in upgrading to 8.3
Date: 2008-02-15 20:49:26
Message-ID: 47B5FAD6.2030207@amsoftwaredesign.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Magnus Hagander wrote:
>
> For the case of upgrading, it wouldn't work. But there are certainly
> other cases where it would help. Say from your central pgadmin console
> administering 10 servers from 3 different major release trees :-(
>
> It can be done with commandline pg_dump, but it means you have to have
> three different installs on your management or backup or whatever
> machine. Those cases would certainly be easier if you could just call
> a backup API on the server that would feed you the data... (yes, there
> are ways to do it with ssh tunneling and whatever, but that's yet
> another external service that has to be set up and configured)
>
> I'm not saying it's worth the work and potential downsides, just that
> there are clear upsides :-)
>

Exactly, I didn't necessarily mean the blogger had a point about
upgrades in general, just that pg_dump had room for improvement.

Hey maybe a backup API is something for the Google Summer of Code thing,
it would be really nice to have, and make general backups much easier
from a admin point of view.

Later,

Tony

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Anton Andreev 2008-02-15 20:56:53 returning a resultset from a function
Previous Message Alvaro Herrera 2008-02-15 20:12:14 Re: PG quitting sporadically!!