Don't like ads? PRO users don't see any ads ;-)
Public Pastes
Guest

Untitled

By: a guest on May 1st, 2012  |  syntax: None  |  size: 2.67 KB  |  hits: 10  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. ======================================================================
  2. For procedural languages and postgresql functions, please note that
  3. you might have to update them when updating the server.
  4.  
  5. If you have many tables and many clients running, consider raising
  6. kern.maxfiles using sysctl(8), or reconfigure your kernel
  7. appropriately.
  8.  
  9. The port is set up to use autovacuum for new databases, but you might
  10. also want to vacuum and perhaps backup your database regularly. There
  11. is a periodic script, /usr/local/etc/periodic/daily/502.pgsql, that
  12. you may find useful. You can use it to backup and perfom vacuum on all
  13. databases nightly. Per default, it perfoms `vacuum analyze'. See the
  14. script for instructions. For autovacuum settings, please review
  15. ~pgsql/data/postgresql.conf.
  16.  
  17. To allow many simultaneous connections to your PostgreSQL server, you
  18. should raise the SystemV shared memory limits in your kernel. Here are
  19. example values for allowing up to 180 clients (configurations in
  20. postgresql.conf also needed, of course):
  21.   options         SYSVSHM
  22.   options         SYSVSEM
  23.   options         SYSVMSG
  24.   options         SHMMAXPGS=65536
  25.   options         SEMMNI=40
  26.   options         SEMMNS=240
  27.   options         SEMUME=40
  28.   options         SEMMNU=120
  29.  
  30. If you plan to access your PostgreSQL server using ODBC, please
  31. consider running the SQL script /usr/local/share/postgresql/odbc.sql
  32. to get the functions required for ODBC compliance.
  33.  
  34. Please note that if you use the rc script,
  35. /usr/local/etc/rc.d/postgresql, to initialize the database, unicode
  36. (UTF-8) will be used to store character data by default.  Set
  37. postgresql_initdb_flags or use login.conf settings described below to
  38. alter this behaviour. See the start rc script for more info.
  39.  
  40. To set limits, environment stuff like locale and collation and other
  41. things, you can set up a class in /etc/login.conf before initializing
  42. the database. Add something similar to this to /etc/login.conf:
  43. ---
  44. postgres:\
  45.         :lang=en_US.UTF-8:\
  46.         :setenv=LC_COLLATE=C:\
  47.         :tc=default:
  48. ---
  49. and run `cap_mkdb /etc/login.conf'.
  50. Then add 'postgresql_class="postgres"' to /etc/rc.conf.
  51.  
  52. ======================================================================
  53.  
  54. To initialize the database, run
  55.  
  56.   /usr/local/etc/rc.d/postgresql initdb
  57.  
  58. You can then start PostgreSQL by running:
  59.  
  60.   /usr/local/etc/rc.d/postgresql start
  61.  
  62. For postmaster settings, see ~pgsql/data/postgresql.conf
  63.  
  64. NB. FreeBSD's PostgreSQL port logs to syslog by default
  65.     See ~pgsql/data/postgresql.conf for more info
  66.  
  67. ======================================================================
  68.  
  69. To run PostgreSQL at startup, add
  70. 'postgresql_enable="YES"' to /etc/rc.conf
create a new version of this paste RAW Paste Data