From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Keith" <keithcelt(at)yahoo(dot)com>, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
Cc: | <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Error on pgAdminIII 1.2.2 and 1.4.0 |
Date: | 2005-10-24 13:12:43 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC3696@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: pgadmin-support-owner(at)postgresql(dot)org
> [mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of Keith
> Sent: 24 October 2005 13:51
> To: Andreas Pflug
> Cc: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] Error on pgAdminIII 1.2.2 and 1.4.0
>
> Hi Andreas,
>
> Your tip about a namespace did the trick. I had
> renamed the "public" schema which had caused all of my
> problems. I do not understand why.
pgAdmin expects pg_postmaster_starttime() to be in the public schema,
and an error occurs when it cannot find it there. Iirc, in 8.1
everything lives in pg_catalog so this shouldn't happen if you
drop/rename public on that version.
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2005-10-24 13:23:15 | Re: pgAdmin III 1.2.2 edit grid crashes with single-column |
Previous Message | Dave Page | 2005-10-24 13:10:20 | Re: Backup problem |