50 lines
1.5 KiB
Plaintext
50 lines
1.5 KiB
Plaintext
The PostgreSQL port has a collection of "side orders":
|
|
|
|
p5-Pg
|
|
A perl5 API for client access to PostgreSQL databases.
|
|
|
|
postgresql-tcltk
|
|
If you want tcl/tk client support. You get a neat GUI, pgaccess, as
|
|
a bonus!
|
|
|
|
postgresql-jdbc
|
|
For Java JDBC support.
|
|
|
|
postgresql-odbc
|
|
For client access from unix applications using ODBC as access
|
|
method. Not needed to access unix PostgreSQL servers from Win32
|
|
using ODBC. See below.
|
|
|
|
ruby-postgres, py-PyGreSQL
|
|
For client access to PostgreSQL databases using the ruby & python
|
|
languages.
|
|
|
|
postgresql-plperl, postgresql-pltcl & postgresql-plruby
|
|
For using perl5, tcl & ruby as procedural languages.
|
|
|
|
etc etc...
|
|
|
|
If you have many tables and many clients running, consider raising
|
|
kern.maxfiles using sysctl(8).
|
|
|
|
You should vacuum and backup your database regularly. There is a
|
|
periodic script, /usr/local/share/postgresql/502.pgsql, that you may
|
|
use.
|
|
|
|
To allow many simultaneous connections to your PostgreSQL server, you
|
|
should raise the SystemV shared memory limits in your kernel. Here are
|
|
example values for allowing up to 180 clients (tinkering in
|
|
postgresql.conf also needed, of course):
|
|
options SYSVSHM
|
|
options SYSVSEM
|
|
options SYSVMSG
|
|
options SHMMAXPGS=65536
|
|
options SEMMNI=40
|
|
options SEMMNS=240
|
|
options SEMUME=40
|
|
options SEMMNU=120
|
|
|
|
If you plan to access your PostgreSQL server using ODBC, please
|
|
consider running the SQL script /usr/local/share/postgresql/odbc.sql
|
|
to get the functions required for ODBC compliance.
|