Обсуждение: Compilation probl with Postgres 7.3.1
7.3.1 's pgNotify structure has no member extra, is there a way to compile and of course use pgadmin with PostgreSQL 7.x or do I have to upgrade to 8.x ? I was trying to compile 1.4.1. regards Gerhard -- Gerhard Hintermayer
> -----Original Message----- > From: pgadmin-support-owner@postgresql.org > [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of > Gerhard Hintermayer > Sent: 15 December 2005 12:37 > To: pgadmin-support@postgresql.org > Subject: [pgadmin-support] Compilation probl with Postgres 7.3.1 > > 7.3.1 's pgNotify structure has no member extra, is there a > way to compile > and of course use pgadmin with PostgreSQL 7.x or do I have to > upgrade to > 8.x ? I was trying to compile 1.4.1. You will need to compile against a newer PostgreSQL, but the resulting pgAdmin can be used to manage a 7.3 server. Regards, Dave
Dave Page wrote: > > > > >>-----Original Message----- >>From: pgadmin-support-owner@postgresql.org >>[mailto:pgadmin-support-owner@postgresql.org] On Behalf Of >>Gerhard Hintermayer >>Sent: 15 December 2005 12:37 >>To: pgadmin-support@postgresql.org >>Subject: [pgadmin-support] Compilation probl with Postgres 7.3.1 >> >>7.3.1 's pgNotify structure has no member extra, is there a >>way to compile >>and of course use pgadmin with PostgreSQL 7.x or do I have to >>upgrade to >>8.x ? I was trying to compile 1.4.1. >> >> > >You will need to compile against a newer PostgreSQL, but the resulting >pgAdmin can be used to manage a 7.3 server. > >Regards, Dave > > > > Thanks. So I have to live with a) having both 7.x and 8.x libs/includes hang around and b) "unsupported frontend protocol" errors in the database logfile (thats at least what I get when I connect with the 8.x psql version. right ?
> -----Original Message----- > From: Gerhard Hintermayer [mailto:g.hintermayer@inode.at] > Sent: 15 December 2005 12:59 > To: Dave Page; pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] Compilation probl with Postgres 7.3.1 > > So I have to live with > a) having both 7.x and 8.x libs/includes hang around > and Not if you build with --enable-static. > b) "unsupported frontend protocol" errors in the database > logfile (thats > at least what I get when I connect with the 8.x psql version. Yes. Regards, Dave.
Dave Page wrote: > > > >>-----Original Message----- >>From: Gerhard Hintermayer [mailto:g.hintermayer@inode.at] >>Sent: 15 December 2005 12:59 >>To: Dave Page; pgadmin-support@postgresql.org >>Subject: Re: [pgadmin-support] Compilation probl with Postgres 7.3.1 >> >>So I have to live with >>a) having both 7.x and 8.x libs/includes hang around >>and > > > Not if you build with --enable-static. > > >>b) "unsupported frontend protocol" errors in the database >>logfile (thats >>at least what I get when I connect with the 8.x psql version. > > > Yes. How about updating to something less outdated... Patch versions are at 7.3.12 already, for good reasons, and upgrading to 8.1 isn't a very bad idea either. Regards, Andreas
> Dave Page wrote: >> >> >> >>>-----Original Message----- >>>From: Gerhard Hintermayer [mailto:g.hintermayer@inode.at] >>>Sent: 15 December 2005 12:59 >>>To: Dave Page; pgadmin-support@postgresql.org >>>Subject: Re: [pgadmin-support] Compilation probl with Postgres 7.3.1 >>> >>>So I have to live with >>>a) having both 7.x and 8.x libs/includes hang around >>>and >> >> >> Not if you build with --enable-static. >> >> >>>b) "unsupported frontend protocol" errors in the database >>>logfile (thats >>>at least what I get when I connect with the 8.x psql version. >> >> >> Yes. > > How about updating to something less outdated... > Patch versions are at 7.3.12 already, for good reasons, and upgrading to > 8.1 isn't a very bad idea either. > 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) PS: please don't send to both mailing list and directly, so I get every mail twice :-( -- Gerhard Hintermayer mailto:g.hintermayer@inode.at
> -----Original Message----- > From: pgadmin-support-owner@postgresql.org > [mailto:pgadmin-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.
Dave Page wrote: > > > >>-----Original Message----- >>From: pgadmin-support-owner@postgresql.org >>[mailto:pgadmin-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
Andreas Pflug wrote: > Dave Page wrote: > >> >> >> >>> -----Original Message----- >>> From: pgadmin-support-owner@postgresql.org >>> [mailto:pgadmin-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