Re: backup/restore buttons deactivated

From: John DeSoi <desoi(at)pgedit(dot)com>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, "Christian Sengstock" <csengstock(at)gmail(dot)com>, <pgadmin-support(at)postgresql(dot)org>, <openmacnews(at)gmail(dot)com>
Subject: Re: backup/restore buttons deactivated
Date: 2005-11-22 13:50:45
Message-ID: 01DE3A5C-EA87-4D39-A3C0-66A928EC183B@pgedit.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgadmin-support


On Nov 21, 2005, at 4:49 PM, Dave Page wrote:

> We always build against the absolute latest version of PostgreSQL -
> pg_dump is backwards compatible so it should always work. Of course,
> it's not beyond he realms of possibility that it might produce a dump
> that cannot be re-imported into an old version of PostgreSQL, but
> if you
> run into that situation, about all you can do is either upgrade, or
> replace pg_dump with an older version.

The effort may not be warranted here, but for my applications which
need PostgreSQL utilities I have 3 options:

1. built-in version included with the distribution (default)
2. whatever is found on the program path
3. the user can specify the PostgreSQL bin path to use

>
>
>> I think that I can find a way to copy pg_dump and pg_restore into the
>> bundle (during "make install"), but I'll be very busy the
>> next few days,
>> so it'll have to wait until the weekend.
>>
>
> OK, great - thanks.

Excellent, I think this is the best option.

John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Dave Page 2005-11-23 09:02:38 FW: Problems with PgAdmin 1.4
Previous Message Web2cad 2005-11-22 09:08:58 password storage error