<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Building PostgreSQL on Leopard</title>
	<atom:link href="http://www.stiefels.net/2007/11/22/building-postgresql-on-leopard/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stiefels.net/2007/11/22/building-postgresql-on-leopard/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 10 Feb 2010 12:43:19 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: BZ</title>
		<link>http://www.stiefels.net/2007/11/22/building-postgresql-on-leopard/comment-page-1/#comment-50</link>
		<dc:creator>BZ</dc:creator>
		<pubDate>Fri, 18 Jul 2008 23:03:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.stiefels.net/2007/11/22/building-postgresql-on-leopard/#comment-50</guid>
		<description>&lt;p&gt;FWIW, I found that this error will occur if you already have an instance of posgresql running.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>FWIW, I found that this error will occur if you already have an instance of posgresql running.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://www.stiefels.net/2007/11/22/building-postgresql-on-leopard/comment-page-1/#comment-49</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Sun, 13 Jul 2008 00:38:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.stiefels.net/2007/11/22/building-postgresql-on-leopard/#comment-49</guid>
		<description>&lt;p&gt;@joost:&lt;br /&gt;
Try increasing the shared memory settings on your system.
Create &lt;strong&gt;/etc/sysctl.conf&lt;/strong&gt; with the follwing content and reboot your machine:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;kern.sysv.shmmax=167772160&lt;br /&gt;
  kern.sysv.shmmin=1&lt;br /&gt;
  kern.sysv.shmmni=32&lt;br /&gt;
  kern.sysv.shmseg=8&lt;br /&gt;
  kern.sysv.shmall=65536&lt;/code&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>@joost:<br />
Try increasing the shared memory settings on your system.<br />
Create <strong>/etc/sysctl.conf</strong> with the follwing content and reboot your machine:</p>
<p><code>kern.sysv.shmmax=167772160<br />
  kern.sysv.shmmin=1<br />
  kern.sysv.shmmni=32<br />
  kern.sysv.shmseg=8<br />
  kern.sysv.shmall=65536</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joost baaij</title>
		<link>http://www.stiefels.net/2007/11/22/building-postgresql-on-leopard/comment-page-1/#comment-48</link>
		<dc:creator>joost baaij</dc:creator>
		<pubDate>Fri, 04 Jul 2008 12:12:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.stiefels.net/2007/11/22/building-postgresql-on-leopard/#comment-48</guid>
		<description>&lt;p&gt;This absolutely does not work with Mac OS X Leopard 10.5.3.&lt;/p&gt;

&lt;p&gt;creating template1 database in ./data/base/1 ... FATAL:  could not create shared memory segment: Cannot allocate memory
DETAIL:  Failed system call was shmget(key=1, size=1777664, 03600).
HINT:  This error usually means that PostgreSQL&#039;s request for a shared memory segment exceeded available memory or swap space. To reduce the request size (currently 1777664 bytes), reduce PostgreSQL&#039;s shared_buffers parameter (currently 50) and/or its max_connections parameter (currently 13).
    The PostgreSQL documentation contains more information about shared memory configuration.
child process exited with exit code 1
initdb: removing contents of data directory &quot;./data&quot;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>This absolutely does not work with Mac OS X Leopard 10.5.3.</p>
<p>creating template1 database in ./data/base/1 &#8230; FATAL:  could not create shared memory segment: Cannot allocate memory<br />
DETAIL:  Failed system call was shmget(key=1, size=1777664, 03600).<br />
HINT:  This error usually means that PostgreSQL&#8217;s request for a shared memory segment exceeded available memory or swap space. To reduce the request size (currently 1777664 bytes), reduce PostgreSQL&#8217;s shared_buffers parameter (currently 50) and/or its max_connections parameter (currently 13).<br />
    The PostgreSQL documentation contains more information about shared memory configuration.<br />
child process exited with exit code 1<br />
initdb: removing contents of data directory &#8220;./data&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joe</title>
		<link>http://www.stiefels.net/2007/11/22/building-postgresql-on-leopard/comment-page-1/#comment-47</link>
		<dc:creator>joe</dc:creator>
		<pubDate>Mon, 25 Feb 2008 23:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.stiefels.net/2007/11/22/building-postgresql-on-leopard/#comment-47</guid>
		<description>&lt;p&gt;Thanks, as far as I can tell this worked on OS X 10.5.2 and PostgreSQL 8.3.0.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Thanks, as far as I can tell this worked on OS X 10.5.2 and PostgreSQL 8.3.0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Powers</title>
		<link>http://www.stiefels.net/2007/11/22/building-postgresql-on-leopard/comment-page-1/#comment-46</link>
		<dc:creator>George Powers</dc:creator>
		<pubDate>Sat, 15 Dec 2007 00:27:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.stiefels.net/2007/11/22/building-postgresql-on-leopard/#comment-46</guid>
		<description>&lt;p&gt;Thanks, this worked for me on the current Leopard version (10.5.1) with one small glitch.  I had to su as admin in order for the install to work.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Thanks, this worked for me on the current Leopard version (10.5.1) with one small glitch.  I had to su as admin in order for the install to work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
