PostgreSQL

From Wikipedia, the free encyclopedia - View original article

PostgreSQL
PostgreSQL logo
Developer(s)PostgreSQL Global Development Group
Initial release1 May 1995 (1995-05-01)
Stable release9.3.3,
9.2.7,
9.1.12,
9.0.16,
8.4.20 /
February 20, 2014; 2 days ago (2014-02-20)[1]
Written inC
Operating systemCross-platform
TypeORDBMS
LicensePostgreSQL license[2][3][4]
Websitewww.postgresql.org
 
Jump to: navigation, search
PostgreSQL
PostgreSQL logo
Developer(s)PostgreSQL Global Development Group
Initial release1 May 1995 (1995-05-01)
Stable release9.3.3,
9.2.7,
9.1.12,
9.0.16,
8.4.20 /
February 20, 2014; 2 days ago (2014-02-20)[1]
Written inC
Operating systemCross-platform
TypeORDBMS
LicensePostgreSQL license[2][3][4]
Websitewww.postgresql.org

PostgreSQL, often simply "Postgres", is an open-source object-relational database management system (ORDBMS) with an emphasis on extensibility and standards-compliance. It is released under the PostgreSQL License, a free/open source software license, similar to the MIT License. PostgreSQL is developed by the PostgreSQL Global Development Group, consisting of a handful of volunteers employed and supervised by companies such as Red Hat and EnterpriseDB.[5] It implements the majority of the SQL:2011 standard,[6] is ACID-compliant, is fully transactional (including all DDL statements), has extensible updateable views, data-types, operators, index methods, functions, aggregates, procedural languages,[7] and has a large number of extensions written by third parties. PostgreSQL runs on many operating-systems including Linux, FreeBSD, Solaris, Microsoft Windows and Mac OS X.

The vast majority of Linux distributions have PostgreSQL available in supplied packages. OS X, starting with Lion, has PostgreSQL server as its standard default database in the server edition,[8][9] and PostgreSQL client tools in the desktop edition.

Name[edit]

PostgreSQL's developers pronounce it /ˈpstɡrɛs ˌkjuː ˈɛl/; (Audio sample, 5.6k MP3). It is abbreviated as Postgres, its original name. Because of ubiquitous support for the SQL Standard amongst most relational databases, the community considered changing the name back to Postgres. However, the PostgreSQL Core Team announced in 2007 that the product would continue to use the name PostgreSQL.[10] The name refers to the project's origins as a "post-Ingres" database, being a development from University Ingres DBMS (Ingres being an abbreviation for INteractive Graphics REtrieval System).[11][12]

History[edit]

PostgreSQL evolved from the Ingres project at the University of California, Berkeley. In 1982, the project leader, Michael Stonebraker, left Berkeley to make a proprietary version of Ingres.[11] He returned to Berkeley in 1985 and started a post-Ingres project to address the problems with contemporary database systems that had become increasingly clear during the early 1980s. The new project, POSTGRES, aimed to add the fewest features needed to completely support types.[13] These features included the ability to define types and to fully describe relationships – something used widely before but maintained entirely by the user. In Postgres, the database "understood" relationships, and could retrieve information in related tables in a natural way using rules. Postgres used many of the ideas of Ingres, but not its code.[14]

Starting in 1986, the team published a number of papers describing the basis of the system, and by 1988 had a prototype version. The team released version 1 to a small number of users in June 1989, then version 2 with a re-written rules system in June 1990. Version 3, released in 1991, again re-wrote the rules system, and added support for multiple storage managers and an improved query engine. By 1993 the great number of users began to overwhelm the project with requests for support and features. After releasing version 4—primarily a cleanup—the project ended.

But open-source developers could obtain copies and develop the system further, because Berkeley had released Postgres under an MIT-style license. In 1994, Berkeley graduate students Andrew Yu and Jolly Chen replaced the Ingres-based QUEL query language interpreter with one for the SQL query language, creating Postgres95. The code was released on the web.

In July 1996, Marc Fournier at Hub.Org Networking Services provided the first non-university development server for the open-source development effort. Along with Bruce Momjian and Vadim B. Mikheev, work began to stabilize the code inherited from Berkeley. The first open-source version was released on August 1, 1996.

In 1996, the project was renamed to PostgreSQL to reflect its support for SQL. The first PostgreSQL release formed version 6.0 in January 1997. Since then, the software has been maintained by a group of database developers and volunteers around the world, coordinating via the Internet.

The PostgreSQL project continues to make major releases (approximately annually) and minor "bugfix" releases, all available under the same license. Code comes from contributions from proprietary vendors, support companies, and open-source programmers at large.

Features[edit]

MVCC[edit]

PostgreSQL manages concurrency through a system known as multiversion concurrency control (MVCC), which gives each transaction a "snapshot" of the database, allowing changes to be made without being visible to other transactions until the changes are committed. This largely eliminates the need for read locks, and ensures the database maintains the ACID (atomicity, consistency, isolation, durability) principles in an efficient manner. PostgreSQL offers three levels of transaction isolation: Read Committed, Repeatable Read and Serializable. Because PostgreSQL is immune to dirty reads, requesting a Read Uncommitted transaction isolation level provides read committed instead. Prior to PostgreSQL 9.1, requesting Serializable provided the same isolation level as Repeatable Read. PostgreSQL 9.1 and later support full serializability via the serializable snapshot isolation (SSI) technique.[15]

Procedural languages[edit]

Procedural languages allow developers to extend the database with custom subroutines (functions), often called stored procedures. These functions can be used to build triggers (functions invoked upon modification of certain data) and custom aggregate functions. Procedural languages can also be invoked without defining a function, using the "DO" command at SQL level.

Languages are divided into two groups: "Safe" languages are sandboxed and can be safely used by any user. Procedures written in "unsafe" languages can only be created by superusers, because they allow bypassing the database's security restrictions, but can also access sources external to the database. Some languages like Perl provide both safe and unsafe versions.

PostgreSQL has built-in support for three procedural languages:

In addition, PostgreSQL allows procedural languages to be loaded into the database through extensions. Three language extensions are included with PostgreSQL to support Perl, Python and Tcl. There are external projects to add support for many other languages, including Java, JavaScript (PL/V8), R.

Indexes[edit]

PostgreSQL includes built-in support for regular B-tree and hash indexes, and two types of inverted indexes: generalized search trees (GiST) and generalized inverted indexes (GIN). Hash indexes are implemented, but discouraged because they cannot be recovered after a crash or power loss. In addition, user-defined index methods can be created, although this is quite an involved process. Indexes in PostgreSQL also support the following features:

Triggers[edit]

Triggers are events triggered by the action of SQL DML statements. For example, an INSERT statement might activate a trigger that checks if the values of the statement are valid. Most triggers are only activated by either INSERT or UPDATE statements.

Triggers are fully supported and can be attached to tables. In PostgreSQL 9.0 and above, triggers can be per-column and conditional, in that UPDATE triggers can target specific columns of a table, and triggers can be told to execute under a set of conditions as specified in the trigger's WHERE clause. As of PostgreSQL 9.1, triggers can be attached to views by utilising the INSTEAD OF condition. Views in versions prior to 9.1 can have rules, though. Multiple triggers are fired in alphabetical order. In addition to calling functions written in the native PL/PgSQL, triggers can also invoke functions written in other languages like PL/Python or PL/Perl.

Schemas[edit]

In PostgreSQL, all objects (with the exception of roles and tablespaces) are held within a schema. Schemas effectively act like namespaces, allowing objects of the same name to co-exist in the same database. Schemas are analogous to directories in a file system, except that they cannot be nested, nor is it possible to create a "symbolic link" pointing to another schema or object.

By default, databases are created with the "public" schema, but any additional schemas can be added, and the public schema isn't mandatory. A "search_path" determines the order in which schemas are checked on unqualified objects (those without a prefixed schema), which can be configured on a database or role level. The search path, by default, contains the special schema name of "$user", which first looks for a schema named after the connected database user (e.g. if the user "dave" were connected, it would first look for a schema also named "dave" when referring to any objects). If such a schema is not found, it then proceeds to the next schema. New objects are created in whichever valid schema (one that presently exists) is listed first in the search path.

Data types[edit]

A wide variety of native data types are supported, including:

In addition, users can create their own data types which can usually be made fully indexable via PostgreSQL's GiST infrastructure. Examples of these include the geographic information system (GIS) data types from the PostGIS project for PostgreSQL.

There is also a data type called a "domain", which is the same as any other data type but with optional constraints defined by the creator of that domain. This means any data entered into a column using the domain will have to conform to whichever constraints were defined as part of the domain.

Range Types[edit]

Starting with PostgreSQL 9.2, a data type that represents a range of data can be used which are called range types. These can be discrete ranges (e.g. all integer values 1 to 10) or continuous ranges (e.g. any point in time between 10:00am and 11:00am). The built-in range types available include ranges of integers, big integers, decimal numbers, time stamps (with and without time zone) and dates.

Custom range types can be created to make new types of ranges available, such as IP address ranges using the inet type as a base, or float ranges using the float data type as a base. Range types support inclusive and exclusive range boundaries using the [] and () characters respectively. (e.g. '[4,9)' represents all integers starting from and including 4 up to but not including 9.) Range types are also compatible with existing operators used to check for overlap, containment, right of etc.

User-defined objects[edit]

New types of almost all objects inside the database can be created, including:

Inheritance[edit]

Tables can be set to inherit their characteristics from a "parent" table. Data in child tables will appear to exist in the parent tables, unless data is selected from the parent table using the ONLY keyword, i.e. SELECT * FROM ONLY parent_table. Adding a column in the parent table will cause that column to appear in the child table.

Inheritance can be used to implement table partitioning, using either triggers or rules to direct inserts to the parent table into the proper child tables.

