<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jrapdx3</author><text>Remarkable similar to my own history with Postgresql, which I started using in ~1998 at the time of their first public release.  Postgresql documentation has indeed been the exemplar for all software, open source or not.  It&amp;#x27;s been the SQL textbook I&amp;#x27;ve relied on.&lt;p&gt;With the steady addition of features, it&amp;#x27;s gotten much more complex, and there will come a time when using just the documentation won&amp;#x27;t be enough to learn how to use Postgresql to full advantage.  With release of 9.5 we might be there now.&lt;p&gt;Perhaps the logical extension of the documentation is some form of coursework to enable users to learn the DB systematically.  I haven&amp;#x27;t looked into it, this might already be offered.</text><parent_chain><item><author>saosebastiao</author><text>Whenever there is a version update, I can&amp;#x27;t help but be grateful for the documentation ethic of Postgres. For the vast majority of my projects I have to wade through unaffiliated and incomplete blog tutorials that may or may not be relevant to the version I&amp;#x27;m trying to use. With anything related to Postgres, I may read about something on a blog post, but I &lt;i&gt;always&lt;/i&gt; know that I can count on the Postgres documentation if I need supplemental information, or sometimes I&amp;#x27;ll skip the post and go straight to the official docs. The PostgreSQL project, in my mind, sets the standard globally for software documentation.&lt;p&gt;I should add that Postgres was the first database I ever used, and I literally learned pretty much everything I know about Postgres, SQL, as well as Relational and Set Logic from the official docs. And that was with no background in software development and an undergraduate business degree with Excel being my most technologically advanced toolset. &lt;i&gt;That&lt;/i&gt; is a documentation success story.</text></item></parent_chain></comment><story><title>PostgreSQL 9.5: UPSERT, Row Level Security, and Big Data</title><url>http://www.postgresql.org/about/news/1636/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ptman</author><text>I call that BSD culture</text><parent_chain><item><author>saosebastiao</author><text>Whenever there is a version update, I can&amp;#x27;t help but be grateful for the documentation ethic of Postgres. For the vast majority of my projects I have to wade through unaffiliated and incomplete blog tutorials that may or may not be relevant to the version I&amp;#x27;m trying to use. With anything related to Postgres, I may read about something on a blog post, but I &lt;i&gt;always&lt;/i&gt; know that I can count on the Postgres documentation if I need supplemental information, or sometimes I&amp;#x27;ll skip the post and go straight to the official docs. The PostgreSQL project, in my mind, sets the standard globally for software documentation.&lt;p&gt;I should add that Postgres was the first database I ever used, and I literally learned pretty much everything I know about Postgres, SQL, as well as Relational and Set Logic from the official docs. And that was with no background in software development and an undergraduate business degree with Excel being my most technologically advanced toolset. &lt;i&gt;That&lt;/i&gt; is a documentation success story.</text></item></parent_chain></comment><story><title>PostgreSQL 9.5: UPSERT, Row Level Security, and Big Data</title><url>http://www.postgresql.org/about/news/1636/</url></story>