> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailtogadmin-support-owner@postgresql.org] On Behalf Of
> Gerhard Hintermayer
> Sent: 15 December 2005 15:27
> To: pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] Compilation probl with Postgres 7.3.1
>
>
> Upgrading to 7.3.12 won't solve the "unsupported frontend
> protocol", and
> the members for pgNotify are the same as in 7.3.1 :-(
> I'd really like to upgrade, but unfortunately the DB-server
> is running at
> least 6*24, so ther's not a lot time to upgrade and test all involved
> applications (which are quite a lot)

I think what he means is that the .12 is a good indicator of how old the
version is.

> PS: please don't send to both mailing list and directly, so I
> get every
> mail twice :-(

That's the convention on all the postgresql.org lists, though you
shouldn't get multiple copies normally unless you've subscirbe with a
couple of addresses.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Dave Page wrote:
>
>
>
>>-----Original Message-----
>>From: pgadmin-support-owner@postgresql.org
>>[mailtogadmin-support-owner@postgresql.org] On Behalf Of
>>Gerhard Hintermayer
>>Sent: 15 December 2005 15:27
>>To: pgadmin-support@postgresql.org
>>Subject: Re: [pgadmin-support] Compilation probl with Postgres 7.3.1
>>
>>
>>Upgrading to 7.3.12 won't solve the "unsupported frontend
>>protocol", and
>>the members for pgNotify are the same as in 7.3.1 :-(
>>I'd really like to upgrade, but unfortunately the DB-server
>>is running at
>>least 6*24, so ther's not a lot time to upgrade and test all involved
>>applications (which are quite a lot)
>
>
> I think what he means is that the .12 is a good indicator of how old the
> version is.

Upgrading to 7.3.12 should be a simple make; make install; stop and
restart server. To perform a smooth update, you could consider using
Slony-I to have an up-to-date replication. This would allow you to
switch over virtually seamlessly (if your current machine is big enough,
I doubt it when looking at your pgsql version, could be even on the same
box).

>>PS: please don't send to both mailing list and directly, so I
>>get every mail twice :-(

> That's the convention on all the postgresql.org lists, though you
> shouldn't get multiple copies normally unless you've subscirbe with a
> couple of addresses.

Yeah, to be sure that *you* get the answer, and all people interested
(and for archive's sake) see it too.

Regards,
Andreas

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Andreas Pflug wrote:

> Dave Page wrote:
>
>>
>>
>>
>>> -----Original Message-----
>>> From: pgadmin-support-owner@postgresql.org
>>> [mailtogadmin-support-owner@postgresql.org] On Behalf Of Gerhard
>>> Hintermayer
>>> Sent: 15 December 2005 15:27
>>> To: pgadmin-support@postgresql.org
>>> Subject: Re: [pgadmin-support] Compilation probl with Postgres 7.3.1
>>>
>>>
>>> Upgrading to 7.3.12 won't solve the "unsupported frontend protocol",
>>> and
>>> the members for pgNotify are the same as in 7.3.1 :-(
>>> I'd really like to upgrade, but unfortunately the DB-server is
>>> running at
>>> least 6*24, so ther's not a lot time to upgrade and test all involved
>>> applications (which are quite a lot)
>>
>>
>>
>> I think what he means is that the .12 is a good indicator of how old the
>> version is.
>
>
> Upgrading to 7.3.12 should be a simple make; make install; stop and
> restart server. To perform a smooth update, you could consider using
> Slony-I to have an up-to-date replication. This would allow you to
> switch over virtually seamlessly (if your current machine is big
> enough, I doubt it when looking at your pgsql version, could be even
> on the same box).
>
As I wrote above. An upgrade to 7.3.12 neither solves the "unsupported
frontend protocol" nor the compilation problem, the structure pgNotify
is exactly the same as in 7.3.1.
I think there are still a lot of 7.3.* versions out there, and they all
have to suffer from that problems.

regards
Gerhard



---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq