<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Postgres OnLine Journal - Comments</title>
    <link>http://www.postgresonline.com/journal/</link>
    <description>Postgres OnLine Journal - an In depth look at the PostgreSQL open source database</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.4.1 - http://www.s9y.org/</generator>
    <pubDate>Sun, 26 May 2013 03:37:46 GMT</pubDate>

    <image>
        <url>http://www.postgresonline.com/journal/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: Postgres OnLine Journal - Comments - Postgres OnLine Journal - an In depth look at the PostgreSQL open source database</title>
        <link>http://www.postgresonline.com/journal/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>CRYSTAL34Robles: KNN GIST with a Lateral twist: Coming soon to a database near you</title>
    <link>http://www.postgresonline.com/journal/archives/306-KNN-GIST-with-a-Lateral-twist-Coming-soon-to-a-database-near-you.html#c8249</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/306-KNN-GIST-with-a-Lateral-twist-Coming-soon-to-a-database-near-you.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=306</wfw:comment>

    

    <author>nospam@example.com (CRYSTAL34Robles)</author>
    <content:encoded>
    I treat my future academic career very seriously and I buy essay, just because of this. 
    </content:encoded>

    <pubDate>Sat, 25 May 2013 19:31:34 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/306-guid.html#c8249</guid>
    
</item>
<item>
    <title>Vadim: PostgreSQL 9.3 extension treats for windows users: plV8</title>
    <link>http://www.postgresonline.com/journal/archives/305-PostgreSQL-9.3-extension-treats-for-windows-users-plV8.html#c8128</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/305-PostgreSQL-9.3-extension-treats-for-windows-users-plV8.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=305</wfw:comment>

    

    <author>nospam@example.com (Vadim)</author>
    <content:encoded>
    I use 64-bit version 
    </content:encoded>

    <pubDate>Thu, 23 May 2013 00:00:38 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/305-guid.html#c8128</guid>
    
</item>
<item>
    <title>Regina: PostgreSQL 9.3 extension treats for windows users: plV8</title>
    <link>http://www.postgresonline.com/journal/archives/305-PostgreSQL-9.3-extension-treats-for-windows-users-plV8.html#c8125</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/305-PostgreSQL-9.3-extension-treats-for-windows-users-plV8.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=305</wfw:comment>

    

    <author>nospam@example.com (Regina)</author>
    <content:encoded>
    I&#039;ll check this out.  Are you using the 64-bit or 32-bit?  or it happens on both? 
    </content:encoded>

    <pubDate>Wed, 22 May 2013 21:39:08 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/305-guid.html#c8125</guid>
    
</item>
<item>
    <title>Regina: KNN GIST with a Lateral twist: Coming soon to a database near you</title>
    <link>http://www.postgresonline.com/journal/archives/306-KNN-GIST-with-a-Lateral-twist-Coming-soon-to-a-database-near-you.html#c8105</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/306-KNN-GIST-with-a-Lateral-twist-Coming-soon-to-a-database-near-you.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=306</wfw:comment>

    

    <author>nospam@example.com (Regina)</author>
    <content:encoded>
    Corrected.  Actually ST_MakePoint isn&#039;t right without ST_SetSRID.  I think I had started with plans to do that and then decided on just using ST_GeomFromText (less to explain) 
    </content:encoded>

    <pubDate>Wed, 22 May 2013 10:21:58 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/306-guid.html#c8105</guid>
    
</item>
<item>
    <title>Vadim: PostgreSQL 9.3 extension treats for windows users: plV8</title>
    <link>http://www.postgresonline.com/journal/archives/305-PostgreSQL-9.3-extension-treats-for-windows-users-plV8.html#c8099</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/305-PostgreSQL-9.3-extension-treats-for-windows-users-plV8.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=305</wfw:comment>

    

    <author>nospam@example.com (Vadim)</author>
    <content:encoded>
    server crhashes when an exception is occure or new error is thrown

What steps will reproduce the problem?
1. create function1 which throw new error in its body
2. create function2 which call the first function like plv8.execute(&#039;select * from function1()&#039;)
3. execute function2

What is the expected output? What do you see instead?
I want to catch the error with try/catch


What version of the product are you using? On what operating system?
9.3beta1 
    </content:encoded>

    <pubDate>Wed, 22 May 2013 01:44:37 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/305-guid.html#c8099</guid>
    
</item>
<item>
    <title>Mike Toews: KNN GIST with a Lateral twist: Coming soon to a database near you</title>
    <link>http://www.postgresonline.com/journal/archives/306-KNN-GIST-with-a-Lateral-twist-Coming-soon-to-a-database-near-you.html#c8091</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/306-KNN-GIST-with-a-Lateral-twist-Coming-soon-to-a-database-near-you.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=306</wfw:comment>

    

    <author>nospam@example.com (Mike Toews)</author>
    <content:encoded>
    &quot;ST_GeomFromText(234054, 902182)&quot; should be corrected to &quot;ST_MakePoint(234054, 902182)&quot; 
    </content:encoded>

    <pubDate>Tue, 21 May 2013 21:40:10 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/306-guid.html#c8091</guid>
    
</item>
<item>
    <title>Regina: Which PostGIS should you use with PostgreSQL 9.3</title>
    <link>http://www.postgresonline.com/journal/archives/303-Which-PostGIS-should-you-use-with-PostgreSQL-9.3.html#c7488</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/303-Which-PostGIS-should-you-use-with-PostgreSQL-9.3.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=303</wfw:comment>

    

    <author>nospam@example.com (Regina)</author>
    <content:encoded>
    We are still on a different release cycle mostly because our code base is fairly huge for a contrib module.  Having to match release cycle with PostgreSQL would be very frustrating for us.  We have enough fighting amongst ourselves when to release without having another group controlling us.  

That said as dusty mentioned, the licensing is incompatible.  But really the main reason is our module is too big to fit in PostgreSQL release cycle.  

The other issue is a lot of GIS folks want newer features without having to upgrade PostgreSQL and are also tied to 3rd party GIS tools that only support X version etc.  Being part of PostgreSQL would force us into a 1 version of PostGIS per version of PostgreSQL which I think would make everyone unhappier. 

As much as I like to complain, I&#039;d rather distros package more than one version of PostGIS per PostgreSQL release rather than we being forced into a one PostGIS version per PostgreSQL. 
    </content:encoded>

    <pubDate>Tue, 30 Apr 2013 13:45:46 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/303-guid.html#c7488</guid>
    
</item>
<item>
    <title>dustymugs: Which PostGIS should you use with PostgreSQL 9.3</title>
    <link>http://www.postgresonline.com/journal/archives/303-Which-PostGIS-should-you-use-with-PostgreSQL-9.3.html#c7485</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/303-Which-PostGIS-should-you-use-with-PostgreSQL-9.3.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=303</wfw:comment>

    

    <author>nospam@example.com (dustymugs)</author>
    <content:encoded>
    PostGIS can&#039;t be part of PostgreSQL (in contrib) due to non-compatible licenses.  PostgreSQL has its own BSD/MIT-like license while PostGIS is GPL v2. 
    </content:encoded>

    <pubDate>Tue, 30 Apr 2013 12:39:38 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/303-guid.html#c7485</guid>
    
</item>
<item>
    <title>Grazvydas: Which PostGIS should you use with PostgreSQL 9.3</title>
    <link>http://www.postgresonline.com/journal/archives/303-Which-PostGIS-should-you-use-with-PostgreSQL-9.3.html#c7481</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/303-Which-PostGIS-should-you-use-with-PostgreSQL-9.3.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=303</wfw:comment>

    

    <author>nospam@example.com (Grazvydas)</author>
    <content:encoded>
    I think PostGIS became mature enough to become aligned to PostgreSQL release cycle. How about to move it to PG contrib or find another way to integrate it to the core PG?
Historical reasons of developing PostGIS separately become less and less attractive - you described reasons of that.
On the other hand - PostGIS is huge value to PostgreSQL. Why PG would insist to keep PostGIS separated? 
    </content:encoded>

    <pubDate>Tue, 30 Apr 2013 08:56:03 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/303-guid.html#c7481</guid>
    
</item>
<item>
    <title>Moses: Which PostGIS should you use with PostgreSQL 9.3</title>
    <link>http://www.postgresonline.com/journal/archives/303-Which-PostGIS-should-you-use-with-PostgreSQL-9.3.html#c7463</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/303-Which-PostGIS-should-you-use-with-PostgreSQL-9.3.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=303</wfw:comment>

    

    <author>nospam@example.com (Moses)</author>
    <content:encoded>
    I&#039;m fine with it. No problem when postgresql and postgis versions going hand in hand. Since we anyway updating to every new version, because there is so much cool stuff. 
    </content:encoded>

    <pubDate>Tue, 30 Apr 2013 01:15:14 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/303-guid.html#c7463</guid>
    
</item>
<item>
    <title>Bruce: Word Play with Spatial SQL</title>
    <link>http://www.postgresonline.com/journal/archives/302-Word-Play-with-Spatial-SQL.html#c7278</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/302-Word-Play-with-Spatial-SQL.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=302</wfw:comment>

    

    <author>nospam@example.com (Bruce)</author>
    <content:encoded>
    Nothing is as easy as it seems.  Take the phrase &quot;Dot you i&#039;s and cross your t&#039;s&quot;  The dot above an i must be coded as a separate path which is different from a donut hole like in the letter e.  If a t is coded as two separate paths the geometries will intersect and not be valid.  Both cases are handled easily in SVG.
The nasty coding is converting ellipses and bezier curves (very common in fonts/SVG) to WKT geometries. 
    </content:encoded>

    <pubDate>Mon, 22 Apr 2013 11:04:57 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/302-guid.html#c7278</guid>
    
</item>
<item>
    <title>Regina: ODBC Foreign Data wrapper to query SQL Server on Window - Part 2</title>
    <link>http://www.postgresonline.com/journal/archives/249-ODBC-Foreign-Data-wrapper-to-query-SQL-Server-on-Window-Part-2.html#c7128</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/249-ODBC-Foreign-Data-wrapper-to-query-SQL-Server-on-Window-Part-2.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=249</wfw:comment>

    

    <author>nospam@example.com (Regina)</author>
    <content:encoded>
    Unfortunately I don&#039;t think so.  Or at least not last time I tried. I tried a couple of months ago and it wouldn&#039;t compile against.  9.2 changed FDW in a major way whcih broke a lot of past FDWs.  I was trying to see if I could patch the code up to work with 9.2 but got as far as getting it to compile, but then it failed on load.  Then I had to move on to something else.  I&#039;ll check if its been updated recently. 
    </content:encoded>

    <pubDate>Sun, 14 Apr 2013 17:16:42 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/249-guid.html#c7128</guid>
    
</item>
<item>
    <title>Rytis: ODBC Foreign Data wrapper to query SQL Server on Window - Part 2</title>
    <link>http://www.postgresonline.com/journal/archives/249-ODBC-Foreign-Data-wrapper-to-query-SQL-Server-on-Window-Part-2.html#c7116</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/249-ODBC-Foreign-Data-wrapper-to-query-SQL-Server-on-Window-Part-2.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=249</wfw:comment>

    

    <author>nospam@example.com (Rytis)</author>
    <content:encoded>
    Hi,
Would it  be possible to post the ODBC FDW binaries for windows 64bit PostgreSQL 9.2?

I&#039;ve tried to compile myself with MinGW but after two long nights this seems to be way out of my league:)

Rytis 
    </content:encoded>

    <pubDate>Sun, 14 Apr 2013 05:37:39 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/249-guid.html#c7116</guid>
    
</item>
<item>
    <title>Regina Obe: Using PgAdmin PLPgSQL Debugger</title>
    <link>http://www.postgresonline.com/journal/archives/214-Using-PgAdmin-PLPgSQL-Debugger.html#c7103</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/214-Using-PgAdmin-PLPgSQL-Debugger.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=214</wfw:comment>

    

    <author>nospam@example.com (Regina Obe)</author>
    <content:encoded>
    I presume you are running the 32-bit version of PostgreSQL since you are referencing a 32-bit version?

You shouldn&#039;t need all that path stuff in shared_preload_libraries, just the dll name should be sufficient since its going to look in lib of the postgresql instance.

If for some reason you need the full path, change the slashes from \ to / .  PostgreSQL never seems to work right in a lot of places with windows style slashes 
    </content:encoded>

    <pubDate>Sat, 13 Apr 2013 17:32:39 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/214-guid.html#c7103</guid>
    
</item>
<item>
    <title>Regina: pgRouting windows binaries for PostgreSQL 9.2 32-bit and 64-bit</title>
    <link>http://www.postgresonline.com/journal/archives/300-pgRouting-windows-binaries-for-PostgreSQL-9.2-32-bit-and-64-bit.html#c7102</link>
            <category></category>
    
    <comments>http://www.postgresonline.com/journal/archives/300-pgRouting-windows-binaries-for-PostgreSQL-9.2-32-bit-and-64-bit.html#comments</comments>
    <wfw:comment>http://www.postgresonline.com/journal/wfwcomment.php?cid=300</wfw:comment>

    

    <author>nospam@example.com (Regina)</author>
    <content:encoded>
    David,

Of course.  Started a series on BostonGIS.  Here is first of what I hope to be several:

http://www.bostongis.com/PrinterFriendly.aspx?content_name=pgrouting_osm2po_1 
    </content:encoded>

    <pubDate>Sat, 13 Apr 2013 17:19:46 -0400</pubDate>
    <guid isPermaLink="false">http://www.postgresonline.com/journal/archives/300-guid.html#c7102</guid>
    
</item>

</channel>
</rss>