'organisations': {
'title': 'Organisation',
'objects': lambda u: Organisation.objects.filter(managers=u),
- 'submit_header': 'Before submitting a new Organisation, please verify on the list of <a href="/account/orglist">current organisations</a> if the organisation already exists. If it does, please contact the manager of the organisation to gain permissions.',
+ 'submit_header': 'Before submitting a new Organisation, please verify on the list of <a href="/account/orglist/">current organisations</a> if the organisation already exists. If it does, please contact the manager of the organisation to gain permissions.',
},
}
{%extends "admin/change_list.html"%}
{%block pretitle%}
<p>
- <a href="/admin/mergeorg">Merge two organisations</a>
+ <a href="/admin/mergeorg/">Merge two organisations</a>
</p>
{%endblock%}
<div id="pgSearchNav">
<ul id="pgSearchNavList">
<li>
- <a href="/about/donate">Donate</a>
+ <a href="/about/donate/">Donate</a>
</li>
<li>
- <a href="/about/contact">Contact</a>
+ <a href="/about/contact/">Contact</a>
</li>
</ul>
</div>
<div id="pgCommunity">
<h1>Community</h1>
-<p>PostgreSQL is well supported by its active community. There are more than a dozen <a href="/community/lists">mailing lists</a> available, categorized into topics like administration, announcements, jobs, performance, and SQL. We also have several PostgreSQL User Groups in the world, and there is also an active <a href="/community/irc">IRC</a> community.</p>
+<p>PostgreSQL is well supported by its active community. There are more than a dozen <a href="/community/lists/">mailing lists</a> available, categorized into topics like administration, announcements, jobs, performance, and SQL. We also have several PostgreSQL User Groups in the world, and there is also an active <a href="/community/irc/">IRC</a> community.</p>
-<p>In addition to the resources available on this site, there are also links to <a href="/community/international">international sites</a> that contain PostgreSQL information in various languages. PostgreSQL community <a href="/community/resources">resources</a> are also highlighted in this section of the website.</p>
+<p>In addition to the resources available on this site, there are also links to <a href="/community/international/">international sites</a> that contain PostgreSQL information in various languages. PostgreSQL community <a href="/community/resources/">resources</a> are also highlighted in this section of the website.</p>
</div>
</div>
</form>
</div>
<div id="docNav">
-<a href="/" title="Home">Home</a> → <a href="/docs
" title="Documentation">Documentation</a> → <a href="/docs/manuals" title="Manuals">Manuals</a> → <a href="/docs/{{page.display_version}}/static/{{doc_index_filename}}">PostgreSQL {{page.display_version}}</a>{%if loaddate%} ({{loaddate|date:"Y-m-d H:i:s"}}){%endif%}
+<a href="/" title="Home">Home</a> → <a href="/docs
/" title="Documentation">Documentation</a> → <a href="/docs/manuals/" title="Manuals">Manuals</a> → <a href="/docs/{{page.display_version}}/static/{{doc_index_filename}}">PostgreSQL {{page.display_version}}</a>{%if loaddate%} ({{loaddate|date:"Y-m-d H:i:s"}}){%endif%}
</div>
<div id="docVersions">
This page in other versions:
<div id="pgDocs">
<h1>Documentation</h1>
-<p>There is a wealth of PostgreSQL information available online. This section contains <a href="/docs/manuals">current</a>
-and <a href="/docs/manuals/archive">archived</a> manuals for PostgreSQL users, as well as
-<a href="/docs/faq">frequently asked questions</a>.</p>
+<p>There is a wealth of PostgreSQL information available online. This section contains <a href="/docs/manuals/">current</a>
+and <a href="/docs/manuals/archive/">archived</a> manuals for PostgreSQL users, as well as
+<a href="/docs/faq/">frequently asked questions</a>.</p>
-<p>You can learn <a href="/docs/9.6/static/release-9-6.html">what's new</a> in the latest release, and view a listing of <a href="/docs/books">books</a>
+<p>You can learn <a href="/docs/9.6/static/release-9-6.html">what's new</a> in the latest release, and view a listing of <a href="/docs/books/">books</a>
written about PostgreSQL (some of which are available in their entirety online).
-<a href="https://wiki.postgresql.org">Technical documentation</a> is also available in this section, or you can check <a href="/support/security">Security Information</a>.</p>
+<a href="https://wiki.postgresql.org">Technical documentation</a> is also available in this section, or you can check <a href="/support/security/">Security Information</a>.</p>
</div>
</div>
<li><a href="https://postgrespro.ru/docs/postgresql">Russian</a></li>
</ul>
</dd>
- <dd><p></p><a href="/docs/manuals">More manuals</a></dd>
+ <dd><p></p><a href="/docs/manuals/">More manuals</a></dd>
</dl>
</div>
</div>
<div id="txtFrontUserText">{{quote.quote}}</div>
<div id="txtFrontUserName"><strong>{{quote.who}}, <a href="{{quote.link}}">{{quote.org}}</a></strong></div>
<div id="txtFrontUserLink">
- <img src="/media/img/layout/blt_blu_arrow.png" width="6" height="5" alt="" /><a href="/about/casestudies">Case Studies</a><span class="txtDivider">|</span><a href="/about/quotesarchive" title="See more quotes">More Quotes</a><span class="txtDivider">|</span><a href="/about/users" title="See featured users">Featured Users</a>
+ <img src="/media/img/layout/blt_blu_arrow.png" width="6" height="5" alt="" /><a href="/about/casestudies/">Case Studies</a><span class="txtDivider">|</span><a href="/about/quotesarchive/" title="See more quotes">More Quotes</a><span class="txtDivider">|</span><a href="/about/users/" title="See featured users">Featured Users</a>
</div>
</div>
</div> <!-- pgFrontUserWrap -->
<br />
{%endfor%}
</div>
- <div id="pgFrontLatestReleasesNote"><strong><a href="/download
">Download</a></strong> | <a href="/versions.rss" title="Versions RSS Feed"><img class="pgRSSImage" src="/media/img/misc/ico_rss.png" width="28" height="13" alt="Versions RSS Feed" /></a><br /><a href="/support/versioning">Why should I upgrade?</a><br/><a href="/developer/roadmap/">Upcoming releases</a></div>
+ <div id="pgFrontLatestReleasesNote"><strong><a href="/download
/">Download</a></strong> | <a href="/versions.rss" title="Versions RSS Feed"><img class="pgRSSImage" src="/media/img/misc/ico_rss.png" width="28" height="13" alt="Versions RSS Feed" /></a><br /><a href="/support/versioning/">Why should I upgrade?</a><br/><a href="/developer/roadmap/">Upcoming releases</a></div>
</div> <!-- pgFrontLatestreleases -->
<div id="pgFrontShortcuts">
<h3 class="txtHomeHeader">> Shortcuts</h3>
<a href="/support/security/">Security</a>
</li>
<li>
- <a href="/community/international">International Sites</a>
+ <a href="/community/international/">International Sites</a>
</li>
<li>
- <a href="/community/lists">Mailing Lists</a>
+ <a href="/community/lists/">Mailing Lists</a>
</li>
<li>
<a href="https://wiki.postgresql.org/">Wiki</a>
</li>
<li>
- <a href="/account/submitbug">Report a Bug</a>
+ <a href="/account/submitbug/">Report a Bug</a>
</li>
<li>
<a href="/docs/faq/">FAQs</a>
<h3 class="txtHomeHeader">> Support Us</h3>
<div id="pgFrontSupportUsWrap">
<div id="txtFrontSupportUsText">
- PostgreSQL is free. Please support our work by making a <a href="/about/donate">donation</a>.
+ PostgreSQL is free. Please support our work by making a <a href="/about/donate/">donation</a>.
</div>
</div>
</div> <!-- pgFrontSupportUs -->
<div id="pgFrontNews" class="txtNewsEvent">
<h3 class="txtHomeHeader">
>
- <a href="/about/newsarchive">News</a>
+ <a href="/about/newsarchive/">News</a>
</h3>
<div class="pgNewsEventsWrap">
{% for n in news %}
<img class="pgArrowImage" src="/media/img/layout/blt_blu_arrow.png" width="6" height="5" alt="" />
<ul class="pgRSSBottomList">
<li>
- <a href="/about/newsarchive" title="More News">More</a>
+ <a href="/about/newsarchive/" title="More News">More</a>
</li>
<li>
<a href="/account/news/new/">Submit News</a>
list where they will be publicly archived.</p>
<p>Make sure you are running the latest available minor release for your major
-<a href="/support/versioning">version</a> before reporting a bug. The current
+<a href="/support/versioning/">version</a> before reporting a bug. The current
list of supported versions is
{%for ver in supportedversions%}{{ver}}{%if not forloop.last%}, {%endif%}{%endfor%}.
</p>
accommodate. There are active PostgreSQL instances in production environments that
manage many terabytes of data, as well as clusters managing petabytes. Some general PostgreSQL limits are
included in the table below. </p><div class="informaltable"><a name="table1"></a><table border="0"><colgroup><col /><col /></colgroup><thead><tr><th><span class="bold"><strong>Limit</strong></span></th><th><span class="bold"><strong>Value</strong></span></th></tr></thead><tbody><tr><td>Maximum Database Size</td><td>Unlimited</td></tr><tr><td>Maximum Table Size</td><td>32 TB</td></tr><tr><td>Maximum Row Size</td><td>1.6 TB</td></tr><tr><td>Maximum Field Size</td><td>1 GB</td></tr><tr><td>Maximum Rows per Table</td><td>Unlimited</td></tr><tr><td>Maximum Columns per Table</td><td>250 - 1600 depending on column types</td></tr><tr><td>Maximum Indexes per Table</td><td>Unlimited</td></tr></tbody></table></div>
-<p>PostgreSQL has won <a href="/about/quotesarchive">praise from its users</a> and <a href="/about/awards">industry recognition</a>, including the Linux New Media Award for Best Database System and five time winner of the The Linux Journal Editors' Choice Award for best DBMS.
+<p>PostgreSQL has won <a href="/about/quotesarchive/">praise from its users</a> and <a href="/about/awards/">industry recognition</a>, including the Linux New Media Award for Best Database System and five time winner of the The Linux Journal Editors' Choice Award for best DBMS.
</p>
<h2>Featureful and Standards Compliant</h2><p>PostgreSQL prides itself in standards compliance. Its SQL implementation
<h2>Press Enquiries</h2>
-<p>For press enquiries, please refer to the <a href="/about/press">Press</a> section.
+<p>For press enquiries, please refer to the <a href="/about/press/">Press</a> section.
This section includes information on regional contacts as well.</p>
<h2>Technical Support</h2>
<p>If you are looking for help with PostgreSQL, or this website.</p>
-<p><a href="/support">Community support</a></p>
+<p><a href="/support/">Community support</a></p>
<h2>Webmasters</h2>
href="mailto:funds-group@postgresql.org">PostgreSQL Funds Group</a>.</p>
<h2>Infrastructure Donations</h2>
-<p>There are many companies that donate <a href="/about/servers">servers.</a></p>
+<p>There are many companies that donate <a href="/about/servers/">servers.</a></p>
{%endblock%}
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>
<p><strong>Q: How is PostgreSQL licensed? How much does it cost?</strong><br />
-A: PostgreSQL is released under the OSI-approved PostgreSQL License. There is no fee, even for use in commercial software products. Please see <a href="/about/licence">the PostgreSQL License</a></p>
+A: PostgreSQL is released under the OSI-approved PostgreSQL License. There is no fee, even for use in commercial software products. Please see <a href="/about/licence/">the PostgreSQL License</a></p>
<p><strong>Q: How many developers work on PostgreSQL?</strong><br />
A: About 200. 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: Please contact press@postgresql.org and our press volunteers will try to arrange a contact.</p>
<p><strong>Q: What company owns PostgreSQL?</strong><br />
-A: None. We are an unincorporated association of volunteers and companies who share code under the PostgreSQL License. The PostgreSQL project involves a couple dozen companies who either support PostgreSQL contributors or directly contribute corporate projects to our repository. Some of our major corporate sponsors are on the <a href="/about/sponsors">sponsors page,</a> and there are many more companies who contribute to the project in other ways.</p>
+A: None. We are an unincorporated association of volunteers and companies who share code under the PostgreSQL License. The PostgreSQL project involves a couple dozen companies who either support PostgreSQL contributors or directly contribute corporate projects to our repository. Some of our major corporate sponsors are on the <a href="/about/sponsors/">sponsors page,</a> and there are many more companies who contribute to the project in other ways.</p>
<p><strong>Q: Where can people get support for PostgreSQL?</strong><br />
A: There are several companies which provide paid support for PostgreSQL. Most of them are regional in nature. People should contact the nearest regional contact volunteer to be connected with one or more companies, or check our <a href="/support/professional_support/">professional services list</a>.</p>
<p>If you have a problem that you cannot resolve, you might want to try asking a question in our IRC channel
<a href="irc://irc.freenode.net/postgresql">#postgresql on irc.freenode.net</a>. The channel has many active users,
and it is an entry into participating in the wider PostgreSQL community. Don't forget to consult
-the <a href="/docs">documentation</a> about your problem before asking your question.</p>
+the <a href="/docs/">documentation</a> about your problem before asking your question.</p>
<h2>Other PostgreSQL Related Channels</h2>
<p>PostgreSQL Related Projects:</p>
<p>A PostgreSQL database developer is someone who is actually working on the project, not someone using it to develop
an application or a website. We don't hire programmers, we reach across the Internet, drawing the best database
-developers in the world to PostgreSQL. Read about the <a href="/community/contributors">people behind PostgreSQL</a> and
+developers in the world to PostgreSQL. Read about the <a href="/community/contributors/">people behind PostgreSQL</a> and
check out the <a href="/files/community/conference06/conference_group.html">group picture</a> from the 2006
PostgreSQL Anniversary Summit.
</p>
<h2>What will you find here?</h2>
<p>The information available in this section will mainly interest PostgreSQL developers. Here you'll find the
-<a href="/developer/roadmap">roadmap</a> with current <a href="https://wiki.postgresql.org/wiki/Todo">TODO list</a>, <a href="/developer/coding">coding</a> and
-<a href="/developer/testing">testing</a> information, <a href="/community/lists#developer">mailing lists</a>, and
+<a href="/developer/roadmap/">roadmap</a> with current <a href="https://wiki.postgresql.org/wiki/Todo">TODO list</a>, <a href="/developer/coding/">coding</a> and
+<a href="/developer/testing/">testing</a> information, <a href="/community/lists/#developer">mailing lists</a>, and
the developer <a href="https://wiki.postgresql.org/wiki/Developer_FAQ">FAQ</a>. Keep in mind the information available here is not
necessarily available in the release version of PostgreSQL - it may not yet even be in the development version.
</p>
<h2>Google Summer of Code Program</h2>
-<p>The PostgreSQL Project is a proud participant in Google's Summer of Code program. If you are interested in working on a PostgreSQL related project, please check out our <a href="/developer/summerofcode">Summer of Code</a> page.</p>
+<p>The PostgreSQL Project is a proud participant in Google's Summer of Code program. If you are interested in working on a PostgreSQL related project, please check out our <a href="/developer/summerofcode/">Summer of Code</a> page.</p>
{%endblock%}
would help to make sure we can reach you as needed for project check-ins.</li>
</ul>
-<p>Please also see our additional <a href="/developer/summerofcodeadvice">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
+<p>Please also see our additional <a href="/developer/summerofcodeadvice/">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
<p>We would prefer that development discussion occur on our project mailing lists when possible, with special recognition being given to those students who vet their proposal with community developers before submitting their proposal to Google SoC. This is not required, but can have a large impact on the chances of your proposal being accepted, so please don't be shy. In any case, you will be required to keep open lines of communication with your mentor should you be accepted, so if you have circumstances that may affect this, please explain them up front in your proposal.</p>
Can you supply us with an email/IM/phone method for being contacted, in case of emergency?</li>
</ul>
-<p>Please also see our additional <a href="/developer/summerofcodeadvice">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
+<p>Please also see our additional <a href="/developer/summerofcodeadvice/">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
<p>We would prefer that development discussion occur on our project mailing lists when possible, with special recognition being given to those students who vet their proposal with community developers before submitting their proposal to Google SoC. This is not required, but can have a large impact on the chances of your proposal being accepted, so please don't be shy. In any case, you will be required to keep open lines of communication with your mentor should you be accepted, so if you have circumstances that may affect this, please explain them up front in your proposal.</p>
Can you supply us with an email/IM/phone method for being contacted, in case of emergency?</li>
</ul>
-<p>Please also see our additional <a href="/developer/summerofcodeadvice">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
+<p>Please also see our additional <a href="/developer/summerofcodeadvice/">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
<p>We would prefer that development discussion occur on our project mailing lists when possible, with special recognition being given to those students who vet their proposal with community developers before submitting their proposal to Google SoC. This is not required, but can have a large impact on the chances of your proposal being accepted, so please don't be shy. In any case, you will be required to keep open lines of communication with your mentor should you be accepted, so if you have circumstances that may affect this, please explain them up front in your proposal.</p>
Can you supply us with an email/IM/phone method for being contacted, in case of emergency?</li>
</ul>
-<p>Please also see our additional <a href="/developer/summerofcodeadvice">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
+<p>Please also see our additional <a href="/developer/summerofcodeadvice/">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
<p>We would prefer that development discussion occur on our project mailing lists when possible, with special recognition being given to those students who vet their proposal with community developers before submitting their proposal to Google SoC. This is not required, but can have a large impact on the chances of your proposal being accepted, so please don't be shy. In any case, you will be required to keep open lines of communication with your mentor should you be accepted, so if you have circumstances that may affect this, please explain them up front in your proposal.</p>
Can you supply us with an email/IM/phone method for being contacted, in case of emergency?</li>
</ul>
-<p>Please also see our additional <a href="/developer/summerofcodeadvice">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
+<p>Please also see our additional <a href="/developer/summerofcodeadvice/">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
<p>We would prefer that development discussion occur on our project mailing lists when possible, with special recognition being given to those students who vet their proposal with community developers before submitting their proposal to Google SoC. This is not required, but can have a large impact on the chances of your proposal being accepted, so please don't be shy. In any case, you will be required to keep open lines of communication with your mentor should you be accepted, so if you have circumstances that may affect this, please explain them up front in your proposal.</p>
Can you supply us with an email/IM/phone method for being contacted, in case of emergency?</li>
</ul>
-<p>Please also see our additional <a href="/developer/summerofcodeadvice">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
+<p>Please also see our additional <a href="/developer/summerofcodeadvice/">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
<p>We would prefer that development discussion occur on our project mailing lists when possible, with special recognition being given to those students who vet their proposal with community developers before submitting their proposal to Google SoC. This is not required, but can have a large impact on the chances of your proposal being accepted, so please don't be shy. In any case, you will be required to keep open lines of communication with your mentor should you be accepted, so if you have circumstances that may affect this, please explain them up front in your proposal.</p>
<ul>
<li><a href="/developer/beta/">Current Beta release information</a></li>
<li><a href="/ftp/snapshot/dev/">Download nightly code build</a></li>
- <li><a href="/download/snapshots">Download periodic binary builds</a></li>
+ <li><a href="/download/snapshots/">Download periodic binary builds</a></li>
<li><a href="https://buildfarm.postgresql.org/">Distributed Build Farm</a></li>
</ul>
</p>
<h2>Documentation</h2>
<ul>
- <li><a href="/docs/devel/static">Developer Version of The Docs</a> (<a href="https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=guaibasaurus&dt=latest&stg=make-doc">build log</a>)</li>
+ <li><a href="/docs/devel/static
/">Developer Version of The Docs</a> (<a href="https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=guaibasaurus&dt=latest&stg=make-doc">build log</a>)</li>
</ul>
{%endblock%}
<h3>Source code</h3>
<p>
-The source code can be found in the main <a href="/ftp/source">file browser</a>
+The source code can be found in the main <a href="/ftp/source/">file browser</a>
or you can access the source control repository directly
at <a href="https://git.postgresql.org/gitweb/?p=postgresql.git;a=summary">git.postgresql.org</a>.
Instructions for building from source can be found in the
<h3>Beta/RC Releases and development snapshots (unstable)</h3>
<p>
-There are source code and binary <a href="/download/snapshots">packages</a>
+There are source code and binary <a href="/download/snapshots/">packages</a>
of beta and release candidates, and of the current development code available
for testing and evaluation of new features. Note that these builds should
be used <strong>for testing purposes only</strong>, and not for production systems.
<h2>Build from source</h2>
<p>
-The source code can be found in the main <a href="/ftp/source">file browser</a>.
+The source code can be found in the main <a href="/ftp/source/">file browser</a>.
Instructions for building from source can be found in the
<a href="/docs/current/static/installation.html">documentation</a>.
</p>
<h1>Support</h1>
<p>PostgreSQL has a wide variety of community and commercial support options available for users.
-The <a href="/community">Community</a> section of this website details the support options available to users from the PostgreSQL
-community, including <a href="/community/lists">mailing lists</a> and <a href="/community/irc">IRC</a>.
-And don't forget to read the <a href="/docs/faq">FAQs</a> and <a href="/docs/">documentation</a>.
+The <a href="/community/">Community</a> section of this website details the support options available to users from the PostgreSQL
+community, including <a href="/community/lists/">mailing lists</a> and <a href="/community/irc/">IRC</a>.
+And don't forget to read the <a href="/docs/faq
/">FAQs</a> and <a href="/docs/">documentation</a>.
</p>
<p>Commercial support is also available from one of the many companies providing <a href="/support/professional_support">professional services</a>
<h2>Bug Reporting</h2>
<p>Found a bug in PostgreSQL? Please read over our <a href="/docs/current/static/bug-reporting.html">bug reporting guidelines</a>
-and then report it using our <a href="/account/submitbug">bug reporting form</a>.</p>
+and then report it using our <a href="/account/submitbug/">bug reporting form</a>.</p>
<p>You can see previous bug reports, and track your own on the <a href="/list/pgsql-bugs/">pgsql-bugs@postgresql.org</a> mailing
list.</p>
<h2>What else is included in this release?</h2>
<p>This release also updates four other, minor, security issues which are
-detailed on the <a href="/support/security">security
+detailed on the <a href="/support/security/">security
page</a> and in the release announcement. It includes a number of bug fixes for
PostgreSQL as well, most notably fixes for two potential data corruption issues
with binary replication.</p>
If you wish to report a new security vulnerability in PostgreSQL, please
send an email to
<a href="mailto:security@postgresql.org">security@postgresql.org</a>.
-For reporting non-security bugs, please see the <a href="/account/submitbug">Report a Bug</a> page.
+For reporting non-security bugs, please see the <a href="/account/submitbug/">Report a Bug</a> page.
</p>
{%if version and not version.supported%}
</p>
<p>
-PostgreSQL security updates are primarily made available as <a href="/support/versioning">minor version</a>
+PostgreSQL security updates are primarily made available as <a href="/support/versioning/">minor version</a>
upgrades. You are always advised to use the latest minor version available,
as it will likely also contain other non-security related fixes. All known
security issues are always fixed in the next major release, when it comes out.
</p>
<p>
-Minor releases are numbered by increasing the last part of the version number. Beginning with version 10, this is the second part of the version number, e.g. 10.0 to 10.1; for older versions this is the third part of the version number, e.g. 9.5.3 to 9.5.4. The PostgreSQL team only adds bug fixes to minor releases. All users should upgrade to the most recent minor release as soon as possible. While upgrades always have some risk, PostgreSQL minor releases fix only frequently-encountered, <a href="/support/security">security</a>, and data corruption bugs to reduce the risk associated with upgrading. <em>The community considers not upgrading to be riskier than upgrading</em>.
+Minor releases are numbered by increasing the last part of the version number. Beginning with version 10, this is the second part of the version number, e.g. 10.0 to 10.1; for older versions this is the third part of the version number, e.g. 9.5.3 to 9.5.4. The PostgreSQL team only adds bug fixes to minor releases. All users should upgrade to the most recent minor release as soon as possible. While upgrades always have some risk, PostgreSQL minor releases fix only frequently-encountered, <a href="/support/security/">security</a>, and data corruption bugs to reduce the risk associated with upgrading. <em>The community considers not upgrading to be riskier than upgrading</em>.
</p>
<p>
projects / pgweb.git / commitdiff