Installing PostgreSQL under Cpanel

There are a couple of PostgreSQL tutorials around the web. I have
followed them. Downloaded the *.rpm files and installed them. Then gone
into my WHM (https://myserver:2087) and enabled the config, and set up
the postgres user with an "su" command "adduser postgres".

Now what?

1. Where's the interactive shell?

2. How do I start the service? How should I set it up to restart
automatically if (a) the service fails (b) machine reboots?

3. How can I start creating a database, creating users, testing things
out?

I looked at the Documentation
(http://www.postgresql.org/docs/8.2/interactive/config-setting.html)
and could not find one intuitive instruction to actually get cracking
with PostgreSQL without getting all configgy.

I'd appreciate some pointers.

Thanks!

There are a couple of PostgreSQL tutorials around the web to make it
work with WHM.

I have followed them. Downloaded the *.rpm files and installed them.
Then gone
into my WHM (https://myserver:2087) and enabled the config, and set up
the postgres user with an "su" command "adduser postgres".

Now what?

1. Where's the interactive shell? How can I start creating a database,
creating users, testing things out?

2. How do I start the service? How should I set it up to restart
automatically if (a) the service fails (b) machine reboots?

I looked at the Documentation
(http://www.postgresql.org/docs/8.2/interactive/config-setting.html)
and could not find one intuitive instruction to actually get cracking
with PostgreSQL without getting all configgy.

I'd appreciate some pointers.

Thanks!

On 23.01.2007 15:10 erick(dot)papa(at)gmail(dot)com wrote:
> Now what?
>
>
> 1. Where's the interactive shell?
http://www.postgresql.org/docs/8.2/static/app-psql.html

> How can I start creating a database,
http://www.postgresql.org/docs/8.2/static/app-createdb.html

> creating users, testing things out?
http://www.postgresql.org/docs/8.2/static/app-createuser.html

Thanks Thomas.

But:

- "psql" at the command says
> psql: FATAL: database "root" does not exist

- "psql -d postgres" at the command says
> psql: FATAL: role "root" does not exist

How should I create the first database, or the first user etc? The
links you suggested are all *after* I login to the interface?

How should I start the postgresql service? How should I check it is on?

Thanks

On 1/23/07, Thomas Kellerer <spam_eater(at)gmx(dot)net> wrote:
> On 23.01.2007 15:10 erick(dot)papa(at)gmail(dot)com wrote:
> > Now what?
> >
> >
> > 1. Where's the interactive shell?
> http://www.postgresql.org/docs/8.2/static/app-psql.html
>
> > How can I start creating a database,
> http://www.postgresql.org/docs/8.2/static/app-createdb.html
>
> > creating users, testing things out?
> http://www.postgresql.org/docs/8.2/static/app-createuser.html
>

Erick,

psql -U postgres

should help.

I hope you remembered the password you gave to the database superuser while
installing...

best wishes,

Harald

--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstraße 202b
70197 Stuttgart
0173/9409607
fx 01212-5-13695179
-
Python: the only language with more web frameworks than keywords.

Erick Papadakis wrote:
> Thanks Thomas.

Please don't top-post, it disturbes the flow of the communication.

> But:
>
> - "psql" at the command says
> > psql: FATAL: database "root" does not exist
>
> - "psql -d postgres" at the command says
> > psql: FATAL: role "root" does not exist
>
> How should I create the first database, or the first user etc? The
> links you suggested are all *after* I login to the interface?

There's documentation about that too, at the end of the installation
instructions IIRC.

> How should I start the postgresql service? How should I check it is on?

This suggests you're using PostgreSQL on Windows. I don't know anything
about Windows (except that it's suitable for games :P), so can't help
you with that. However, I can solve one of your other problems:

Windows doesn't really have a native "interactive shell"; I suppose
cmd.exe is the closest thing. I suppose that's what you were looking for
when you were told to use psql - which wasn't the correct answer in that
case.

> Thanks
>
>
> On 1/23/07, Thomas Kellerer <spam_eater(at)gmx(dot)net> wrote:
>> On 23.01.2007 15:10 erick(dot)papa(at)gmail(dot)com wrote:
>> > Now what?
>> >
>> >
>> > 1. Where's the interactive shell?
>> http://www.postgresql.org/docs/8.2/static/app-psql.html

I think this has caused some confusion. Although psql is an interactive
shell, it is a shell to the database - not to the OS. I think the OP's
question refered to interactive shells to the OS.

This isn't the first time for this question to rise. Apparently some
documentation refers to the term without explaining what it is (which
would indeed be quite unnecessary for UNIX users). Maybe a documentation
patch is in order?

>> > How can I start creating a database,
>> http://www.postgresql.org/docs/8.2/static/app-createdb.html

createdb is a command line utility, that you can start from your
"interactive shell". Using cmd.exe, you probably need to set your PATH
to where createdb.exe(?) and createuser.exe(?) were installed.

>> > creating users, testing things out?
>> http://www.postgresql.org/docs/8.2/static/app-createuser.html

See above.

--
Alban Hertroys
alban(at)magproductions(dot)nl

magproductions b.v.

T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede

// Integrate Your World //

Doesn't work:

- psql -U postgres
> psql: FATAL: Ident authentication failed for user "postgres"

- psql -U postgres -W
> psql: FATAL: Ident authentication failed for user "postgres"

Would appreciate some insights. Where's the step by step guide to make
this work? Cpanel/WHM and Plesk are THE most widespread control
panels, and I see zilch on postgresql.org that addresses them.

Maybe this is why MySQL is popular. The thing just works! (Which is
all one needs in 99% of simple webbie cases).

Thanks in advance!

On 1/23/07, Harald Armin Massa <haraldarminmassa(at)gmail(dot)com> wrote:
> Erick,
>
> psql -U postgres
>
> should help.
>
> I hope you remembered the password you gave to the database superuser while
> installing...
>

> Please don't top-post, it disturbes the flow of the communication.

Interesting. I prefer getting to the point an author is making.

> There's documentation about that too, at the end of the installation
> instructions IIRC.

I did not see them. Please point me? I'd deeply appreciate it.

> This suggests you're using PostgreSQL on Windows. I don't know anything
> about Windows (except that it's suitable for games :P), so can't help
> you with that. However, I can solve one of your other problems:

No, I am using *the most popular* setup on the web these days, which
is almost the norm in hosting environments these days -- CentOS 4.4,
with Cpanel/WHM.

Erick

Erick Papadakis schrieb:
> Doesn't work:
>
> - psql -U postgres
> > psql: FATAL: Ident authentication failed for user "postgres"
>
> - psql -U postgres -W
> > psql: FATAL: Ident authentication failed for user "postgres"
>
>
> Would appreciate some insights. Where's the step by step guide to make
> this work? Cpanel/WHM and Plesk are THE most widespread control
> panels, and I see zilch on postgresql.org that addresses them.
>
> Maybe this is why MySQL is popular. The thing just works! (Which is
> all one needs in 99% of simple webbie cases).
>
> Thanks in advance!

Well looks like Plesk and stuff would handle this incorrect and are to
be blamed for this. This is not the business of postgresql to fix
broken deployment applications they dont own.

If they would handle mySQL the same way it woulndt work either.

Regards
Tino

"Erick Papadakis" <erick(dot)papa(at)gmail(dot)com> writes:
> Doesn't work:
> - psql -U postgres
>>>> psql: FATAL: Ident authentication failed for user "postgres"

su to postgres, then psql will let you in. Or you can RTFM about
changing the default authentication method ...

regards, tom lane

On 1/23/07, Erick Papadakis <erick(dot)papa(at)gmail(dot)com> wrote:
> Doesn't work:
>
> - psql -U postgres
> > psql: FATAL: Ident authentication failed for user "postgres"
>
> - psql -U postgres -W
> > psql: FATAL: Ident authentication failed for user "postgres"

that is saying you need to have the password to login to the database.
edit pg_hba.conf and change where it says 'ident' on the 127.0.0.1
line to 'trust'. (wihtout quotes).

> Would appreciate some insights. Where's the step by step guide to make
> this work? Cpanel/WHM and Plesk are THE most widespread control
> panels, and I see zilch on postgresql.org that addresses them.

> Maybe this is why MySQL is popular. The thing just works! (Which is
> all one needs in 99% of simple webbie cases).

no, you just don't know what you are doing. installing mysql and
postgresql from source require approximately the same number of steps
(actually, pg is IMO easier). Binary installations are going to
require different steps depending on the packaging. haven't checked,
but if IIRC redhat provided sys v init scripts can do most of the hard
work for you:

service postgresql start

it will bootstrap (initdb) the database cluster, etc. with suitable defaults.

merlin

Erick,

- psql -U postgres
> > psql: FATAL: Ident authentication failed for user "postgres"

Nice. This gives us some more information about what kind of client
authorization is configured by cpanel.

You can read everything about client-autorisation on:

http://www.postgresql.org/docs/8.2/interactive/client-authentication.html

It looks as if cpanel has configured your pg_hba.conf for ident based
authorization, please read the appropriate chapter.

Would appreciate some insights. Where's the step by step guide to make
> this work? Cpanel/WHM and Plesk are THE most widespread control
> panels, and I see zilch on postgresql.org that addresses them.

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. That's sad, but the way it is; and you can help to
improve it: after you learned the hard way how to make cpanel do what you
want, document your steps and send it to the list.

Thanks for trying PostgreSQL,

Harald

--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstraße 202b
70197 Stuttgart
0173/9409607
fx 01212-5-13695179
-
Python: the only language with more web frameworks than keywords.

Where is pg_hba.conf?

I tried find and whereis commands, but could not find it.

Thanks for any pointers.

pg_hba.conf is within the PostgreSQL data directory.

That directory can be put everywhere by the installation routine.

usual places:
- on windows per default below \programme\postgresql\8.2\data
- within linux often below /var

I tried find and whereis commands, but could not find it.

Either your search command was wrong; or you do not have access to that
directory. (second one is very unlikely as root)

best wishes,

Harald

--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstraße 202b
70197 Stuttgart
0173/9409607
fx 01212-5-13695179
-
Python: the only language with more web frameworks than keywords.

> 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.

Erick Papadakis schrieb:
>> 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.

This may or may not be the case. However typical distributions of
postgres add distribution specific documentation - and I'm thinking
thats the way it should work. Postgres community cannot really superwise
all these distributions to update documentation on the main project
site. For an example debian adds a README.debian to the docs at the
usual places and also offers howtos on main project page. Your
Cpanel should do similar and if not, it should be fixed there.

What we could do is to link to current documentation on these
distribution project places from postgres main site/documentation
as "if you are using foo, please look here for additional information"

Btw, the ident problem is pretty standard and you should easily find
it covered in the FAQ anyway.

> 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

My impression of these "documentation" is completely different. I find
the oracle documentation pretty useless as it is. You always need
additional resources to find your way thru it.

> 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.

Feel free to contribute doc patches - I think this is all solvable
and in the end we would have a documentation most people are happy with.

Regards
Tino

On Wed, Jan 24, 2007 at 01:31:23AM +0800, Erick Papadakis wrote:
> 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.

Setting aside the fact that I don't even know what Cpanel is, I'm not
sure how this is practical. How many versions of Cpanel are there and
which versions of postgres do they ship? If Cpanel releases a new
version, do the postgresql docs needs to be updated?

The only people who can provide the documentation with any reasonable
accuracy are the makers of Cpanel themselves. And since they evidently
don't do it I'm not sure why we should do it for them.

For example, Debian has a README.Debian file with every package that
describes any special steps needed to get the lackage working. That's
the way it should be.

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

On 1/23/07, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
> On Wed, Jan 24, 2007 at 01:31:23AM +0800, Erick Papadakis wrote:
> > 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.
>
> Setting aside the fact that I don't even know what Cpanel is, I'm not

I think it's some sort of serum they inject into semi-skilled i.t.
workers that makes them arrogant and spout off random poorly
constructed off topic posts on professional mailing lists while asking
for help in the same breath. Fortunately, I never went to college and
missed my shot.

merlin

[p.s. view sure is great from the ivory tower!]

> Setting aside the fact that I don't even know what Cpanel is, I'm not
> sure how this is practical. How many versions of Cpanel are there and
> which versions of postgres do they ship? If Cpanel releases a new
> version, do the postgresql docs needs to be updated?

Cpanel team takes care of all of this. All it takes is for someone
like pgsql to wake up, smell the coffee, and get over the ignorance
about a platform that is the most prevalent in the web hosting world.
Cpanel is used by millions of users. I'll be surprised if Debian is.

MySQL has cracked this model. It sucks rocks as a database, but its
team knows how to market itself, which makes a world of difference.
(To end-users too, who thus become advocates, like for PHP).

Debian is an OS distro. The equivalent in my case is CentOS. Only a
small subset of hardcore techies would read a database man that comes
with an OS distro. Most people, including those hardcore techies,
would go to postgresql.org and expect to find as much info as
possible. (On that note, perhaps it's time someone considered a name
change to PgSQL, which is much saner--and did something with the
barren pgsql.com)

Right now, if I wish to contribute to the documentation, how do I make
it relevant? Look at MySQL docs, or PHP manual. I can leave comments
in a context-relevant manner -- e.g., check at the bottom of page:
http://sg.php.net/manual/en/ref.pgsql.php.

I was just looking at the ident/trust/etc authentication banter from
pgsql docs. Couldn't make out what greek was on there. When I jostled
a bit, and finally understood it, and really wanted to write it in
plain English for the next "simple" user like myself who just wants to
get cracking with the db and doesn't care about the admin intricasies,
then how I should I write it?

Only option for me is to pour content on these mailing lists (I mean,
we're in 2007, why is a forum so difficult? It's a lot friendlier than
a mailing list as I only get content updates for threads I subscribe
to, and can get there whenever I want...with search and all other
paraphernalia) or to put it on some blog and hope it shows up on
google.

Which it seldom does. If you think the problem "psql: FATAL: role
'root' does not exist" is so common, try it on google with double
quotes. It returns 5 websites, 3 in English. None of which explains
anything meaningful.

> I think it's some sort of serum they inject into semi-skilled i.t.
> workers that makes them arrogant and spout off random poorly
> constructed off topic posts on professional mailing lists while asking
> for help in the same breath. Fortunately, I never went to college and
> missed my shot.

You clearly missed a lot more at college.

Yes I was trying for help. I see a lot of people like me who're
newbies but REALLY want to grok Postgresql but find themselves
needlessly intimidated by the geeky learning curve, which, at version
8.2, is pathetic and inexcusable.

My problem is solved. Thanks for the community. No thanks to you.

But I offered constructive feedback about why this mailing list banter
should not be necessary. These big Cpanel type applications -- used by
millions of hosting providers, including many people who run their
servers on Debian -- are precisely what MySQL has cracked the code.

The sooner PG "gets it", the better it will be for PG, for the PG
community, and if my sordid experiences with MySQL are anything to go
by, for several database users in general.

The last thing PGSQL needs is cocky isolationists such as yourself. I
have added specific commentary to this thread (and so have others who
have helped me even if we discussed peripheral issues in the margins)
to help the cause of the application about which this mailing list is.
You have only spewed your ignorance and attitude. Spare me.

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(dot)papa(at)gmail(dot)com> 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(dot)finner(at)invenius(dot)de
Telefax: 0271 231 8608 Web: http://www.invenius.de
Key fingerprint = 90DF FF40 582E 6D6B BADF 6E6A A74E 67E4 E788 2651

Martijn van Oosterhout wrote:
> On Wed, Jan 24, 2007 at 01:31:23AM +0800, Erick Papadakis wrote:
>> 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.
>
> Setting aside the fact that I don't even know what Cpanel is, I'm not
> sure how this is practical. How many versions of Cpanel are there and
> which versions of postgres do they ship? If Cpanel releases a new
> version, do the postgresql docs needs to be updated?

Cpanel is one of those things that consultants dread. It is a hosting
panel that gives a nice web administrative interface to a bunch of stuff
like email, vhosting etc..

THe problem is, it is also badly designed from a PostgreSQL
infrastructure perspective and typically ships with older versions of
PostgreSQL and further it sort of jails its install so upgrading
PostgreSQL becomes a bear.

IMO, if you want to use a PostgreSQL ignore Cpanel and use PostgreSQL.
Use Cpanel for all its pretty features but stay away from it for your
PostgreSQL requirements.

Sincerely,

Joshua D. Drake

--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

How about using "updatedb" before using whereis or locate?

Regards, Frank.

On Wed, 24 Jan 2007 01:18:20 +0800 "Erick Papadakis" <erick(dot)papa(at)gmail(dot)com> thought long, then sat down and wrote:

> Where is pg_hba.conf?
>
> I tried find and whereis commands, but could not find it.
>
> Thanks for any pointers.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match

--
Frank Finner

Invenius - Lösungen mit Linux
Köpfchenstraße 36
57072 Siegen
Telefon: 0271 231 8606 Mail: frank(dot)finner(at)invenius(dot)de
Telefax: 0271 231 8608 Web: http://www.invenius.de
Key fingerprint = 90DF FF40 582E 6D6B BADF 6E6A A74E 67E4 E788 2651

Erick Papadakis wrote:
> Right now, if I wish to contribute to the documentation, how do I make
> it relevant? Look at MySQL docs, or PHP manual. I can leave comments
> in a context-relevant manner -- e.g., check at the bottom of page:
> http://sg.php.net/manual/en/ref.pgsql.php.

Have you seen the "interactive" documentation which starts at
http://www.postgresql.org/docs/8.2/interactive/index.html ?

There are 2 different PG documentation trees on the web site -- the
"static" pages (http://www.postgresql.org/docs/8.2/static/index.html),
which only include the content generated from the documentation source,
and the interactive pages which allow users to post
comments/clarifications as you desire.

Depending on how you originally found the documentation, you may have
come from Google results or found an existing deep link into the static
pages, which don't provide any indication that the interactive pages exist.

Andrew

P.S. - Has anyone considered adding links in the documentation so that a
given static/interactive documentation page would contain a link to the
same page in the interactive/static section? Or at least a link from
the static page to the corresponding interactive page?

On Wed, Jan 24, 2007 at 02:17:53AM +0800, Erick Papadakis wrote:
> Cpanel team takes care of all of this. All it takes is for someone
> like pgsql to wake up, smell the coffee, and get over the ignorance
> about a platform that is the most prevalent in the web hosting world.
> Cpanel is used by millions of users. I'll be surprised if Debian is.

Dunno. I know the Google pagecount for Debian outnumbers that of cPanel
by more than 10-to-1.

> Debian is an OS distro. The equivalent in my case is CentOS. Only a
> small subset of hardcore techies would read a database man that comes
> with an OS distro.

You don't seriously beleive that, do you? Debian occasionally makes
significant changes to software it distributes and someone who doesn't
check the accompanying notes is likely to get confused because what
they have might not match the online documentation.

If you want exactly what's distributed by the Postgresql team, compile
and install it yourself. If someone else compiled it for you, you'd be
wise to check what they setup before looking elsewhere.

> Only option for me is to pour content on these mailing lists (I mean,
> we're in 2007, why is a forum so difficult? It's a lot friendlier than
> a mailing list as I only get content updates for threads I subscribe
> to, and can get there whenever I want...with search and all other
> paraphernalia) or to put it on some blog and hope it shows up on
> google.

There are forums, they just never get anywhere because the critical
mass of users is here. (Personally, I hate forums)

> Which it seldom does. If you think the problem "psql: FATAL: role
> 'root' does not exist" is so common, try it on google with double
> quotes. It returns 5 websites, 3 in English. None of which explains
> anything meaningful.

Your problem is the double quotes, take them out and you get thousands
of pages with your exact problem. Google tip: don't use double quotes
where the error message contains something substituted (like 'root' in
your message).

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

On Wed, Jan 24, 2007 at 02:17:53 +0800,
Erick Papadakis <erick(dot)papa(at)gmail(dot)com> wrote:
>
> I was just looking at the ident/trust/etc authentication banter from
> pgsql docs. Couldn't make out what greek was on there. When I jostled
> a bit, and finally understood it, and really wanted to write it in
> plain English for the next "simple" user like myself who just wants to
> get cracking with the db and doesn't care about the admin intricasies,
> then how I should I write it?

That's really not a good idea. I strongly recommend at least skimming through
the entire postgres manual before trying to admin your own instance of it.
Spending some time up front to better understand what you are doing and what
options you have is going to save you much grief down the road.

# erick(dot)papa(at)gmail(dot)com / 2007-01-23 23:17:31 +0800:
> >Please don't top-post, it disturbes the flow of the communication.
>
> Interesting. I prefer getting to the point an author is making.

Top posting means you end up far off the mark.

> >There's documentation about that too, at the end of the installation
> >instructions IIRC.
>
>
> I did not see them. Please point me? I'd deeply appreciate it.

Please stop asking for spoonfeeding. You have no problems reading email,
how about some web pages?

http://www.postgresql.org/docs/8.2/interactive/index.html
http://www.postgresql.org/docs/8.2/interactive/bookindex.html

--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991

Have you read

http://www.postgresql.org/docs/8.2/static/tutorial.html

??

If there are specific parts in there that are unclear or missing I'm
sure the developers would be happy to know.

-Doug