Atomicorp

Posted: **Thu Nov 10, 2005 11:00 pm**

Are there any PGSQL 8 rpms available yet? If so, are they compatible with the plesk interface?

Posted: **Fri Nov 11, 2005 8:40 am**

I havent really done anything with postgres (you're the first person to ask in 3 years!), but it shouldn't have any effect on PSA. Unlike with mysql, psa doesn't use postgres at all for anything internal, so updating it would probably be pretty easy. I'll add it to my list.

Posted: **Sun Nov 13, 2005 4:17 pm**

Thanks for the reply Scott.

I found the RHEL 3.0 RPMS on the PGSQL site:

http://www.postgresql.org/ftp/binary/v8 ... el-es-3.0/

I tried to install it and I get these dep issues:

error: Failed dependencies:
libpq.so.3 is needed by (installed) perl-DBD-Pg-1.21-2
libpq.so.3 is needed by (installed) php-pgsql-4.3.11-8.rhel3.art

Do you know the best way to resolve this?

Posted: **Sun Nov 13, 2005 4:38 pm**

Yep, thats telling you that upgrading to postgres 8.0 will break the perl postgres connector (DBD) and the php postgres module. You'll either have to rebuild perl-DBD-Pg and php or create/find a compatibility rpm that includes the older libraries for those applications.

Posted: **Mon Nov 14, 2005 3:44 am**

I take it your newest php rpms doesn't include a newer version?

I'm a little precautious when it comes to php, thats a show stopper!

Posted: **Mon Nov 14, 2005 10:38 am**

No its linked against whatever the default is for the OS, otherwise everyone would have to upgrade postgres to use a newer version of php. I do the same thing with mysql, I link against the vendor default.

Posted: **Tue Nov 15, 2005 12:13 am**

I suppose I could make php from the source. I hate doing that, but if I have to I will. I guess now would be a good time to upgrade to 5.0

Posted: **Fri Nov 18, 2005 3:11 pm**

Scott,

Do you know of any compatibility RPMS that might contain this older library? Or should I just install PGSQL from the source? I really want to get this upgrade taken care of without breaking PHP.

Got any suggestions?

Posted: **Fri Nov 18, 2005 3:27 pm**

Ok, I found the compat RPM that I needed.

http://www.gunduz.org/postgresql/rpms/c ... G.i686.rpm

I installed the RPMS, but here's what happened:

warning: compat-postgresql-libs-3-2PGDG.i686.rpm: V3 DSA signature: NOKEY, key ID 748f7d0e
Preparing... ########################################### [100%]
1:postgresql-libs ########################################### [ 9%]
2:postgresql ########################################### [ 18%]
3:compat-postgresql-libs ########################################### [ 27%]
4:postgresql-server ########################################### [ 36%]
/sbin/ldconfig: /usr/lib/libpgtypes.so.1 is not a symbolic link

/sbin/ldconfig: /usr/lib/libecpg_compat.so.1 is not a symbolic link

/sbin/ldconfig: /usr/lib/libecpg.so.4 is not a symbolic link

/sbin/ldconfig: /usr/lib/libpq.so.3 is not a symbolic link

5:postgresql-contrib ########################################### [ 45%]
6:postgresql-devel ########################################### [ 55%]
7:postgresql-docs ########################################### [ 64%]
8:postgresql-jdbc ########################################### [ 73%]
9:postgresql-pl ########################################### [ 82%]
/sbin/ldconfig: /usr/lib/libpgtypes.so.1 is not a symbolic link

/sbin/ldconfig: /usr/lib/libecpg_compat.so.1 is not a symbolic link

/sbin/ldconfig: /usr/lib/libecpg.so.4 is not a symbolic link

/sbin/ldconfig: /usr/lib/libpq.so.3 is not a symbolic link

10:postgresql-python ########################################### [ 91%]
11:postgresql-test ########################################### [100%]
/sbin/ldconfig: /usr/lib/libpgtypes.so.1 is not a symbolic link

/sbin/ldconfig: /usr/lib/libecpg_compat.so.1 is not a symbolic link

/sbin/ldconfig: /usr/lib/libecpg.so.4 is not a symbolic link

/sbin/ldconfig: /usr/lib/libpq.so.3 is not a symbolic link

/sbin/ldconfig: /usr/lib/libpgtypes.so.1 is not a symbolic link

/sbin/ldconfig: /usr/lib/libecpg_compat.so.1 is not a symbolic link

/sbin/ldconfig: /usr/lib/libecpg.so.4 is not a symbolic link

/sbin/ldconfig: /usr/lib/libpq.so.3 is not a symbolic link

Now, inside Plesk, it says that PGSQL is not installed and has removed the ability to create PGSQL databases from my control panel.

From root, when i type postgres --version, it returns:

postgres (PostgreSQL) 8.1.0

When I try to run it from the command line I get:

postgres does not know where to find the server configuration file.
You must specify the --config-file or -D invocation option or set the PGDATA environment variable.

So I'm not sure if the server got installed ok or if it's just not syncing with my Plesk control panel.

Can someone help me resolve this?

Posted: **Fri Nov 18, 2005 3:39 pm**

Ive never looked into the way that one is put together to be honest, I suspect that its in a trigger or something. Maybe ask the folks at sw-soft?

Posted: **Fri Nov 18, 2005 3:41 pm**

I'll give it a shot. I hope i didn't break anything.

One thought. From the control panel, i can run the Plesk updater and it gives me the option to install "PosgreSQL server support". Is this just the interface from Plesk into PGSQL? If so, do you think if I re-install this from the control panel it will plug itself back in?

Posted: **Fri Nov 18, 2005 4:37 pm**

After all this, I get a response back from Plesk. Here is what they say:

Unfortunately Plesk does not work with PostgreSQL 8.x.
Plesk can work with PostgreSQL 7.x only. PgSQL 8.x has different paths to configuration files, different name of
start script, so it has difeerent infrastructure than PgSQL 7.x. That's why Plesk is not able to manage PgSQL 8.x.

Also some keys of PgSQL utilities were change. For example 'createuser' utility:

# createuser --help
createuser creates a new PostgreSQL user.

Usage:
createuser [OPTION]... [USERNAME]

Options:
-a, --adduser user can add new users
-A, --no-adduser user cannot add new users
-d, --createdb user can create new databases
-D, --no-createdb user cannot create databases
-P, --pwprompt assign a password to new user
-E, --encrypted encrypt stored password
-N, --unencrypted do no encrypt stored password
-i, --sysid=SYSID select sysid for new user
-e, --echo show the commands being sent to the server
-q, --quiet don't write any messages
--help show this help, then exit
--version output version information, then exit

for PgSQL 7.4.3
and

$createuser --help
createuser creates a new PostgreSQL role.

Usage:
createuser [OPTION]... [USERNAME]

Options:
-s, --superuser role will be superuser
-S, --no-superuser role will not be superuser
-d, --createdb role can create new databases
-D, --no-createdb role cannot create databases
-r, --createrole role can create new roles
-R, --no-createrole role cannot create roles
-l, --login role can login (default)
-L, --no-login role cannot login
-i, --inherit role inherits privileges of roles it is a
member of (default)
-I, --no-inherit role does not inherit privileges
-c, --connection-limit=N connection limit for role (default: no limit)
-P, --pwprompt assign a password to new role
-E, --encrypted ??????????? ??????????? ??????
-N, --unencrypted ?? ????????? ??????????? ??????
-e, --echo ?????????? ??????? ???????????? ???????
-q, --quiet ?? ???????? ??????? ?????????
--help ???????? ??? ??????? ? ?????
--version ???????? ?????? ? ?????

for PgSQL 8.1

PosgreSQL hasn't 'user' objects but it has 'role' objects. Also there are a lot of other changes from PgSQL 7.x to 8.x.

Anyway even if you are able to glue PgSQL 8.1 with Plesk we cannot guarantee fine work due to we have never tested PgSQL 8.1 with Plesk environment.

Feel free to contact us if something is unclear there or if you have any questions.

Thanks,
______________________________
Damir R. Islamov
Technical Support Engineer
SWsoft, Inc.

How can this be true? From the Plesk website:

Additional features in Plesk 7.5.4:

* Subdomains with ‘.’ in names
* Several new command line interface utilities
* Coldfusion 7 support
* API to change hostname
* Extended server-wide disk usage information
* Ability to create multi-volume backups
* Improved domain usage statistics
* Additional archive types for Domain Skeletons
* PostgreSQL 8 support
* Now you can install Site Applications in the Document Root of your domain

Posted: **Fri Nov 18, 2005 10:43 pm**

Id ask

I rarely ever play with postgres so I don't think I'd be much help here.

Posted: **Sat Nov 19, 2005 11:57 am**

At least I can say that plesk support has been rather responsive to my issue. That's a big plus.

However, I'm still stuck with this issue. They did confirm that the 8.0 branch is compatible with plesk but the 8.1 branch is NOT.

I reverted back to 7.3 and got that working. Then I tried to re-upgrade to 8.0.4 and it still doesn't work. I get:

Unable to make action: Unable to manage service by pg_manage: Unable to start PostgreSQL. 1
0: /usr/local/psa/admin/htdocs/server/restart_services.php:28 psaerror(string "Unable to make action: Unable to manage service by pg_manage: Unable to start PostgreSQL. 1")

So, I'll let you know if I make any progress, but right now the outlook isn't good.

Thanks again.

Posted: **Sat Nov 19, 2005 12:02 pm**

Thanks for the update, at least we can get it up to 8.0. Do you know what the major changes from 8 to 8.1?

Atomicorp

PostgreSQL v8.0?

PostgreSQL v8.0?