VladPolskiy/postgres-web
1
0
Fork 0
mirror of https://github.com/postgres/pgweb.git synced 2025-08-06 09:57:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

General information updates about PostgreSQL 12.

Browse Source 
This adds some more details to features that are available in PostgreSQL 12
on the about page, including updated statistics. Additionally, updates the
press FAQ with information around PostgreSQL 12 (and PostgreSQL 13).
This commit is contained in:
Jonathan S. Katz
2019-09-29 23:43:09 -04:00
parent a8290f017a
commit a0f4dc421a
2 changed files with 17 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
templates/core/about.html
View File

@ -13,7 +13,7 @@
<p>
PostgreSQL comes with <a href="/about/featurematrix/">many features</a> aimed to help developers build applications, administrators to protect data integrity and build fault-tolerant environments, and help you manage your data no matter how big or small the dataset. In addition to being <a href="/about/license/">free and open source</a>, PostgreSQL is highly extensible. For example, you can define your own data types, build out custom functions, even write code from <a href="/docs/current/xplang.html">different programming languages</a> without recompiling your database!
</p>
<p>PostgreSQL tries to conform with the <a href="/docs/current/features.html">SQL standard</a> where such conformance does not contradict traditional features or could lead to poor architectural decisions. Many of the features required by the SQL standard are supported, though sometimes with slightly differing syntax or function. Further moves towards conformance can be expected over time. As of the version 11 release in October 2018, PostgreSQL conforms to at least 160 of the 179 mandatory features for SQL:2011 Core conformance. As of this writing, no relational database meets full conformance with this standard.
<p>PostgreSQL tries to conform with the <a href="/docs/current/features.html">SQL standard</a> where such conformance does not contradict traditional features or could lead to poor architectural decisions. Many of the features required by the SQL standard are supported, though sometimes with slightly differing syntax or function. Further moves towards conformance can be expected over time. As of the version 12 release in October 2019, PostgreSQL conforms to at least 160 of the 179 mandatory features for SQL:2016 Core conformance. As of this writing, no relational database meets full conformance with this standard.
</p>
<p>Below is an inexhaustive list of various features found in PostgreSQL, with more being added in every <a href="/developer/roadmap/">major release</a>:
</p>
@ -67,6 +67,7 @@
<li>Authentication: GSSAPI, SSPI, LDAP, SCRAM-SHA-256, Certificate, and more</li>
<li>Robust access-control system</li>
<li>Column and row-level security</li>
<li>Multi-factor authentication with certificates and an additional method</li>
</ul>
</li>
<li>
@ -74,7 +75,9 @@
<ul>
<li>Stored functions and procedures</li>
<li>Procedural Languages: PL/PGSQL, Perl, Python (and many more)</li>
<li>SQL/JSON path expressions</li>
<li>Foreign data wrappers: connect to other databases or streams with a standard SQL interface</li>
<li>Customizable storage interface for tables</li>
<li>Many extensions that provide additional functionality, including PostGIS</li>
</ul>
</li>
@ -82,6 +85,7 @@
<strong>Internationalisation, Text Search</strong>
<ul>
<li>Support for international character sets, e.g. through ICU collations</li>
<li>Case-insensitive and accent-insensitive collations</li>
<li>Full-text search</li>
</ul>
</li>
@ -134,10 +138,10 @@
<h3>30+ Years Development</h3>
</div>
<div class="col-sm-3 feature-grid">
<h3>400+ Contributors</h3>
<h3>500+ Contributors</h3>
</div>
<div class="col-sm-3 feature-grid">
<h3>45,000+ Commits</h3>
<h3>47,500+ Commits</h3>
</div>
<div class="col-sm-3 feature-grid">
<h3>50+ Local User Groups</h3>
@ -145,10 +149,10 @@
</div>
<div class="row">
<div class="col-sm-3 feature-grid">
<h3>1,100,000+ Lines of C</h3>
<h3>1,250,000+ Lines of C</h3>
</div>
<div class="col-sm-3 feature-grid">
<h3>500+ Events</h3>
<h3>600+ Events</h3>
</div>
<div class="col-sm-3 feature-grid">
<h3>Millions of Happy Users</h3>

17
templates/pages/about/press/faq.html
View File

@ -5,13 +5,13 @@
<h1>Frequently Asked Questions</h1>
<p><strong>Q: What is the current version of PostgreSQL?</strong><br />
A: 11, which was released October 18, 2018. This is our 29th major release in 30 years of development. We release a new version of PostgreSQL every year, which is unique among SQL databases.</p>
A: 12, which was released October 3, 2019. This is our 30th major release in over 30 years of development. We release a new version of PostgreSQL every year, which is unique among SQL databases.</p>
<p><strong>Q: Does the PostgreSQL Project have a Code of Conduct?</strong><br />
A: The PostgreSQL Project prides itself on the quality of our code and our work, and the technical and professional accomplishments of our community. We expect everyone who participates to conduct themselves in a professional manner, acting with common courtesy and in the common interest, with respect for all users and developers. To that end, we established a <a href="https://www.postgresql.org/about/policies/coc/">Code of Conduct</a> for community interaction and participation in the project’s work and the community at large.
<p><strong>Q: What will the version number of the next major release be? What will the version number of the next patch release be?</strong><br />
A: The next major release of PostgreSQL will be version 12, and follows a two-part version numbering scheme. So the first patch release for 11 will be 11.1. The version of PostgreSQL released in 2019 will be version 12.</p>
A: The next major release of PostgreSQL will be version 13, and follows a two-part version numbering scheme. So the first patch release for 12 will be 12.1. The version of PostgreSQL released in 2020 will be version 13.</p>
<p><strong>Q: Why are older versions that are labeled 9.6.6 or 9.5.9?</strong><br />
A: Because of the long history of our project the first two decimals are major releases. Thus 9.6, 9.5 etc. were all major releases. Minor releases have numbers like 9.6.6. Since version 10, the project has adopted a two-part version numbering scheme.</p>
@ -20,10 +20,10 @@ A: Because of the long history of our project the first two decimals are major r
A: PostgreSQL is released under the OSI-approved PostgreSQL Licence. There is no fee, even for use in commercial software products. Please see <a href="/about/licence/">the PostgreSQL Licence</a>.</p>
<p><strong>Q: How many developers work on PostgreSQL?</strong><br />
A: Over 400. As with other open source projects, of course, we depend on hundreds of community members for documentation, translations, advocacy, conferences, website development, infrastructure, and peer-to-peer support.</p>
A: Over 500. As with other open source projects, of course, we depend on hundreds of community members for documentation, translations, advocacy, conferences, website development, infrastructure, and peer-to-peer support.</p>
<p><strong>Q: How many PostgreSQL users are there, worldwide?</strong><br />
A: Our wide distribution through the open source world and liberal licensing make that a difficult question to answer with any accuracy. 451Research estimates that around 30% of tech companies use PostgreSQL for core applications as of 2012, and around 11% of Debian users worldwide install PostgreSQL. Most users get PostgreSQL with a Linux distribution, or with some of the many other products, OSS software, and hardware devices that include PostgreSQL. Many indexes, such as the <a href="https://db-engines.com/en/ranking" target="_blank">DB-Engines Ranking</a>, demonstrate that PostgreSQL adoption continues to grow at a rapid pace, including DB-Engines recognition of PostgreSQL as the <a href="https://db-engines.com/en/blog_post/76">DBMS of the Year in 2017</a>.</p>
A: Our wide distribution through the open source world and liberal licensing make that a difficult question to answer with any accuracy. 451Research estimates that around 30% of tech companies use PostgreSQL for core applications as of 2012, and around 11% of Debian users worldwide install PostgreSQL. Most users get PostgreSQL with a Linux distribution, or with some of the many other products, OSS software, and hardware devices that include PostgreSQL. Many indexes, such as the <a href="https://db-engines.com/en/ranking" target="_blank">DB-Engines Ranking</a>, demonstrate that PostgreSQL adoption continues to grow at a rapid pace, including DB-Engines recognition of PostgreSQL as the <a href="https://db-engines.com/en/blog_post/76">DBMS of the Year in 2017</a> and <a href="https://db-engines.com/en/blog_post/79" target="_blank">2018</a>.</p>
<p><strong>Q: Can we talk to some of your users?</strong><br />
A: Please contact <a href="mailto:press@postgresql.org">press@postgresql.org</a> and our press volunteers will try to arrange a contact.</p>
@ -55,13 +55,12 @@ A: To date there is one: a <a href="http://www.spec.org/jAppServer2004/results/r
<p><strong>Q: When will PostgreSQL get database server clustering?</strong><br />
A: We already have it. Since no one type of clustering satisfies all needs, we have several different clustering tools which take various clustering approaches. The open source projects PostgresXC and Postgres-XL are available, as well as open source forks and proprietary tools such as Greenplum Database, Citus Data and several others. Also, PostgreSQL is supported by filesystem-based clustering systems for failover, including ones from Red Hat, Microsoft, Veritas and Oracle.</p>
<p><strong>Q: When will PostgreSQL 12 come out?</strong><br />
A: The PostgreSQL project begins work on the next version of PostgreSQL in July of each year, and it generally takes 12 to 15 months to work to a release. So expect version 12 around September 2019.</p>
<p><strong>Q: When will PostgreSQL 13 come out?</strong><br />
A: The PostgreSQL project begins work on the next version of PostgreSQL in July of each year, and it generally takes 12 to 15 months to work to a release. So expect version 13 around September 2020.</p>
<p><strong>Q: What features will 12 have?</strong><br />
A: As always, we can't be certain what will go in and what won't; the project has strict quality standards that not all patches can make before deadline. All we can tell you is what's currently being worked on, which includes numerous improvements to the executor, work on pluggable storage, continued improvements to parallelism and partitioning, more improvements to JIT expression compilation as well as stored procedures, and many more. By the time 12 is released, though, this feature may have changed considerably.</p>
<p><strong>Q: What features will 13 have?</strong><br />
A: As always, we can't be certain what will go in and what won't; the project has strict quality standards that not all patches can make before deadline. All we can tell you is what's currently being worked on, which continued work on the pluggable storage interface (including plugins such as zheap or zedstore), native transparent data encryption support, continued improvements to parallelism and partitioning, and many more features. By the time 13 is released, though, this feature may have changed considerably.</p>
<p><strong>Q: How do you pronounce PostgreSQL</strong><br />
A: post-GRES-que-ell, per this <a href="/files/postgresql.mp3">audio file</a>. Many people, however, just say "post-GRES" or "post-GREZ".</p>
{%endblock%}