> -----Original Message-----
> From: Florian G. Pflug [mailto:fgp@phlo.org]
> Sent: 21 November 2005 19:25
> To: Dave Page
> Cc: John DeSoi; Andreas Pflug; Christian Sengstock;
> pgadmin-support@postgresql.org; openmacnews@gmail.com
> Subject: Re: [pgadmin-support] backup/restore buttons deactivated
>
> Dave Page wrote:
> > Thanks for the link. We do already have a plist file - the
> only sensible
> > option I can think of is to add /usr/local/pgsql/bin (and
> whereever the
> > dports version installs if it's different) to the path in
> it and hope
> > the user installs PostgreSQL there. We can always include a
> note in the
> > docs explaining how to adjust it if required.
> >
> > Unless anyone has a better idea? Florian or Richard perhaps?
> This code in appbase.cpp
> -------------------------
> #if defined(__WXMAC__)
>
> //When using wxStandardPaths on OSX, wx defaults to the unix,
> //not to the mac variants. Therefor, we request wxStandardPathsCF
> //directly.
> wxStandardPathsCF stdPaths ;
> dataDir = stdPaths.GetDataDir() ;
>
> if (wxDir::Exists(dataDir + HELPER_DIR))
> path.Add(dataDir + HELPER_DIR) ;
> if (wxDir::Exists(dataDir + SCRIPT_DIR))
> path.Add(dataDir + SCRIPT_DIR) ;
>
> #else // other *ixes
> --------------------------
>
> adds $bundledir/Contents/SharedSupport/helper to the path used by
> pgadmin3. I think pgadmin3 should copy pg_dump and pg_restore into
> that dir during "make install" - I remember trying to do that a while
> ago, but couldn't find a reliable way to find the pg_dump and
> pg_restore
> while doing "make install". But since pgadmin3 now uses pg_config, I
> guess the path to pg_dump and pg_restore could be queried
> from pg_config.
>
> Another problem is that this won't guarantee that the version
> of pg_dump
> and pg_restore matches the version of the database which pg_dump and
> pg_restore are trying to backup/restore - but that's a more general
> problem - how does it work on windows, btw?

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.

> 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.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

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


---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend