Postgresql as Backend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drupal |
Invalid
|
Undecided
|
Unassigned |
Bug Description
'sudo aptitude install drupal', after I already had apache, php4, and postgresql installed, didn't create the drupal user or drupal database in Postgresql.
'sudo dpkg-reconfigure drupal' threw up a nice curses interface, but it didn't do the job either.
I don't know about packaging. I did get the setup to work, and have documented the workaround: http://
Some things I noticed:
You have to su - postgres before creating a new user, database, or language.
The /usr/share/
- does not create the drupal user or database, so apparently isn't run as the postgres user to do this part of the job.
- has CREATE FUNCTION statements which require the loading of plpgsql language.
- has the two commands to load the plpgsql language tacked onto the end of the file, perhaps they need to be defined earlier?
- needs those last two commands to be run as the postgres user.
Changed in drupal: | |
status: | New → Invalid |
Oh yeah, the /usr/share/ drupal/ database/ database. pgsql mentions Debian Bug #242572, which tacks the two language commands on the end. Probably has nothing to do with the problem, but I thought I'd mention it. Details at: lists.drupal. org/archives/ drupal- devel/2004- 05/msg00569. html
http://