Jsp, Tomcat, J2Ee, Linux Web Hosting, Hibernate Programming Blog

586 CHAPTER 25 INSTALLING POSTGRESQL 2. User Interfaces: This category includes the psql and pgAdmin III GUI applications, both of which are scheduled for installation by default. Both applications are introduced in Chapter 27. 3. Database Drivers: This category includes the JDBC, Npgsql, ODBC, and OLEDB drivers, all of which are scheduled for installation by default. If you don t plan to use PostgreSQL in conjunction with Java-, .NET-, ODBC-, or OLEDB-compatible technologies, respectively, then cancel their installation to save some drive space. 4. Development: This category includes various development-related files and utilities, all of which are not scheduled for installation by default and are not required for the purposes of this book. During this stage you also have the opportunity to change the installation directory, with the default being set to C:Program FilesPostgreSQLX.X. Because spaces in pathnames can be somewhat of an annoyance when writing scripts, consider changing this to C:pgsql or something similar. Once this is complete, click Next to continue. 4. Service Configuration: This step involves setting several very important parameters: 1. Install as a Service: You re first prompted to install PostgreSQL as a service, which means it will turn on and off automatically along with the operating system. You ll learn more about running PostgreSQL as a service in the later section, Starting and Stopping PostgreSQL Automatically. When running PostgreSQL as mission-critical applications, you ll certainly want to leave this enabled; however, for testing environments, you may choose to start and stop it manually. Doing so is also covered in the aforementioned section. If you choose to not install PostgreSQL as a service, then the remaining five parameters are irrelevant, so you should continue to Step 5. 2. Service Name: If you do choose to install PostgreSQL as a service, this field represents the name of the service; you can set this field to anything you please, although the default is just fine. 3. Account Name: This field specifies the name of the user who owns the PostgreSQL daemon process. Consider leaving this set to postgres(unless you have good reasons for doing otherwise), which causes this account to be created and used expressly for operating the PostgreSQL daemon. You re also free to specify the name of an existing account; however, this account cannot be a privileged user, such as Administrator! 4. Account Domain: This field specifies the server s commonly used network name. This is set to your server s specified domain name by default. 5. Daemon Account: Finally, you re prompted to enter and verify a password via the Account password and Verify password fields, respectively. Be sure to choose a sufficiently difficult password, yet something you can remember. You also have the option of leaving this blank, which prompts PostgreSQL to create a random password for you. If you allow PostgreSQL to choose the password, it will not communicate the password to you, because this account should be used for no purpose other than to operate the daemon account, and therefore there is no particular reason to know this password.
If you are looking for cheap and quality webhost to host and run your website check Jboss Web Hosting services.

CHAPTER 25 INSTALLING POSTGRESQL Step 3. Add the PostgreSQL bin Directory to Your System Path For reasons of convenience, add the location of PostgreSQL s bin directory to your system path. Although this is not a requirement, doing so enables you to run the applications found in that directory regardless of your present location in the path. If you want to do this only for your user, add the following information to your shell configuration file (which typically resides in your home directory). Otherwise, add it to /etc/profile to make this convenience available to every user. PATH=/usr/local/pgsql/bin:$PATH export PATH Once these changes have been saved to the appropriate file, you need to either log out and log back in again or, depending on the shell you re using, use the source command to effect the changes. With these three steps completed, proceed to the section Starting PostgreSQL for the First Time. Installing PostgreSQL on Windows 2000, XP, and 2003 Only as of version 8.0 has a native version of PostgreSQL been available for the Windows platform. However, despite being such a new addition, the installer is already very usable, making installation on the Windows platform quite trivial. Please note that PostgreSQL cannot be installed on the FAT file system; only NTFS is supported. The following steps outline the installation process on Windows: 1. Installation Language and Log: Unzip the package, and then click the postgres-X.X.msi icon, found in the downloaded installer package, to begin the installation process. The first installer screen prompts you to choose a preferred language for the process. Presently the installer supports the Brazilian Portuguese, English, French, German, Russian, Swedish, and Turkish languages. At this stage you can also choose to write a log that details the installation process. Typically this is necessary only during troubleshooting situations, but feel free to check this box if you want to learn more about exactly what happens during installation. Choose the appropriate language and, if necessary, enable the log. Click the Start button to continue. 2. Installation Welcome and Notes: The next few screens offer a welcome message and information regarding installation issues, licensing terms, and various other pertinent bits of data. Feel free to peruse these screens, and then proceed by clicking Next. 3. Installation Options: Next you are presented with installation options. These options are broken into four categories: 1. Database Server: This category contains options for installing the data directory files, for enabling non-English support for status and error messages, and for supporting geographical data. If you don t require the latter two options, feel free to leave both disabled. However, be sure to leave the data directory installation option enabled.
Check Tomcat Web Hosting services for best quality webspace to host your web application.

584 CHAPTER 25 INSTALLING POSTGRESQL Step 1. Create the postgres User Although it s possible to run PostgreSQL as any non-root user for instance, from your home directory, for testing purposes for most typical uses, you ll want to create a special user whose only purpose is to own the PostgreSQL daemon process (known as postmaster) and the database files. When properly configured, it will be impossible for others to log in as this user, thereby ensuring that the server s operation can t be interfered with and that the data files can t be deleted or surreptitiously accessed. While the name of this user is completely up to you, the name postgres is commonly used. Therefore, go ahead and create this user, using either postgres or another name of your choosing: %> useradd postgres Note You need superuser privileges to execute this command. From this point forward, it s presumed that you opted to use the username postgres; if you did not, please substitute any further references in this chapter with the appropriate name. Step 2. Initialize the PostgreSQL Database Next, you must initialize the PostgreSQL database cluster, which involves specifying the location of the database files and creating two initial databases, namely postgres and template1. You accomplish this by using the PostgreSQL command initdb. You should execute this command as the newly created postgres user; however, because this user isn t privileged and the database directory must be created first, you need to first create this directory as a privileged user: %> mkdir /usr/local/pgsql/data Note that this example presumes that /usr/local/pgsql/ is the location in which PostgreSQL has been installed. Keep in mind that you are by no means constrained to hosting the databases within the PostgreSQL installation directory and are free to choose any directory you please. However, for the sake of consistency, from this point forward it s assumed that you chose that directory; therefore, substitute any further references in this chapter with the appropriate name if you chose a different default location. Next, assign the ownership of this data directory to the postgres user created in the previous step: %> chown postgres /usr/local/pgsql/data Now it s time to execute the initdb command, which will create the cluster. However, you should do so as the postgres user, so change over to that user before proceeding. %>su postgres postgres$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
From our experience, we can recommend PHP Web Hosting services, if you need affordable webhost to host and run your web application.

CHAPTER 25 INSTALLING POSTGRESQL 583 %> ./configure –without-docdir Table 25-1 offers a list of some of the more commonplace configuration options. A complete list of configuration options is available by executing configure as follows (note that two dashes precede the help option, which may be difficult to distinguish in print): %> ./configure –help Table 25-1. Useful Configuration Options Option Description –prefix=prefix Install PostgreSQL in the directory specified by prefix. The default directory is /usr/local/pgsql. –bindir=dir Install the application directories in the directory specified by dir. The default directory is prefix/bin. –datadir=dir Designate the data directory as dir. The default directory is prefix/XXX. –with-docdir=dir Install documentation in the directory specified by dir. The default directory is prefix/doc. –without-docdir Do not install the documentation. –with-perl Enable support for Perl-based stored procedures (Pl/Perl). –with-pgport=port Set PostgreSQL s default port to port. –with-python Enable support for Python-based stored procedures (Pl/Python). –with-tcl Enable support for Tcl-based stored procedures (P/Tcl). Therefore, to install PostgreSQL from source, simply execute configure with any appropriate options, execute make, and then change to the superuser and execute make install. Note To minimize the amount of installation space, some Linux variants do not install the readline-devel and zlib-devel packages by default. Because the availability of Readline improves the psql client s capabilities, and zlib is used to compress dumped data, you need to install them if you receive messages during the configuration step indicating the script s inability to locate them. If they are by chance installed in a nonstandard location, you can use the option –with-libs to point to them. If you choose to forego these capabilities, pass –without-readline and –without-zlib when configuring PostgreSQL. Linux Post-Installation Steps Once PostgreSQL has been successfully installed on the Linux/Unix operating system, you need to carry out a few more steps before the database server is fully operational. Those steps are outlined in this section.
Visit our web design programs services for an affordable and reliable webhost to suit all your needs.

