Re: pgAdmin linking to the wrong pg_dump

From: "Cousin Florence" <fcousin(at)sopragroup(dot)com>
To: <pgadmin-support(at)postgresql(dot)org>
Cc: <rod(at)iol(dot)ie>, "Guillaume Lelarge" <guillaume(at)lelarge(dot)info>, "Dave Page" <dpage(at)pgadmin(dot)org>
Subject: Re: pgAdmin linking to the wrong pg_dump
Date: 2010-09-24 08:35:02
Message-ID: 5771_1285317304_4C9C62B8_5771_5104020_1_D02CE8BCC08BC6488B6A9DB54827C9F502ADE988@WBE12.ancy.fr.sopra
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

> -----Message d'origine-----
> De : pgadmin-support-owner(at)postgresql(dot)org
> [mailto:pgadmin-support-owner(at)postgresql(dot)org] De la part de Dave Page

> >> Hi there,
> >>
> >> Go to File -> Options, and on the "General" tab look for "PG bin
> >> path" - enter the correct path here.
> >>
> >
> > And, actually, there are no really good answers to this
> question. You
> > need a pg_dump release that goes along with the server release you
> > will use to restore your dump. I mean, if you want to dump
> a database
> > on a
> > 8.3 server and restore it on a 8.4, you need either a 8.3 or a 8.4
> > pg_dump (preferably a 8.4 one). Not a 9.0, not a <8.3. If you dump
> > with pgAdmin 1.12, you will have (by default) a 9.0 dump
> which you may
> > have problems to restore on the 8.4 server.
> >
> > Users have to know that pgAdmin's dump and restore facilities use
> > pg_dump and pg_restore of the last available PostgreSQL
> release by default.
>
> Except, that default is only used if there isn't an existing
> path in the config, set by a previous release of pgAdmin.

Thank you everybody for your explanations.

Florence Cousin

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Valentine Gogichashvili 2010-09-24 08:55:51 Re: Connection color is not correctly changed in query windows connection drop-down.
Previous Message Gianni 2010-09-24 05:32:11 Re: Issues with 1.12.0 (Mac OS X)