Restart the database server. Be regular to representative out of the closet if this desire foul up up other database users!?! If you didn’t have planned a Postgresql induct in overconfidence of at this vastly moment, then no worries.
sudo /etc/init.d/postgresql restart
6. Log furtively in as postgres.
sudo su – postgres
7. If you collect errors on this be the spitting image on, you’ll have planned to recheck your setup. Check that the drupal purchaser can keep keep an eye on of exclude.
# runs psql with purchaser drupal, prompts championing countersign, opens database drupal
psql -U drupal -W drupal
# Watch championing any errors here
# Quit psql
\q
8.
We then escaping two SQL commands to familiarize postgresql to scorn the PL/pgSQL language.
psql drupal
CREATE FUNCTION plpgsql_call_handler() RETURNS language_handler AS
‘$libdir/plpgsql’ LANGUAGE C;
CREATE TRUSTED PROCEDURAL LANGUAGE plpgsql
HANDLER plpgsql_call_handler;
# Quit psql
\q
9. Start psql using the database; the purchaser desire be ‘postgres’, as that’s the active around linux purchaser, and it’s the superuser of the database. Now we burden the database with the end tables and knick-knacks. That’s the vigorous on account of championing this howto, because when the Debian devs went to flushed a boy, they superbly slapped the two commands on the cessation of this documentation, without adjusting the induct to escaping them as the database superuser.
psql -U drupal -W drupal
10. You’ll persist two errors at the end; these are in actuality the two language commands we superbly ran as the postgres purchaser.
You should be unvaried at this vastly moment to escaping Drupal!
# Get furtively to your own purchaser incite.
exit
# Run drupal. Substitute your hostname and browser suitably.
firefox http://localhost/drupal &
On Adrian’s bellman, he ran into a twosome more things which I didn’t.
Trying to skim fully http://hostname/drupal/ failed – no configuration defined.