582 CHAPTER 25 INSTALLING POSTGRESQL Installing PostgreSQL on Linux and Unix This section outlines installing PostgreSQL using both the RPMs and source code. Installing PostgreSQL from RPMs Installing PostgreSQL from an RPM is a trivial task; just execute the following command as root: %>rpm -ivh postgresql-*.rpm Next, proceed to the section Linux Post-Installation Steps to complete the configuration process. Installing PostgreSQL from Source Installing from source is the route you want to take if you want to modify the default settings, such as specifying whether documentation should be installed or changing the default location of the PostgreSQL applications. In fact, you might be forced to install from source if prebuilt packages are not available for your particular Unix variant. While newcomers to open source software might feel a bit intimidated by the idea of executing the unfamiliar commands involved in the configuration and installation process, it s actually quite trivial. In fact, at its most basic level you can build from source simply by executing the following commands: %> gunzip postgresql-X.X.X.tar.gz %> tar xvf postgresql-X.X.X.tar %> cd postgresql-X.X.X %> ./configure [Wait patiently while the configuration process completes] %> make [Wait patiently while the build process completes] %> make install [Wait patiently while the installation process completes] If, when executing any of these commands, you receive a message stating something to the effect of command not found, then your operating system doesn t have all of the requisite software installed. At a minimum, you need tar (http://www.gnu.org/software/tar/) and gzip (http://www.gnu.org/software/gzip/) (although tar can also unzip) or similar solutions for uncompressing and unarchiving the PostgreSQL package, respectively. You also need a solu tion such as GNU make (http://www.gnu.org/software/make/) for building the package and, finally, a C compiler such as that found in the GNU Compiler Collection, better known as GCC (http://gcc.gnu.org/). If any of these applications is not presently installed on your system, you re guaranteed to find it on the distribution CD or on your repository of choice. Also, you need to execute the last command (make install) as a superuser, due to the need to create and write to directories; for security reasons, you should execute the first two commands as any non-superuser. However, executing these commands as just described causes PostgreSQL to be built using the default settings, some of which you may wish to change. To do so, you need to pass one or several options to the configure command. For example, to bypass instal lation of the documentation, execute configure like so, and then execute make and make install as indicated above:
Please visit our professional web hosting services to find out about cheap and reliable webhost service that will surely answer all your demands.

CHAPTER 25 INSTALLING POSTGRESQL postgresql-X.X.X-binaries-no-installer-zip: Contains the installation directory, which you could just uncompress and place in an appropriate directory, C:/ for instance. However, this does not include several useful utilities and drivers. postgresql-X.X.X-ja.zip: Contains PostgreSQL s Japanese-language version. Although downloading the version lacking the installer is fine, the installer does provide some additional configuration features, so we recommend that you download the installer. At the time of this writing, the installer version was 21MB in size; therefore, depending upon your connection speed, you may want to initiate the download procedure now and continue reading until the download is complete. Of course, if you prefer the Japanese-language version, go ahead and download that version. In any case, you need the services of a compression utility such as WinZip (http://www.winzip.com/) to uncompress the package. PostgreSQL is natively available on the Windows platform only as of version 8.0 (released in January, 2005), so making PostgreSQL compatible with the dwindling number of Windows 95, 98, and Me installations didn t make sense. However, a solution is available for those of you still using these older Windows versions: the Unix-like Cygwin environment (http://www. cygwin.com/). More information regarding this process is provided in the later section, Installing PostgreSQL on Windows 95, 98, and Me. Also, note that while PostgreSQL is known to operate properly on Windows 2000, XP, and 2003, it has not at the time of this writing been tested on 64-bit systems. Finally, PostgreSQL must be installed on the NTFS file system, because FAT file systems do not offer adequate corruption protection or security features. Tip PostgreSQL is also known to run on Windows NT 4, although it s not officially supported and does come with some issues. See the PostgreSQL manual for more information about the caveats. Downloading the Documentation The PostgreSQL manual is available for both download and viewing via the PostgreSQL Web site (http://www.postgresql.org/docs/manuals/). Links to PDFs are available via this URL, while SGML and HTML versions are available on the PostgreSQL FTP site, at http://www. postgresql.org/ftp/. Additionally, you can find a tremendous amount of other learning resources on the Web site http://techdocs.postgresql.org/, including a compilation of the latest tutorials from around the Web, conference papers, and information regarding matters such as PostgreSQL hosting providers, project contributors, and book reviews. Installing PostgreSQL This section details the PostgreSQL installation process for the Linux and Windows platforms. PostgreSQL version 8.1.2 was used to outline the process, but the process for newer versions almost certainly will be identical for some time to come.
Note: In case you are looking for affordable and reliable webhost to host and run your j2ee application check Vision J2ee Web Hosting services.

580 CHAPTER 25 INSTALLING POSTGRESQL Downloading the Unix Version PostgreSQL has a developmental history dating back an impressive 20 years, and was conceived and maintained exclusively for Unix-based platforms until very recently (PostgreSQL 8 was the first version to natively support Windows). Accordingly, in terms of download formats, Unix users have at their disposal a wealth of options, several of the most popular of which are introduced in this section. However, keep in mind that because of PostgreSQL s prominence, it s packaged with all mainstream Unix and Linux variants these days. That said, you may already have a version of PostgreSQL installed. For instance, to determine whether PostgreSQL is available on your RPM-based system, execute the following command: %> rpm -qa | grep -i postgres On a Debian-based operating system such as Ubuntu Linux, use the Synaptic Package Manager to make this determination. In any case, even if a version of PostgreSQL is already installed, you ll nonetheless probably wish to remove it and reinstall anew because the pres ently installed version likely is outdated. RPMs At the time of writing, RPMs were available on the PostgreSQL Web site for Red Hat 9, Red Hat Enterprise Linux 2.1, 3.0, and 4, Red Hat Enterprise Linux 3.0 for 64-bit servers, and Fedora Core versions 1 through 4, with 64-bit versions available for Fedora 2, 3, and 4. A quick search on the popular Rpmfind search Web site http://www.rpmfind.net/turned up RPMs for Mandriva, SuSE, Mandrake, and Yellow Dog PPC. Source As is standard for any open source project, PostgreSQL s source code is available via its Web site. While RPMs offer a very convenient means for installing PostgreSQL, installing from source enables you to wield considerably more control. For instance, when installing from source, you have the opportunity to modify the default location of the data directory, choose to forego installation of the documentation, enable debugging (useful if you are participating in PostgreSQL development and testing), and include additional extensions for talking to PostgreSQL using languages such as Perl, Python, and Tcl. If you re interested in this additional control, proceed to the source directory within the PostgreSQL Web site s Downloads section, navigate to the directory containing the latest non-beta version, and download the distribution in your compressed format of choice (gz or bz2). Downloading the Windows Version If you plan to install PostgreSQL on Windows, binary versions are available via the PostgreSQL FTP site (http://www.postgresql.org/ftp/). In fact, three different versions are available: postgresql-X.X.X.zip: Contains the multilanguage version of the PostgreSQL installer. This is the preferred version and is the one demonstrated later in the chapter, in the section Installing PostgreSQL on Windows.
In case you need quality webspace to host and run your web applications, try our personal web hosting services.

CHAPTER 25 Installing PostgreSQL This chapter offers a general introduction to the PostgreSQL installation and configuration process. This chapter is not intended as a replacement for the instructions provided in the PostgreSQL user manual, but rather highlights the key procedures of immediate interest to anybody who wants to quickly ready the database server for use. In total, this chapter covers the following topics: Understanding the PostgreSQL licensing requirements Downloading instructions for the various platforms supported by PostgreSQL Installing PostgreSQL on Linux and Windows Starting PostgreSQL for the first time PostgreSQL Licensing Requirements PostgreSQL is released under the BSD license, freeing you to use, modify, and even redistribute the software in both source code and binary formats for both commercial and noncommercial purposes. According to the terms of the BSD license, you re even free to incorporate PostgreSQL into proprietary products and not share your enhancements (although you re certainly encouraged to do so). So, in a nutshell, what does this mean? Perhaps most importantly, it means that you re not constrained by any onerous licensing fees, yet you can use the software for profit as well as fun. Note To learn more about the BSD license, see its Wikipedia entry, located at http://en. wikipedia.org/wiki/BSD_license. Downloading PostgreSQL PostgreSQL is available for download from the official PostgreSQL Web site, located at http://www.postgresql.org/, and via the file-sharing application BitTorrent. In this section, you ll learn more about the available PostgreSQL versions for both the Unix and Windows platforms.
If you are looking for cheap and quality webhost to host and run your website check Jboss Web Hosting services.

CHAPTER 24 INTRODUCING POSTGRESQL The National Weather Service The National Oceanic and Atmospheric Administration s (NOAA) National Weather Service (http://weather.gov) is another one of those backbone service providers that people rely on every day. It is responsible for providing weather information and climate forecasts and warnings for the United States and its surrounding areas, providing services to both private and public organizations throughout the world. One of the key areas where PostgreSQL is having an impact is the new Interactive Forecast Preparation System (IFPS), described at http:// www.nws.noaa.gov/mdl/icwf/IFPS_WebPages/indexIFPS.html. This system integrates data from the Doppler radar, surface, and hydrology systems to build detailed localized forecast models. Once the project is fully operational, NOAA expects more than 150 PostgreSQL servers will be in service. WhitePages.com WhitePages.com started up as a hobby site back in the heady dot-com days of 1996. Today, it is one of the Internet s busiest Web sites, handling more than 2 million hits a day on the WhitePages.com site, and more than 8 million hits a day across its network, powering sites like 411.com, Verizon s superpages.com, and the White Pages section of MSN. Even though WhitePages.com had been using both Oracle and MySQL, when it came time to move its core directories in-house, it turned to PostgreSQL. Because WhitePages.com needs to combine large sets of data from multiple sources, PostgreSQL s ability to load and index data at an extremely high rate was a key to its decision to use PostgreSQL. Since then, WhitePages.com s databases have grown to over 375GB, with tables exceeding more than 250 million rows. PostgreSQL has become a very big part of the WhitePages.com network. Summary From humble beginnings in academia to some of the most crucial projects around the globe, PostgreSQL has come a long way since its university days. In this chapter, we have looked at PostgreSQL s history and where it stands today. We also touched upon just a few of the thousands of companies that are making PostgreSQL an integral part of their enterprise solutions. In the following chapters, we ll further acquaint you with many of PostgreSQL s basic topics, covering the installation and configuration process, several PostgreSQL clients, table structures, and security features. If you re new to PostgreSQL, this material will prove invaluable for getting up to speed regarding the basic features and behavior of this powerful database server. If you re already quite familiar with PostgreSQL, we still suggest that you browse through the material; at the very least, it should serve as a valuable reference.
Go visit our java server pages services for a reliable, lowcost webhost to satisfy all your needs.

576 CHAPTER 24 INTRODUCING POSTGRESQL overdeployment, no matter what direction your database needs take you. You can find the full license on the PostgreSQL Web site at http://www.postgresql.org/about/licence. Multiple Support Avenues One of the unique aspects of PostgreSQL compared to other database solutions is its wide range of support services. First and foremost, PostgreSQL has a very active and open user community. Whether looking for help through the mailing lists (http://www.postgresql.org/community/ lists/) or chatting with users on IRC in the #postgresql channel, expert help is always available; in fact, you can often find core database developers answering questions on the novice mailing list. The PostgreSQL community also provides a full array of services for its users, including online interactive documentation (http://www.postgresql.org/docs/), archived and searchable mailing lists (http://archives.postgresql.org/), and project-hosting facilities for PostgreSQL-related software (http://projects.postgresql.org/). Of course, PostgreSQL has more than just a vibrant community behind it; there are also dozens of support companies that make PostgreSQL an integral part of their business. Companies like Command Prompt Inc., credativ GmbH, and PostgreSQL Inc. are all smaller companies who specialize in PostgreSQL. There are also the big companies like Fujitsu, Pervasive Software Inc, and SRA International Inc. who provide PostgreSQL support on a more global scale. This spectrum of companies behind PostgreSQL means that no matter what your support needs, you will be able to find a solution to fit those needs, and you will never have to worry about vendor lock-in. Real-World Users Whether it s a personal pet project or a multinational mission-critical application, chances are PostgreSQL can suit your needs. This section highlights some particularly compelling deployments using this powerful platform. Afilias Inc. Afilias Inc. (http://www.afilias.info) is one of those companies that no one has ever heard of but everybody depends upon. Afilias provides domain name registry solutions, and its systems help to power more than a half dozen different country code domains as well as the .info and .org domains. Afilias use of PostgreSQL is almost revolutionary in the registry industry; at the time of the proposals for the replacement of the .org domain, 9 of the 11 proposals were based on expensive proprietary database solutions. The other two were PostgreSQL (see http:// www.icann.org/tlds/org/questions-to-applicants-13.htm). At this point, Afilias has operated successfully for a number of years under high load conditions, including handling more than 1000 inserts per second, and the folks at Afilias couldn t be happier. In fact, they have become such big fans of the software and its community process that they have hired a number of developers, including PostgreSQL core developer Jan Wieck. They have also sponsored the Slony-I replication project (http://slony.info), which added cross-version, cascading replication into PostgreSQL. The relationship between Afilias and PostgreSQL is a strong one at this point, and each new release helps strengthen that bond.
Check Tomcat Web Hosting services for best quality webspace to host your web application.