|
|
|
|
|
Known issues:
Users must be added to postgres list by support, similar to how mailing lists or ftp space are created for users. Send a note to support@eskimo.com with your eskimo.com login and the password you want to set for your database.
The 'psql' on the main shell server, 'eskimo.com' connects to databases and creates/updates correctly. For security, a user's database would have the same name as the user's login, and only that user can connect to it. Table names are not limited in that way.
'psql' is located at '/usr/local/pgsql/bin' on 'eskimo' and 'www'. The PostgreSQL server itself is on 'www'.
From the main eskimo.com server, the command to connect would be only 'psql -h www'.
From the web server www.eskimo.com, CGI's running as the user's id need only use 'psql' to connect/update.
Other hosts would authenticate with a requested password unique to postgres (similar to the way the mailing lists have their own passwords).
This will facilitate the situation where a user has someone else doing SQL admin for them without releasing the account's password itself, etc. The "GRANT" SQL command is not practical since it cannot be used on databases themselves in PostgreSQL (yet?).
The 'pg_dump' on eskimo.com fails (previous version, errors about regular expressions failing), but the 'pg_dump' on www (for CGI's, etc.) works properly. Working compiles on other machines (my own test was with v7.0 on my home Linux box. ~ Eric) can use 'pg_dump' without error.
A work-around for this can be to use a CGI-script to redirect the output of 'pg_dump' to a file in your directory (remember, 'database-name' will be the same as your eskimo.com login):
#!/bin/sh
/bin/echo "Content-Type: text/html"
/bin/echo
/usr/local/pgsql/bin/pg_dump database-name > ~/data-dump
/bin/echo "Done"
This would need to run under your own userid. Please see http://www.eskimo.com/support/www.html.
Updated May. 19, 2001