changing major/minor on libpq for releases ...
Just curious, but how do ppl handle running two different versions on the
same machine? I want to start up a v6.5 server where v6.4.2 server
already exists...
I'm wondering if it might make sense to up the libpq on a release, so that
this can work?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
The Hermit Hacker <scrappy@hub.org> writes:
Just curious, but how do ppl handle running two different versions on the
same machine? I want to start up a v6.5 server where v6.4.2 server
already exists...
Run them with different port addresses. I do it all the time...
I'm wondering if it might make sense to up the libpq on a release, so that
this can work?
No, I don't think that's a good idea. There's no reason to break binary
compatibility of libpq when setting PGPORT will do the job; the same
psql binary (or any other application) can talk to either release.
regards, tom lane
Import Notes
Reply to msg id not found: YourmessageofTue29Jun1999175518-0300Pine.BSF.4.05.9906291754050.49155-100000@thelab.hub.org | Resolved by subject fallback
Normally I just set up a specially designated user and set all of his
environment variable accordingly.
I don't use the Perl interface or any interface that requires compiling as
root.
I can see those being a real problem without libpq versioning.
-DEJ
Show quoted text
-----Original Message-----
From: The Hermit Hacker [SMTP:scrappy@hub.org]
Sent: Tuesday, June 29, 1999 3:55 PM
To: pgsql-hackers@postgreSQL.org
Subject: [HACKERS] changing major/minor on libpq for releases ...Just curious, but how do ppl handle running two different versions on the
same machine? I want to start up a v6.5 server where v6.4.2 server
already exists...I'm wondering if it might make sense to up the libpq on a release, so that
this can work?Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary:
scrappy@{freebsd|postgresql}.org
Import Notes
Resolved by subject fallback
On Tue, 29 Jun 1999, Jackson, DeJuan wrote:
Normally I just set up a specially designated user and set all of his
environment variable accordingly.
I don't use the Perl interface or any interface that requires compiling as
root.
I can see those being a real problem without libpq versioning.
That's the problem taht I have...all my stuff is in perl, but I only want
to move things over one by one...
Oh well, bite the bullet and move them all, ig uess :)
-DEJ
-----Original Message-----
From: The Hermit Hacker [SMTP:scrappy@hub.org]
Sent: Tuesday, June 29, 1999 3:55 PM
To: pgsql-hackers@postgreSQL.org
Subject: [HACKERS] changing major/minor on libpq for releases ...Just curious, but how do ppl handle running two different versions on the
same machine? I want to start up a v6.5 server where v6.4.2 server
already exists...I'm wondering if it might make sense to up the libpq on a release, so that
this can work?Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary:
scrappy@{freebsd|postgresql}.org
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org