Postgres Pro
Downloads
Home   >   mailing lists

Thread: typo in postgresql.conf

typo in postgresql.conf

From
Holger Klawitter
Date:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

INSTALLATION REPORT:
postgres runs fine on Linux (i386, sid, 2.4.27) I checked
basic functionality and multibyte encodings.

TYPOS:
* postgresql.conf says that you may specify "interfaces" in
listen_addresses, it should read "hostnames".

NITPICKING:
* (initdb.1) it might be good to add a warnung like this:
=20=20
  Beware: Not every --locale works with every --encoding!
  In particular --econding=3DUNICODE (you might want to use
  "--locale=3Den_US.utf8" or similar. See "locale -a" to obtain
  a list of available locales.

STORE:
* (store.pgsql.com) I still miss an item to make a donation.

* Even worse: "Merchant Account is CLOSED."

Mit freundlichem Gru=DF / With kind regards
    Holger Klawitter
- --
lists <at> klawitter <dot> de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFBGcMb1Xdt0HKSwgYRApTVAJ4tBb0fiWF3mk87foUCfQHQ19AsbwCeNMNv
Oit5y2Evo3HSKL1ycnOHbBo=3D
=3DvOVp
-----END PGP SIGNATURE-----

Re: typo in postgresql.conf

From
Tom Lane
Date:
Holger Klawitter <lists@klawitter.de> writes:
> TYPOS:
> * postgresql.conf says that you may specify "interfaces" in
> listen_addresses, it should read "hostnames".

I think it means what it says.  Interfaces are what you can actually
bind to or not bind to, at least with the TCP stacks I've worked with.

> NITPICKING:
> * (initdb.1) it might be good to add a warnung like this:

>   Beware: Not every --locale works with every --encoding!
>   In particular --econding=UNICODE (you might want to use
>   "--locale=en_US.utf8" or similar. See "locale -a" to obtain
>   a list of available locales.

There is a test now in initdb to warn you if you pick an incompatible
pair.  Does it not work for you?

            regards, tom lane

Re: typo in postgresql.conf

From
Gaetano Mendola
Date:
Tom Lane wrote:

> Holger Klawitter <lists@klawitter.de> writes:
>
>>TYPOS:
>>* postgresql.conf says that you may specify "interfaces" in
>>listen_addresses, it should read "hostnames".
>
>
> I think it means what it says.  Interfaces are what you can actually
> bind to or not bind to, at least with the TCP stacks I've worked with.

mmm You can bind a local address not an interface, may be I don't have
your experiences but I think that interfaces in Linux world are
eth0, eth1, ...

for sure I'm wrong :-)

Regards
Gaetano Mendola