I use PostgreSQL now since about 10 years, a long time on SuSE-Linux, since about 2 years on CentOS, also on RedHat, NetBSD and Solaris, and I never had any problems with installation or initialization or documentation. Simply follow the few steps at the beginning of the INSTALL file included with the tarball: ./configure gmake su gmake install adduser postgres mkdir /usr/local/pgsql/data chown postgres /usr/local/pgsql/data su - postgres /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data /usr/local/pgsql/bin/postgres -D /usr/local/pgsql/data >logfile 2>&1 & /usr/local/pgsql/bin/createdb test /usr/local/pgsql/bin/psql test If you do not know, what these steps mean, it is better to go and learn something about the OS you are using. If the commands mentioned above are not available on Cpanel (whatever that really is... - some kind of shell-GUI?), go to the Cpanel documentation and look, what the equivalents for them is there. IMO it is nevertheless always better to use a real shell like csh or bash on a VServer instead of some limiting configuration tool. I you are using debs or rpms or whatever, you usually still have to create a superuser, whic is usually called "postgres", and to initialize the whole thing. If Cpanel cannot do this for you, don't blame PostgreSQL for the problems of Cpanel! Regards, Frank. On Wed, 24 Jan 2007 01:31:23 +0800 "Erick Papadakis" <erick.papa@xxxxxxxxx> thought long, then sat down and wrote: > > Correct. Also you will find nearly no stuff about using apt-get and rpm, > > which are some of the most used package systems on Linux on postgresql.org . > > And nothing about emerge, which is central to Gentoo Linux. And no real > > documentation to ports, which is prevalent on FreeBsd. > > > > PostgreSQL.org has extensive, detailed documentation of the PostgreSQL > > database. The ways the database is used or crunched by various installation > > tools is not covered. > > > > You are entitled to your perspectives, but for any self-respecting > software to get accepted by a decent-sized community, it is vital that > some of the main platforms are covered in the documentation in an easy > to understand manner. > > I am not speaking of exotic platforms like some obscure fork of POSIX > or something. I am speaking of Cpanel/WHM with Linux (CentOS in my > case) which must be hosted on hundreds of thousands of webservers > around the world. > > As such, it makes all the sense to make it a vital part of the docs, > especially if pgsql is going continue to be so lame in adcovating > itself to cpanels' makers and get itself included by default in the > WHM or Plesk interface. This ivory-tower "we don't bother because > we're so cool" spirit doesn't do anyone any good. > > And no, I disagree that the pgsql documentation is great. It is > extensive, sure, but is way too geekily presented. On Oracle or MySQL > online docs I can see a lot more of necessary information in a given > browser window space than on pgsql website. And they clearly tell me > through the navigation where I am, instead of useless crumbs on pgsql > site such as "Fast Backward" and "Fast Forward"--these dont tell me > anything--it would be much more useful to show me which section of the > humongous and geeky manual I am currently in. The PHP manual is a > fantastical layout to follow. > > My 0.02. Thanks anyway. > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend -- Frank Finner Invenius - Lösungen mit Linux Köpfchenstraße 36 57072 Siegen Telefon: 0271 231 8606 Mail: frank.finner@xxxxxxxxxxx Telefax: 0271 231 8608 Web: http://www.invenius.de Key fingerprint = 90DF FF40 582E 6D6B BADF 6E6A A74E 67E4 E788 2651
Attachment:
pgpMZEsQKfmEV.pgp
Description: PGP signature
