-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> How I can find all the aggregate functions available ?
count() min() max() avg() sum() stddev() variance()
> How to set a password for postgres user ?
ALTER USER bob WITH PASSWORD 'pipesmoke';
Check out the documentation on the pg_hba.conf file to make
sure that you are requiring passwords.
> Which is the format of admins file ?
Not sure what you mean, but you probably want the file "postgresql.conf",
which is located in your PGDATA directory.
- From the documentation:
All parameter names are case-insensitive. Every parameter takes a value of one
of the four types: Boolean, integer, floating point, and string. Boolean
values are ON, OFF, TRUE, FALSE, YES, NO, 1, 0 (case-insensitive) or any
non-ambiguous prefix of these.
One way to set these options is to edit the file postgresql.conf in the data
directory. (A default file is installed there.) An example of what this file
might look like is:
# This is a comment
log_connections = yes
syslog = 2
search_path = '$user, public'
As you see, options are one per line. The equal sign between name and value is
optional. Whitespace is insignificant and blank lines are ignored. Hash marks
("#") introduce comments anywhere. Parameter values that are not simple
identifiers or numbers should be single-quoted.
The configuration file is reread whenever the postmaster receives a SIGHUP
signal (which is most easily sent by means of pg_ctl reload). The postmaster
also propagates this signal to all currently running backend processes so that
existing sessions also get the new value. Alternatively, you can send the
signal to a single backend process directly.
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200302141042
-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+TQ7MvJuQZxSWSsgRAq9VAJ4xDdrJIhfGYsBejoz/lfe5l25bHACgjfUI
YT402td83kTxTJW2IN9s/oc=
=iQnx
-----END PGP SIGNATURE-----
