dbTalk Databases Forums  

[BUGS] typo in postgresql.conf

mailing.database.pgsql-bugs mailing.database.pgsql-bugs


Discuss [BUGS] typo in postgresql.conf in the mailing.database.pgsql-bugs forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Holger Klawitter
 
Posts: n/a

Default [BUGS] typo in postgresql.conf - 08-13-2004 , 01:28 PM






-----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)

iD8DBQFBGcMb1Xdt0HKSwgYRApTVAJ4tBb0fiWF3mk87foUCfQ HQ19AsbwCeNMNv
Oit5y2Evo3HSKL1ycnOHbBo=3D
=3DvOVp
-----END PGP SIGNATURE-----


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

Reply With Quote
  #2  
Old   
Tom Lane
 
Posts: n/a

Default Re: [BUGS] typo in postgresql.conf - 08-13-2004 , 03:29 PM






Holger Klawitter <lists (AT) klawitter (DOT) de> writes:
Quote:
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.

Quote:
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

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly


Reply With Quote
  #3  
Old   
Gaetano Mendola
 
Posts: n/a

Default Re: [BUGS] typo in postgresql.conf - 08-14-2004 , 06:42 AM



Tom Lane wrote:

Quote:
Holger Klawitter <lists (AT) klawitter (DOT) 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





---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.