<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
<channel>
<title>Keith's Web Blog RSS Feed</title>
<language>en-us</language>
<link>http://www.keithwatanabe.net/index.php</link>
<description>Keith Watanabe's Website</description>
<item>
<title>Quick Postgres Source Installation</title>
<link>http://www.keithwatanabe.net/blogs/2004/4/23/ae4ee5df9e92678668e5b5e3a464b97f.html</link>
<description><![CDATA[You can put this into a shell script and run it:

./configure --prefix=/opt/databases/postgres7.4.2 --enable-locale --enable-multibyte=UNICODE --with-odbc --with-java
--with-perl --with-python --with-tcl
make
make install

all the --with-* style flags are what i tend to use.  make sure that you have certain software setup when you do this such as java and tcl!  Java additionally requires ant.  So you need to have the ant binary in your $PATH.  tcl requires additional libraries for the client software program.  If you're running Redhat, make sure you install those tcl rpms.  I use apt-get from freshrpms.net to avoid the headaches of dependencies.

From there, if you want to get it started, here's a few additional steps:

# adduser pgsql
# mkdir /opt/databases/pgsql/data
# chown pgsql /opt/databases/pgsql/data
# su - pgsql
# /opt/databases/pgsql/bin/initdb -D /opt/databases/pgsql/data -S

That last commands puts the server into a daemon mode and forks it into the background.]]></description>
<pubDate>Fri, 23 Apr 2004 09:56:19 -0600</pubDate>
<guid>http://www.keithwatanabe.net/blogs/2004/4/23/ae4ee5df9e92678668e5b5e3a464b97f.html</guid>
</item>
<item>
<title>Postgres Stored Procedures and Perl</title>
<link>http://www.keithwatanabe.net/blogs/2004/4/23/43b55b1af28b6e6dd9488b4fe3fc865f.html</link>
<description><![CDATA[As far as I know, the DBD::Pg module doesn't support stored procedures.  Really, you're better off keeping transactions under the application if you're using perl and DBD::Pg (sidenote: I've found the stored procedure language to be poor in postgres; this is just the author's opinion).]]></description>
<pubDate>Fri, 23 Apr 2004 09:58:45 -0600</pubDate>
<guid>http://www.keithwatanabe.net/blogs/2004/4/23/43b55b1af28b6e6dd9488b4fe3fc865f.html</guid>
</item>
<item>
<title>Configuring Postgres Over the Network</title>
<link>http://www.keithwatanabe.net/blogs/2004/9/7/67abca29bac51671ff029424c986e33c.html</link>
<description><![CDATA[Had a bitch of a problem trying to get my remote system to connect to my postgres server.  Turned out there were at least two places to look.  One (the hardest to determine) was the firewall (iptables) and the other which was slightly easier was pg_hba.conf.  Although I'm not 100% certain that I did this correctly, I basically hacked /etc/sysconfig/iptables and added a line:

-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 5432 -j ACCEPT

before one of the reject rules.  then i restarted the iptables service.  Still when you run postgres to allow TCP connections to come in, you still have another layer of security: pg_hba.conf.

Here, you can fine tune the settings so that only certain users can get access to a database, etc.  For instance, you might have a line like:

host	foo		bar		192.168.2.24		  255.255.255.255	trust

this line indicates that database foo can let user bar in through the ip/host 192.168.2.24.  very useful!
]]></description>
<pubDate>Tue, 07 Sep 2004 00:03:34 -0600</pubDate>
<guid>http://www.keithwatanabe.net/blogs/2004/9/7/67abca29bac51671ff029424c986e33c.html</guid>
</item>
</channel>
</rss>
