PostgreSQL on OS X

Are there major differences between the windows and mac versions as to where the FAQ/tutorials for windows user wouldn't be helpful for those on OS X? I'm trying to figure out how to configure my data base a bit to help speed it up a bit but am lost looking through the FAQs/Tutorials on how to do so.
I'm in PGAdmin and can't find where it is I go to change up the configs as noted in the PostgreSQL wiki. Another thing I'm running into is this screen when connecting to my data base:
Database encoding
The database PT3 DB is created to store data using the SQL_ASCII encoding. This encoding is defined for 7 bit characters only; the meaning of characters with the 8th bit set (non-ASCII characters 127-255) is not defined. Consequently, it is not possible for the server to convert the data to other encodings.
If you're storing non-ASCII data in the database, you're strongly encouraged to use a proper database encoding representing your locale character set to take benefit from the automatic conversion to different client encodings when needed. If you store non-ASCII data in an SQL_ASCII database, you may encounter weird characters written to or read from the database, caused by code conversion problems. This may cause you a lot of headache when accessing the database using different client programs and drivers.
For most installations, Unicode (UTF8) encoding will provide the most flexible capabilities.
I'm in PGAdmin and can't find where it is I go to change up the configs as noted in the PostgreSQL wiki. Another thing I'm running into is this screen when connecting to my data base:
Database encoding
The database PT3 DB is created to store data using the SQL_ASCII encoding. This encoding is defined for 7 bit characters only; the meaning of characters with the 8th bit set (non-ASCII characters 127-255) is not defined. Consequently, it is not possible for the server to convert the data to other encodings.
If you're storing non-ASCII data in the database, you're strongly encouraged to use a proper database encoding representing your locale character set to take benefit from the automatic conversion to different client encodings when needed. If you store non-ASCII data in an SQL_ASCII database, you may encounter weird characters written to or read from the database, caused by code conversion problems. This may cause you a lot of headache when accessing the database using different client programs and drivers.
For most installations, Unicode (UTF8) encoding will provide the most flexible capabilities.