As of 2010 this feature is not fully supported yet—in particular, table constraints are not currently inheritable. All check constraints and not-null constraints on a parent table are automatically inherited by its children. Other types of constraints (unique, primary key, and foreign key constraints) are not inherited.

Inheritance provides a way to map the features of generalization hierarchies depicted in Entity Relationship Diagrams (ERD) directly into the PostgreSQL database.

Rules[edit]

Rules allow the "query tree" of an incoming query to be rewritten. Rules, or more properly, "Query Re-Write Rules", are attached to a table/class and "Re-Write" the incoming DML (select, insert, update, and/or delete) into one or more queries that either replace the original DML statement or execute in addition to it. Query Re-Write occurs after DML statement parsing, but before query planning.

Replication[edit]

Binary replication[edit]

PostgreSQL, beginning from version 9.0, includes built-in binary replication, based on shipping the changes (write-ahead logs) to slave systems asynchronously.

Version 9.0 also introduced the ability to run read-only queries against these replicated slaves, where earlier versions would only allow that after promoting them to be a new master. This allows splitting read traffic among multiple nodes efficiently. Earlier replication software that allowed similar read scaling normally relied on adding replication triggers to the master, introducing additional load onto it.

Beginning from version 9.1, PostgreSQL also includes built-in synchronous replication[16] that ensures that, for each write transaction, the master waits until at least one slave node has written the data to its transaction log. Unlike other database systems, the durability of a transaction (whether it's asynchronous or synchronous) can be specified per-database, per-user, per-session or even per-transaction. This can be useful for work loads that don't require such guarantees, and may not be wanted for all data as it will have some negative effect on performance due to the requirement of the confirmation of the transaction reaching the synchronous standby.

There can be a mixture of synchronous and asynchronous standby servers. A list of synchronous standby servers can be specified in the configuration which determines which servers are candidates for synchronous replication. The first in the list which is currently connected and actively streaming is the one that will be used as the current synchronous server. When this fails, it falls to the next in line.

Synchronous multi-master replication is currently not included in the PostgreSQL core. Postgres-XC which is based on PostgreSQL provides scalable synchronous multi-master replication[17] and is licensed under the BSD license.

The community has also written some tools to make managing replication clusters easier, such as repmgr.

Trigger-based replication[edit]

There are also several asynchronous trigger-based replication packages for PostgreSQL. These remain useful even after introduction of the expanded core capabilities, for situations where binary replication of an entire database cluster isn't the appropriate approach:

Asynchronous notifications[edit]

PostgreSQL provides an asynchronous messaging system that is accessed through the NOTIFY, LISTEN and UNLISTEN commands. A session can issue a NOTIFY command, along with the user-specified channel and an optional payload, to mark a particular event occurring. Other sessions are able to detect these events by issuing a LISTEN command, which can listen to a particular channel. This functionality can be used for a wide variety of purposes, such as letting other sessions know when a table has updated or for separate applications to detect when a particular action has been performed. Such a system prevents the need for continuous polling by applications to see if anything has yet changed, and reducing unnecessary overhead. Notifications are fully transactional, in that messages aren't sent until the transaction they were sent from is committed. This eliminates the problem of messages being sent for an action being performed which is then rolled back.

Many of the connectors for PostgreSQL provide support for this notification system (including libpq, JDBC, Npgsql, psycopg and node.js) so it can be used by external applications.

Security[edit]

Internal[edit]

Security within the database is managed on a per-role-basis. A role is generally regarded to be a user (a role that can log in), or a group (a role which other roles are members of). Permissions can be granted or revoked on any object down to the column level, and can also allow/prevent the creation of new objects at the database, schema or table levels.

The sepgsql extension (provided with PostgreSQL as of version 9.1) provides an additional layer of security by integrating with SELinux. This utilises PostgreSQL's SECURITY LABEL feature.

External[edit]

PostgreSQL natively supports a broad number of authentication mechanisms including:

The GSSAPI, SSPI, Kerberos, peer, ident and certificate methods can also use a specified "map" file that lists which users matched by that authentication system are allowed to connect as a specific database user.

These methods are specified in the cluster's host-based authentication configuration file (pg_hba.conf), which determines what connections are allowed. This allows control over which user can connect to which database, where they can connect from (IP address/IP address range/domain socket), which authentication system will be enforced, and whether the connection must use SSL.

Foreign data wrappers[edit]

As of version 9.1, PostgreSQL can link to other systems to retrieve data via foreign data wrappers (FDWs). These can take the form of any data source, such as a file system, another RDBMS, or a web service. This means regular database queries can use these data sources like regular tables, and even join multiple data sources together.

Other features[edit]

Add-ons[edit]

Upcoming features in 9.4[edit]

In order of commit:

Interfaces[edit]

PostgreSQL has several forms of interface available and is also widely supported among programming language libraries. These include:

Built-in[edit]

External[edit]

Platforms[edit]

Operating systems[edit]

PostgreSQL is available for the following operating systems: Linux (all recent distributions), Windows (Windows 2000 SP4 and later), DragonFly_BSD, FreeBSD, OpenBSD, NetBSD, Mac OS X, AIX, BSD/OS, HP-UX, IRIX, OpenIndiana,[39] OpenSolaris, SCO OpenServer, SCO UnixWare, Solaris and Tru64 Unix. As of 2012, support for the following obsolete systems was removed:[40] DG/UX, NeXTSTEP, SunOS 4, SVR4, Ultrix 4, and Univel. Most other Unix-like systems should also work.

Instruction set architectures[edit]

PostgreSQL works on any of the following instruction set architectures: x86 and x86-64 on Windows and other operatings systems; other than Windows: IA-64 Itanium, PowerPC, PowerPC 64, S/390, S/390x, SPARC, SPARC 64, Alpha, ARMv8-A (64-bit)[41] and older ARM (32-bit), MIPS, MIPSel, M68k, and PA-RISC. It is also known to work on M32R, NS32k, and VAX. In addition to these, it is possible to build PostgreSQL for an unsupported CPU by disabling spinlocks.[42]

Database administration[edit]

Open source front-ends and tools[edit]

psql[edit]

The primary front-end for PostgreSQL is the psql command-line program, which can be used to enter SQL queries directly, or execute them from a file. In addition, psql provides a number of meta-commands and various shell-like features to facilitate writing scripts and automating a wide variety of tasks; for example tab completion of object names and SQL syntax.

pgAdmin[edit]

The pgAdmin package is a free and open source graphical user interface administration tool for PostgreSQL, which is supported on many computer platforms.[43] The program is available in more than a dozen languages. The first prototype, named pgManager, was written for PostgreSQL 6.3.2 from 1998, and rewritten and released as pgAdmin under the GPL License in later months. The second incarnation (named pgAdmin II) was a complete rewrite, first released on January 16, 2002. The third version, pgAdmin III, was originally released under the Artistic License and then released under the same license as PostgreSQL. Unlike prior versions that were written in Visual Basic, pgAdmin III is written in C++, using the wxWidgets framework allowing it to run on most common operating systems.

phpPgAdmin[edit]

phpPgAdmin is a web-based administration tool for PostgreSQL written in PHP and based on the popular phpMyAdmin interface originally written for MySQL administration.[44]

PostgreSQL Studio[edit]

PostgreSQL Studio allows users to perform essential PostgreSQL database development tasks from a web-based console. PostgreSQL Studio allows users to work with cloud databases without the need to open firewalls.[45]

TeamPostgreSQL[edit]

AJAX/JavaScript-driven web interface for PostgreSQL. Allows browsing, maintaining and creating data and database objects via a web browser. The interface offers tabbed SQL editor with auto-completion, row-editing widgets, click-through foreign key navigation between rows and tables, 'favorites' management for commonly used scripts, among other features. Supports SSH for both the web interface and the database connections. Installers are available for Windows, Mac and Linux, as well as a simple cross-platform archive that runs from a script.[46]

LibreOffice/OpenOffice.org Base[edit]

LibreOffice/OpenOffice.org Base can be used as a front-end for PostgreSQL.[47][48]

pgFouine[edit]

The pgFouine PostgreSQL log analyzer generates detailed reports from a PostgreSQL log file and provides VACUUM analysis.[49]

Proprietary front-ends and tools[edit]

A number of companies offer proprietary tools for PostgreSQL. They often consist of a universal core that is adapted for various specific database products. These tools mostly share the administration features with the open source tools but offer improvements in data modeling, importing, exporting or reporting.

Benchmarks and performance[edit]

Many informal performance studies of PostgreSQL have been done.[50] Performance improvements aimed at improving scalability started heavily with version 8.1. Simple benchmarks between version 8.0 and version 8.4 showed that the latter was more than 10 times faster on read-only workloads and at least 7.5 times faster on both read and write workloads.[51]

The first industry-standard and peer-validated benchmark was completed in June 2007 using the Sun Java System Application Server (proprietary version of GlassFish) 9.0 Platform Edition, UltraSPARC T1-based Sun Fire server and Postgres 8.2.[52] This result of 778.14 SPECjAppServer2004 JOPS@Standard compares favourably with the 874 JOPS@Standard with Oracle 10 on an Itanium-based HP-UX system.[50]

In August 2007, Sun submitted an improved benchmark score of 813.73 SPECjAppServer2004 JOPS@Standard. With the system under test at a reduced price, the price/performance improved from $US 84.98/JOPS to $US 70.57/JOPS.[53]

The default configuration of PostgreSQL uses only a small amount of dedicated memory for performance-critical purposes such as caching database blocks and sorting. This limitation is primarily because older operating systems required kernel changes to allow allocating large blocks of shared memory.[54] PostgreSQL.org provides advice on basic recommended performance practice in a wiki.[55]

In April 2012, Robert Haas of EnterpriseDB demonstrated PostgreSQL 9.2's linear CPU scalability using a server with 64 cores.[56]

Prominent users[edit]

PostgreSQL as a service[edit]

Heroku, a platform as a service provider, has supported PostgreSQL[74] since the start in 2007. They offer value-add features like full database "roll-back" (ability to restore a database from any point in time),[75] which is based on WAL-E, open source software developed by Heroku.[76]

In January 2012 EnterpriseDB released a cloud version of both PostgreSQL and their own proprietary Postgres Plus Advanced Server with automated provisioning for failover, replication, load-balancing, and scaling. It runs on Amazon Web Services.[77]

VMware offers vFabric Postgres for private clouds on vSphere since 2012 May.[78]

In 2013 November, Amazon announced that they are adding PostgreSQL to their Relational Database Service offering.[79][80]

Proprietary derivatives and support[edit]

Although the license allowed proprietary products based on Postgres, the code did not develop in the proprietary space at first. The first main offshoot originated when Paula Hawthorn (an original Ingres team member who moved from Ingres) and Michael Stonebraker formed Illustra Information Technologies to make a proprietary product based on Postgres.

In 2000, former Red Hat investors created the company Great Bridge to make a proprietary product based on PostgreSQL and compete against proprietary database vendors. Great Bridge sponsored several PostgreSQL developers and donated many resources back to the community,[81] but by late 2001 closed due to tough competition from companies like Red Hat and to poor market conditions.[82][83]

In 2001 Command Prompt, Inc. released Mammoth PostgreSQL, a proprietary product based on PostgreSQL. In 2008 Command Prompt, Inc. released the source under the original license. Command Prompt, Inc. continues to support the PostgreSQL community actively through developer sponsorships and projects including PL/Perl, PL/php, and hosting of community projects such as the PostgreSQL build farm.

In January 2005, PostgreSQL received backing by database vendor Pervasive Software, known for its Btrieve product which was ubiquitous on the Novell NetWare platform. Pervasive announced commercial support and community participation and achieved some success. In July 2006, Pervasive left the PostgreSQL support market.[84]

In mid-2005 two other companies announced plans to make proprietary products based on PostgreSQL with focus on separate niche markets. EnterpriseDB added functionality to allow applications written to work with Oracle to be more readily run with PostgreSQL. Greenplum contributed enhancements directed at data warehouse and business intelligence applications, including the BizGres project.

In October 2005 John Loiacono, executive vice president of software at Sun Microsystems, commented: "We're not going to OEM Microsoft but we are looking at PostgreSQL right now,"[85] although no specifics were released at that time. By November 2005 Sun had announced support for PostgreSQL.[86] By June 2006 Sun Solaris 10 (6/06 release) shipped with PostgreSQL.

In August 2007, EnterpriseDB announced[87] EnterpriseDB Postgres, a pre-configured distribution of PostgreSQL including many contrib modules and add-on components. EnterpriseDB Postgres was renamed to Postgres Plus in March 2008. Postgres Plus is available in two versions: Postgres Plus Solution Pack[88] (comprising PostgreSQL delivered in a GUI one-click install plus Solution Pack components that include; Postgres Enterprise Manager, Update Monitor, xDB Replication Server, SQL Profiler, SQL Protect, Migration Toolkit and PL/Secure), and Postgres Plus Advanced Server[89] which has all the features of Postgres Plus Solutions Pack plus Oracle compatibility, performance features not available in PostgreSQL, as well as advanced security features not available in PostgreSQL. Both versions are available for download at no cost and are fully supported. The Solution Pack components and Advanced Server are restricted by a "limited use" license for evaluation purposes only unless purchased though a subscription. In 2011, EnterpriseDB announced Postgres Plus Cloud Database,[90] which easily provisions PostgreSQL and Postgres Plus Advanced Server databases (with Oracle compatibility) in single instances, high availability clusters, or development sandboxes for Database-as-a-Service environments.

In 2011, 2ndQuadrant became a Platinum Sponsor of PostgreSQL, in recognition of their long-standing contributions and developer sponsorship. 2ndQuadrant employ one of the largest teams of PostgreSQL contributors and provide professional support for open source PostgreSQL.

Many other companies have used PostgreSQL as the base for their proprietary database projects. e.g. Truviso, Netezza, ParAccel. In many cases the products have been enhanced so much that the software has been forked, though with some features cherry-picked from later releases.

Release history[edit]

ReleaseFirst releaseLatest minor versionLatest releaseMilestones
0.011995-05-010.031995-07-21Initial release as Postgres95
1.01995-09-051.091996-11-04Changed copyright to a more liberal license
6.01997-01-29Name change from Postgres95 to PostgreSQL, unique indexes, pg_dumpall utility, ident authentication.
6.11997-06-086.1.11997-07-22Multi-column indexes, sequences, money data type, GEQO (GEnetic Query Optimizer).
6.21997-10-026.2.11997-10-17JDBC interface, triggers, server programming interface, constraints.
6.31998-03-016.3.21998-04-07SQL92 subselect capability, PL/pgTCL
6.41998-10-306.4.21998-12-20VIEWs and RULEs, PL/pgSQL
6.51999-06-096.5.31999-10-13MVCC, temporary tables, more SQL statement support (CASE, INTERSECT, and EXCEPT)
7.02000-05-087.0.32000-11-11Foreign keys, SQL92 syntax for joins
7.12001-04-137.1.32001-08-15Write-ahead log, Outer joins
7.22002-02-047.2.82005-05-09PL/Python, OIDs no longer required, internationalization of messages
7.32002-11-277.3.212008-01-07Schema, Internationalization
7.42003-11-177.4.302010-10-04Optimization all-round
8.02005-01-198.0.262010-10-04Native server on Microsoft Windows, savepoints, tablespaces, exception handling in functions, point-in-time recovery
8.12005-11-088.1.232010-12-16Performance optimization, two-phase commit, table partitioning, index bitmap scan, shared row locking, roles
8.22006-12-058.2.232011-09-26Performance optimization, online index builds, advisory locks, warm standby
8.32008-02-048.3.232013-02-07Heap-only tuples, full text search, SQL/XML, ENUM types, UUID types
8.42009-07-018.4.202014-02-20Windowing functions, default and variadic parameters for functions, column-level permissions, parallel database restore, per-database collation, common table expressions and recursive queries
9.02010-09-209.0.162014-02-20Built-in binary streaming replication, Hot standby, 64-bit Windows, per-column triggers and conditional trigger execution, exclusion constraints, anonymous code blocks, named parameters, password rules
9.12011-09-129.1.122014-02-20Synchronous replication, per-column collations, unlogged tables, k-nearest-neighbor indexing, serializable snapshot isolation, writeable common table expressions, SE-Linux integration, extensions, SQL/MED attached tables (Foreign Data Wrappers), triggers on views
9.22012-09-109.2.72014-02-20Cascading streaming replication, index-only scans, native JSON support, improved lock management, range types, pg_receivexlog tool, space-partitioned GiST indexes
9.32013-09-099.3.32014-02-20Custom background workers, data checksums, dedicated JSON operators, LATERAL JOIN, faster pg_dump, new pg_isready server monitoring tool, trigger features, view features, writeable foreign tables, materialized views, replication improvements
Community-supported
Community support ended[91]

See also[edit]

References[edit]

  1. ^ "PostgreSQL Maintenance Releases: 9.3.3, 9.2.7, 9.1.12, 9.0.16, and 8.4.20". PostgreSQL. The PostgreSQL Global Development Group. 2014-02-20. Retrieved 2014-02-20. 
  2. ^ "PostgreSQL licence approved by OSI". Crynwr. 2010-02-18. Retrieved 2010-02-18. 
  3. ^ "OSI PostgreSQL licence". Open Source Initiative. 2010-02-20. Retrieved 2010-02-20. 
  4. ^ "License". PostgreSQL Global Development Group. Retrieved 2010-09-20. 
  5. ^ "Contributor Profiles". PostgreSQL. Retrieved December 17, 2011. 
  6. ^ "SQL Conformance". postgresql.org. 2013-04-04. Retrieved 2013-08-28. 
  7. ^ "What is PostgreSQL?". PostgreSQL 9.3.0 Documentation. PostgreSQL Global Development Group. Retrieved 2013-09-20. 
  8. ^ "Lion Server: MySQL not included". 2011-08-04. Retrieved 2011-11-12. 
  9. ^ "OS X Lion Server - Technical Specifications". 2011-08-04. Retrieved 2011-11-12. 
  10. ^ "Project name — statement from the core team". archives.postgresql.org. 2007-11-16. Retrieved 2007-11-16. 
  11. ^ a b Stonebraker, M; Rowe, LA (May 1986). "The design of POSTGRES" (PDF). Proc. 1986 ACM SIGMOD Conference on Management of Data. Washington, DC. Retrieved 2011-12-17. 
  12. ^ http://www.postgresql.org/about/history/
  13. ^ Stonebraker, M; Rowe, LA. "The POSTGRES data model" (PDF). Proceedings of the 13th International Conference on Very Large Data Bases. Brighton, England: Morgan Kaufmann Publishers. pp. 83–96. ISBN 0-934613-46-X. 
  14. ^ Pavel Stehule (9 June 2012). "Historie projektu PostgreSQL" (in Czech). 
  15. ^ Dan R. K. Ports, Kevin Grittner (2012). "Serializable Snapshot Isolation in PostgreSQL". Proceedings of the VLDB Endowment 5 (12): 1850–1861. 
  16. ^ PostgreSQL 9.1 with synchronous replication (news), H Online 
  17. ^ Postgres-XC project page (website), Postgres-XC 
  18. ^ Marit Fischer (2007-11-10). "Backcountry.com finally gives something back to the open source community" (Press release). Backcountry.com. 
  19. ^ "Add a materialized view relations.". 2013-03-04. Retrieved 2013-03-04. 
  20. ^ "Support automatically-updatable views.". 2012-12-08. Retrieved 2012-12-08. 
  21. ^ "Add CREATE RECURSIVE VIEW syntax". 2013-02-01. Retrieved 2013-02-28. 
  22. ^ Momjian, Bruce (2001). "Subqueries". PostgreSQL: Introduction and Concepts. Addison-Wesley. ISBN 0-201-70331-9. Retrieved 2010-09-25. 
  23. ^ "Appendix D. SQL Conformance". PostgreSQL 9 Documentation. PostgreSQL Global Development Group. 2009 [1996]. Retrieved 2013-04-01. 
  24. ^ Bernier, Robert (2 February 2006). "Using Regular Expressions in PostgreSQL". O'Reilly Media. Retrieved 2010-09-25. 
  25. ^ a b "Postgres Plus Downloads". Company website. EnterpriseDB. Retrieved November 12, 2011. 
  26. ^ pgRouting, PostLBS 
  27. ^ "Postgres Enterprise Manager". Company website. EnterpriseDB. Retrieved November 12, 2011. 
  28. ^ ST Links 
  29. ^ "Add support for REFRESH MATERIALIZED VIEW CONCURRENTLY.". 2013-07-16. Retrieved 2013-12-19. 
  30. ^ "Implement the FILTER clause for aggregate function calls.". 2013-07-17. Retrieved 2013-12-19. 
  31. ^ "WITH CHECK OPTION support for auto-updatable VIEWs". 2013-07-18. Retrieved 2013-12-19. 
  32. ^ "Add SQL Standard WITH ORDINALITY support for UNNEST (and any other SRF)". 2013-07-29. Retrieved 2013-12-19. 
  33. ^ "Support multi-argument UNNEST(), and TABLE() syntax for multiple functions.". 2013-11-22. Retrieved 2013-12-19. 
  34. ^ "Add ALTER SYSTEM command to edit the server configuration file.". 2013-12-18. Retrieved 2013-12-19. 
  35. ^ "pg_prewarm, a contrib module for prewarming relationd data.". 2013-12-20. Retrieved 2013-12-20. 
  36. ^ "Support ordered-set (WITHIN GROUP) aggregates.". 2013-12-23. Retrieved 2013-12-23. 
  37. ^ "Add ALTER TABLESPACE ... MOVE command". 2014-01-19. Retrieved 2014-02-06. 
  38. ^ "Introduce replication slots.". 2014-02-01. Retrieved 2014-02-06. 
  39. ^ "oi_151a Release Notes". OpenIndiana. Retrieved 2012-04-07. 
  40. ^ "Git - postgresql.git/commitdiff". Git.postgresql.org. Retrieved 2012-07-08. 
  41. ^ http://lists.debian.org/debian-devel/2012/07/msg00536.html
  42. ^ "Supported Platforms". PostgreSQL Global Development Group. Retrieved 2012-04-06. 
  43. ^ "pgAdmin: PostgreSQL administration and management tools". website. Retrieved November 12, 2011. 
  44. ^ phpPgAdmin Project (2008-04-25). "About phpPgAdmin". Retrieved 2008-04-25. 
  45. ^ PostgreSQL Studio (2013-10-09). "About PostgreSQL Studio". Retrieved 2013-10-09. 
  46. ^ "TeamPostgreSQL website". 2013-10-03. Retrieved 2013-10-03. 
  47. ^ oooforum.org (2010-01-10). "Back Ends for OpenOffice". Retrieved 2011-01-05. 
  48. ^ libreoffice.org (2012-10-14). "Base features". Retrieved 2012-10-14. 
  49. ^ Greg Smith (15 October 2010). "PostgreSQL 9.0 High Performance". free download (Packt Publishing). ISBN 978-1-84951-030-1. 
  50. ^ a b Josh Berkus (2007-07-06). "PostgreSQL publishes first real benchmark". Retrieved 2007-07-10. 
  51. ^ György Vilmos (2009-09-29). "PostgreSQL history". Retrieved 2010-08-28. 
  52. ^ "SPECjAppServer2004 Result". SPEC. 2007-07-06. Retrieved 2007-07-10. 
  53. ^ "SPECjAppServer2004 Result". SPEC. 2007-07-04. Retrieved 2007-09-01. 
  54. ^ "Managing Kernel Resources". PostgreSQL Manual. PostgreSQL.org. Retrieved November 12, 2011. 
  55. ^ Greg Smith, Robert Treat, and Christopher Browne. "Tuning your PostgreSQL server". Wiki. PostgreSQL.org. Retrieved November 12, 2011. 
  56. ^ Robert Haas (2012-04-03). "Did I Say 32 Cores? How about 64?". Retrieved 2012-04-08. 
  57. ^ Eric Lai (2008-05-22). "Size matters: Yahoo claims 2-petabyte database is world's biggest, busiest". Computerworld. 
  58. ^ Thomas Claburn (2008-05-21). "Yahoo Claims Record With Petabyte Database". InformationWeek. 
  59. ^ Emmanuel Cecchet (May 21, 2009). "Building PetaByte Warehouses with Unmodified PostgreSQL". PGCon 2009. Retrieved November 12, 2011. 
  60. ^ "MySpace.com scales analytics for all their friends" (PDF). case study. Aster Data. June 15, 2010. Archived from the original on November 14, 2010. Retrieved November 12, 2011. 
  61. ^ "Last Weekend’s Outage". Blog. Geni. 2011-08-01. 
  62. ^ "Database". Wiki. OpenStreetMap. 
  63. ^ PostgreSQL affiliates .ORG domain, AU: Computer World 
  64. ^ Sony Online opts for open-source database over Oracle, Computer World 
  65. ^ A Web Commerce Group Case Study on PostgreSQL (PDF) (1.2 ed.), PostgreSQL 
  66. ^ "FAQ". Reddit. 2010. Retrieved 2010-08-14. 
  67. ^ "PostgreSQL at Skype". Skype Developer Zone. 2006. Retrieved 2007-10-23. 
  68. ^ "How Much Are You Paying For Your Database?". Sun Microsystems blog. 2007. Retrieved 2007-12-14. 
  69. ^ "Database - MusicBrainz". MusicBrainz Wiki. Retrieved 5 February 2011. 
  70. ^ Duncavage, Daniel P (2010-07-13). "NASA needs Postgres-Nagios help". 
  71. ^ Roy, Gavin M (2010). "PostgreSQL at myYearbook.com" (talk). USA East: PostgreSQL Conference. 
  72. ^ "Keeping Instagram up with over a million new users in twelve hours". Instagram-engineering.tumblr.com. 2011-05-17. Retrieved 2012-07-07. 
  73. ^ "Postgres at Disqus". Retrieved May 24, 2013. 
  74. ^ Alex Williams (1 April 2013). "Heroku Forces Customer Upgrade To Fix Critical PostgreSQL Security Hole". TechCrunch. 
  75. ^ Barb Darrow (11 November 2013). "Heroku gussies up Postgres with database roll-back and proactive alerts". GigaOM. 
  76. ^ Craig Kerstiens (26 September 2013). "WAL-E and Continuous Protection with Heroku Postgres". Heroku blog. 
  77. ^ "EnterpriseDB Offers Up Postgres Plus Cloud Database". Techweekeurope.co.uk. 2012-01-27. Retrieved 2012-07-07. 
  78. ^ Al Sargent (15 May 2012). "Introducing VMware vFabric Suite 5.1: Automated Deployment, New Components, and Open Source Support". VMware blogs. 
  79. ^ Jeff (14 November 2013). "Amazon RDS for PostgreSQL - Now Available". Amazon Web Services Blog. 
  80. ^ Alex Williams (14 November 2013). "PostgreSQL Now Available On Amazon’s Relational Database Service". TechCrunch. 
  81. ^ Maya Tamiya (2001-01-10). "Interview: Bruce Momjian". LWN.net. Retrieved 2007-09-07. 
  82. ^ "Great Bridge ceases operations" (Press release). Great Bridge. 2001-09-06. Retrieved 2007-09-07. 
  83. ^ Nikolai Bezroukov (1 July 2004). "The Sunset of Linux Hype". Portraits of Open Source Pioneers. "NORFOLK, Va., September 6, 2001 -- Great Bridge LLC, the company that pioneered commercial distribution and support of the PostgreSQL open source database, announced today that it has ceased business operations" 
  84. ^ John Farr (2006-07-25). "Open letter to the PostgreSQL Community". Pervasive Software. Archived from the original on 2007-02-25. Retrieved 2007-02-13. 
  85. ^ Rodney Gedda (2005-10-05). "Sun's software chief eyes databases, groupware". Computerworld. Retrieved 2007-02-13. 
  86. ^ "Sun Announces Support for Postgres Database on Solaris 10" (Press release). Sun Microsystems. 2005-11-17. Retrieved 2007-02-13. 
  87. ^ "EnterpriseDB Announces First-Ever Professional-Grade PostgreSQL Distribution for Linux" (Press release). EnterpriseDB. 2007-08-07. Retrieved 2007-08-07. 
  88. ^ "Postgres Plus Solution Pack". EnterpriseDB. Retrieved 2012-07-07. 
  89. ^ "Postgres Plus® Advanced Server". EnterpriseDB. Retrieved 2012-07-07. 
  90. ^ "Postgres Plus® Cloud Database". EnterpriseDB. Retrieved 2012-07-07. 
  91. ^ "Versioning policy". PostgreSQL Global Development Group. Retrieved 2012-01-30. 

Further reading[edit]

PostgreSQL 9.1–9.2
PostgreSQL 9
PostgreSQL 8
PostgreSQL 7

External links[edit]