Jump to content

PostgreSQL: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
→Release history: "ability to refresh materialized views" better?
Line 48: Line 48:
PostgreSQL evolved from the [[Ingres (database)|Ingres]] project at the University of California, Berkeley. In 1982, the leader of the Ingres team, [[Michael Stonebraker]], left Berkeley to make a proprietary version of Ingres.<ref name="design" /> 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 [[data type|types]].<ref name="Stonebraker" /> These features included the ability to define types and to fully describe relationships{{snd}} 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.<ref name="pavel-history" />
PostgreSQL evolved from the [[Ingres (database)|Ingres]] project at the University of California, Berkeley. In 1982, the leader of the Ingres team, [[Michael Stonebraker]], left Berkeley to make a proprietary version of Ingres.<ref name="design" /> 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 [[data type|types]].<ref name="Stonebraker" /> These features included the ability to define types and to fully describe relationships{{snd}} 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.<ref name="pavel-history" />


Starting in 1986, the POSTGRES team published a number of papers describing the basis of the system, and by 1987 had a prototype version shown at the 1988 [[ACM SIGMOD Conference]]. 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 manager]]s{{citation needed|date=February 2017}} 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.2<ref name="University POSTGRES" /> on June 30, 1994{{snd}} primarily a cleanup{{snd}} the project ended. Berkeley had released POSTGRES under an [[MIT License|MIT-style license]], which enabled other developers to use the code for any use. At the time, POSTGRES used an Ingres-influenced [[POSTQUEL query language]] interpreter, which could be interactively used with a [[console application]] named <tt>monitor</tt>.<!-- See http://db.cs.berkeley.edu/postgres-v4r2/postgres-setup.ps -->
Starting in 1986, the POSTGRES team published a number of papers describing the basis of the system, and by 1987 had a prototype version shown at the 1988 [[ACM SIGMOD Conference]]. 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{{citation needed|date=February 2017}} 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.2<ref name="University POSTGRES" /> on June 30, 1994{{snd}} primarily a cleanup{{snd}} the project ended. Berkeley had released POSTGRES under an [[MIT License|MIT-style license]], which enabled other developers to use the code for any use. At the time, POSTGRES used an Ingres-influenced [[POSTQUEL query language]] interpreter, which could be interactively used with a [[console application]] named <tt>monitor</tt>.<!-- See http://db.cs.berkeley.edu/postgres-v4r2/postgres-setup.ps -->


In 1994, Berkeley graduate students Andrew Yu and Jolly Chen replaced the POSTQUEL query language interpreter with one for the SQL query language, creating Postgres95. The front-end program <tt>monitor</tt> was also replaced by <tt>psql</tt>. Yu and Chen announced the first version (0.01) to [[beta tester]]s on May 5, 1995.<!-- email lists are not citeable, however see message 3165 of |url=http://db.cs.berkeley.edu/postgres-v4r2/mail-archive/1995.05.tar.gz |title=Announcement: Postgres95 Beta |author=Andrew K. Yu |date=1 May 1995 --> Version 1.0 of Postgres95 was announced on September 5, 1995, with a more liberal license that enabled the software to be freely modifiable for any purpose.<!-- message 3279 of |url=http://db.cs.berkeley.edu/postgres-v4r2/mail-archive/1995.09.tar.gz |title=ANNOUNCEMENT for postgres95 version 1.0 |author=Jolly Chen |date=September 5, 1995 -->
In 1994, Berkeley graduate students Andrew Yu and Jolly Chen replaced the POSTQUEL query language interpreter with one for the SQL query language, creating Postgres95. The front-end program <tt>monitor</tt> was also replaced by <tt>psql</tt>. Yu and Chen announced the first version (0.01) to [[beta tester]]s on May 5, 1995.<!-- email lists are not citeable, however see message 3165 of |url=http://db.cs.berkeley.edu/postgres-v4r2/mail-archive/1995.05.tar.gz |title=Announcement: Postgres95 Beta |author=Andrew K. Yu |date=1 May 1995 --> Version 1.0 of Postgres95 was announced on September 5, 1995, with a more liberal license that enabled the software to be freely modifiable for any purpose.<!-- message 3279 of |url=http://db.cs.berkeley.edu/postgres-v4r2/mail-archive/1995.09.tar.gz |title=ANNOUNCEMENT for postgres95 version 1.0 |author=Jolly Chen |date=September 5, 1995 -->

Revision as of 01:10, 10 March 2018

PostgreSQL
Developer(s)PostgreSQL Global Development Group
Initial release8 July 1996;
28 years ago (1996-07-08)[1]
Stable release
10.3 / 1 March 2018;
6 years ago (2018-03-01)[2]
Repository
Written inC (pgAdmin: wxWidgets[3])
Operating systemMost Unix-like operating systems and Windows
TypeORDBMS
LicensePostgreSQL License (free and open-source, permissive)[4][5][6]
Websitepostgresql.org
PostgreSQL License[4]
Debian FSG compatibleYes[7][8]
FSF approvedYes[9]
OSI approvedYes[6]
GPL compatibleYes
CopyleftNo
Linking from code with a different licenceYes
Websitepostgresql.org/about/licence

PostgreSQL, often simply Postgres, is an object-relational database management system (ORDBMS) with an emphasis on extensibility and standards compliance. As a database server, its primary functions are to store data securely and return that data in response to requests from other software applications. It can handle workloads ranging from small single-machine applications to large Internet-facing applications (or for data warehousing) with many concurrent users; on macOS Server, PostgreSQL is the default database;[10][11][12] and it is also available for Microsoft Windows and Linux (supplied in most distributions).

PostgreSQL is ACID-compliant and transactional. PostgreSQL has updatable views and materialized views, triggers, foreign keys; supports functions and stored procedures, and other expandability.[13]

PostgreSQL is developed by the PostgreSQL Global Development Group, a diverse group of many companies and individual contributors.[14] It is free and open-source, released under the terms of the PostgreSQL License, a permissive software license.

Name

PostgreSQL's developers pronounce PostgreSQL as /ˈpoʊstɡrɛs ˌkjuː ˈɛl/.[15] It is abbreviated as Postgres because of ubiquitous support for (at least early version of) the SQL standard among most relational databases. PostgreSQL implements features of old and up to later versions. Originally named POSTGRES, the name (Post Ingres) refers to the project's origins in that database which was developed at University of California, Berkeley.[16][17] 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.[18]

History

PostgreSQL evolved from the Ingres project at the University of California, Berkeley. In 1982, the leader of the Ingres team, Michael Stonebraker, left Berkeley to make a proprietary version of Ingres.[16] 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.[19] 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.[20]

Starting in 1986, the POSTGRES team published a number of papers describing the basis of the system, and by 1987 had a prototype version shown at the 1988 ACM SIGMOD Conference. 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[citation needed] 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.2[21] on June 30, 1994 – primarily a cleanup – the project ended. Berkeley had released POSTGRES under an MIT-style license, which enabled other developers to use the code for any use. At the time, POSTGRES used an Ingres-influenced POSTQUEL query language interpreter, which could be interactively used with a console application named monitor.

In 1994, Berkeley graduate students Andrew Yu and Jolly Chen replaced the POSTQUEL query language interpreter with one for the SQL query language, creating Postgres95. The front-end program monitor was also replaced by psql. Yu and Chen announced the first version (0.01) to beta testers on May 5, 1995. Version 1.0 of Postgres95 was announced on September 5, 1995, with a more liberal license that enabled the software to be freely modifiable for any purpose.

On July 8, 1996, Marc Fournier at Hub.org Networking Services provided the first non-university development server for the open-source development effort.[1] With the participation of Bruce Momjian and Vadim B. Mikheev, work began to stabilize the code inherited from Berkeley.

In 1996, the project was renamed to PostgreSQL to reflect its support for SQL. The online presence at the website PostgreSQL.org began on October 22, 1996.[22] The first PostgreSQL release formed version 6.0 on January 29, 1997. Since then a group of developers and volunteers around the world have maintained the software as The PostgreSQL Global Development Group.[14]

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

Development

PostgreSQL does not have a bug tracker (while it "has a bug-submission form that feeds into the pgsql-bugs mailing list"), making it quite difficult to know the status of bugs.[23]

Multiversion concurrency control (MVCC)

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. PostgreSQL supports full serializability via the serializable snapshot isolation (SSI) technique.[24]

Storage and replication

Replication

PostgreSQL includes built-in binary replication based on shipping the changes (write-ahead logs) to replica nodes asynchronously, with the ability to run read-only queries against these replicated nodes. 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.

PostgreSQL also includes built-in synchronous replication[25] that ensures that, for each write transaction, the master waits until at least one replica node has written the data to its transaction log. Unlike other database systems, the durability of a transaction (whether it is asynchronous or synchronous) can be specified per-database, per-user, per-session or even per-transaction. This can be useful for work loads that do not 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,[26] available in version 1.2.1 (April 2015 version) is licensed under the same license as PostgreSQL. A similar project is called Postgres-XL. Postgres-R is yet another older fork.[27] Bi-directional replication (BDR) is an asynchronous multi-master replication system for PostgreSQL.[28]

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

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 is not the appropriate approach:

Indexes

PostgreSQL includes built-in support for regular B-tree and hash indexes, and four index access methods: generalized search trees (GiST), generalized inverted indexes (GIN), Space-Partitioned GiST (SP-GiST)[30] and Block Range Indexes (BRIN). Hash indexes are implemented, but discouraged because they cannot be recovered after a crash or power loss, although this will no longer be the case from version 10.[31] In addition, user-defined index methods can be created, although this is quite an involved process. Indexes in PostgreSQL also support the following features:

  • Expression indexes can be created with an index of the result of an expression or function, instead of simply the value of a column.
  • Partial indexes, which only index part of a table, can be created by adding a WHERE clause to the end of the CREATE INDEX statement. This allows a smaller index to be created.
  • The planner is capable of using multiple indexes together to satisfy complex queries, using temporary in-memory bitmap index operations (useful in data warehousing applications for joining a large fact table to smaller dimension tables such as those arranged in a star schema).
  • k-nearest neighbors (k-NN) indexing (also referred to KNN-GiST[32]) provides efficient searching of "closest values" to that specified, useful to finding similar words, or close objects or locations with geospatial data. This is achieved without exhaustive matching of values.
  • In PostgreSQL 9.2 and later, index-only scans often allow the system to fetch data from indexes without ever having to access the main table.
  • PostgreSQL 9.5 introduced Block Range Indexes (BRIN).

Schemas

In PostgreSQL, a schema holds all objects (with the exception of roles and tablespaces). Schemas effectively act like namespaces, allowing objects of the same name to co-exist in the same database. By default, newly created databases have a schema called "public", but any additional schemas can be added, and the public schema isn't mandatory.

A "search_path" setting determines the order in which PostgreSQL checks schemas for unqualified objects (those without a prefixed schema). By default, it is set to "$user, public" ($user refers to the currently connected database user). This default can be set on a database or role level, but as it is a session parameter, it can be freely changed (even multiple times) during a client session, affecting that session only.

Non-existent schemas listed in search_path are silently skipped during objects lookup.

New objects are created in whichever valid schema (one that presently exists) appears first in the search_path.Schema is an outline of database.

Data types

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

  • Boolean
  • Arbitrary precision numerics
  • Character (text, varchar, char)
  • Binary
  • Date/time (timestamp/time with/without timezone, date, interval)
  • Money
  • Enum
  • Bit strings
  • Text search type
  • Composite
  • HStore (an extension enabled key-value store within PostgreSQL)
  • Arrays (variable length and can be of any data type, including text and composite types) up to 1 GB in total storage size
  • Geometric primitives
  • IPv4 and IPv6 addresses
  • CIDR blocks and MAC addresses
  • XML supporting XPath queries
  • UUID
  • JSON (since version 9.2), and a faster binary JSONB (since version 9.4; not the same as BSON[33])

In addition, users can create their own data types which can usually be made fully indexable via PostgreSQL's indexing infrastructures – GiST, GIN, SP-GiST. 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.

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:00 am and 11:00 am). 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

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

  • Casts
  • Conversions
  • Data types
  • Domains
  • Functions, including aggregate functions and window functions
  • Indexes including custom indexes for custom types
  • Operators (existing ones can be overloaded)
  • Procedural languages

Inheritance

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 (ERDs) directly into the PostgreSQL database.

Other storage features

  • Referential integrity constraints including foreign key constraints, column constraints, and row checks
  • Binary and textual large-object storage
  • Tablespaces
  • Per-column collation
  • Online backup
  • Point-in-time recovery, implemented using write-ahead logging
  • In-place upgrades with pg_upgrade for less downtime (supports upgrades from 8.3.x and later)

Control and connectivity

Foreign data wrappers

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

Interfaces

PostgreSQL has several interfaces available and is also widely supported among programming language libraries. Built-in interfaces include libpq (PostgreSQL's official C application interface) and ECPG (an embedded C system). External interfaces include:

  • libpqxx: C++ interface
  • PostgresDAC: PostgresDAC (for Embarcadero RadStudio/Delphi/CBuilder XE-XE3)
  • DBD::Pg: Perl DBI driver
  • JDBC: JDBC interface
  • Lua: Lua interface
  • Npgsql: .NET data provider
  • ST-Links SpatialKit: Link Tool to ArcGIS
  • PostgreSQL.jl: Julia interface
  • node-postgres: Node.js interface
  • pgoledb: OLEDB interface
  • psqlODBC: ODBC interface
  • psycopg2:[35] Python interface (also used by HTSQL)
  • pgtclng: Tcl interface
  • pyODBC: Python library
  • php5-pgsql: PHP driver based on libpq
  • postmodern: A Common Lisp interface
  • pq: A pure Go PostgreSQL driver for the Go database/sql package. The driver passes the compatibility test suite.[36]
  • RPostgreSQL: R interface[37]
  • dpq: D interface to libpq
  • epgsql: Erlang interface

Procedural languages

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:

  • Plain SQL (safe). Simpler SQL functions can get expanded inline into the calling (SQL) query, which saves function call overhead and allows the query optimizer to "see inside" the function.
  • PL/pgSQL (safe), which resembles Oracle's PL/SQL procedural language and SQL/PSM.
  • C (unsafe), which allows loading custom shared libraries into the database. Functions written in C offer the best performance, but bugs in code can crash and potentially corrupt the database. Most built-in functions are written in C.

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,[38] including Java, JavaScript (PL/V8), R, Ruby, and others.

Triggers

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. 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. Triggers can be attached to views by using the INSTEAD OF condition. 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.

Asynchronous notifications

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 are not 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.

Rules

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.

Other querying features

  • Transactions
  • Full text search
  • Views
    • Materialized views[39]
    • Updateable views[40]
    • Recursive views[41]
  • Inner, outer (full, left and right), and cross joins
  • Sub-selects
    • Correlated sub-queries[42]
  • Regular expressions[43]
  • Common table expressions and writable common table expressions
  • Encrypted connections via TLS (current versions do not use vulnerable SSL, even with that configuration option)[44]
  • Domains
  • Savepoints
  • Two-phase commit
  • TOAST (The Oversized-Attribute Storage Technique) is used to transparently store large table attributes (such as big MIME attachments or XML messages) in a separate area, with automatic compression.
  • Embedded SQL is implemented using preprocessor. SQL code is first written embedded into C code. Then code is run through ECPG preprocessor, which replaces SQL with calls to code library. Then code can be compiled using a C compiler. Embedding works also with C++ but it does not recognize all C++ constructs.

Concurrency model

PostgreSQL server is process-based (not threaded), and uses one operating system process per database session. A single database session (connection) cannot utilize more than one CPU. Of course, multiple sessions are automatically spread across all available CPUs by the operating system. Client applications can easily use threads and create multiple database connections from each thread. [45]

Security

PostgreSQL manages its internal security 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 of which other roles are members). 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.

PostgreSQL's SECURITY LABEL feature (extension to SQL standards), allows for additional security; with a bundled loadable module that supports label-based mandatory access control (MAC) based on SELinux security policy.[46][47]

PostgreSQL natively supports a broad number of external 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 TLS.

Benchmarks and performance

Many informal performance studies of PostgreSQL have been done.[48] 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.[49]

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 PostgreSQL 8.2.[50] 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.[48]

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 $84.98/JOPS to $70.57/JOPS.[51]

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.[52] PostgreSQL.org provides advice on basic recommended performance practice in a wiki.[53]

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

Matloob Khushi performed benchmarking between Postgresql 9.0 and MySQL 5.6.15 for their ability to process genomic data. In his performance analysis he found that PostgreSQL extracts overlapping genomic regions eight times faster than MySQL using two datasets of 80,000 each forming random human DNA regions. Insertion and data uploads in PostgreSQL were also better, although general searching capability of both databases was almost equivalent.[55]

Platforms

PostgreSQL is available for the following operating systems: Linux (all recent distributions), Windows (Windows 2000 SP4 and later; compilable by e.g. Visual Studio, now with up to most recent 2015 version), FreeBSD, OpenBSD, NetBSD, OS X (macOS),[12] AIX, HP-UX, Solaris, and UnixWare; and not officially tested: DragonFly BSD, BSD/OS, IRIX, OpenIndiana,[56] OpenSolaris, OpenServer, and Tru64 Unix. Most other Unix-like systems could also work; most modern do support.

PostgreSQL works on any of the following instruction set architectures: x86 and x86-64 on Windows and other operating systems; these are supported on other than Windows: IA-64 Itanium (external support for HP-UX), PowerPC, PowerPC 64, S/390, S/390x, SPARC, SPARC 64, ARMv8-A (64-bit)[57] and older ARM (32-bit, including older such as ARMv6 in Raspberry Pi[58]), MIPS, MIPSel, and PA-RISC. It is also known to work on Alpha (dropped in 9.5), M68k, M32R, NS32k, and VAX. In addition to these, it is possible to build PostgreSQL for an unsupported CPU by disabling spinlocks.[59]

Database administration

See also: Comparison of database tools

Open source front-ends and tools for administering PostgreSQL include:

psql
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
The pgAdmin package is a free and open source graphical user interface administration tool for PostgreSQL, which is supported on many computer platforms.[60] 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 GNU General Public License (GPL) 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. The query tool includes a scripting language called pgScript for supporting admin and development tasks. In December 2014, Dave Page, the pgAdmin project founder and primary developer,[61] announced that with the shift towards web-based models work has started on pgAdmin 4 with the aim of facilitating Cloud deployments.[62] In 2016, pgAdmin 4 was released.
phpPgAdmin
phpPgAdmin is a web-based administration tool for PostgreSQL written in PHP and based on the popular phpMyAdmin interface originally written for MySQL administration.[63]
PostgreSQL Studio
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.[64]
TeamPostgreSQL
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.[65]
LibreOffice/OpenOffice.org Base
LibreOffice/OpenOffice.org Base can be used as a front-end for PostgreSQL.[66][67]
pgBadger
The pgBadger PostgreSQL log analyzer generates detailed reports from a PostgreSQL log file.[68]
pgDevOps
pgDevOps is a suite of web tools to install & manage multiple PostgreSQL versions, extensions, and community components, develop SQL queries, monitor running databases and find performance problems.[69]

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.

Prominent users

Prominent organizations and products that use PostgreSQL as the primary database include:

Service implementations

Some notable vendors offer PostgreSQL as software as a service:

  • Heroku, a platform as a service provider, has supported PostgreSQL since the start in 2007.[92] They offer value-add features like full database "roll-back" (ability to restore a database from any point in time),[93] which is based on WAL-E, open-source software developed by Heroku.[94]
  • 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.[95]
  • VMware has offered vFabric Postgres (also known as vPostgres[96]) for private clouds on vSphere since May 2012.[97]
  • In November 2013, Amazon.com announced the addition of PostgreSQL to their Relational Database Service offering.[98][99]
  • In November 2016, Amazon Web Services announced the addition of PostgreSQL compatibility to their cloud-native Amazon Aurora managed database offering.[100]

Release history

Release First release Latest minor version Latest release End of
Life[101] 		Milestones
6.0 1997-01-29 — — — First formal release of PostgreSQL, unique indexes, pg_dumpall utility, ident authentication
6.1 1997-06-08 6.1.1 Old version, no longer maintained: 1997-07-22 — Multi-column indexes, sequences, money data type, GEQO (GEnetic Query Optimizer)
6.2 1997-10-02 6.2.1 Old version, no longer maintained: 1997-10-17 — JDBC interface, triggers, server programming interface, constraints
6.3 1998-03-01 6.3.2 Old version, no longer maintained: 1998-04-07 Old version, no longer maintained: 2003-04 SQL-92 subselect capability, PL/pgTCL
6.4 1998-10-30 6.4.2 Old version, no longer maintained: 1998-12-20 Old version, no longer maintained: 2003-10 VIEWs (then only read-only) and RULEs, PL/pgSQL
6.5 1999-06-09 6.5.3 Old version, no longer maintained: 1999-10-13 Old version, no longer maintained: 2004-06 MVCC, temporary tables, more SQL statement support (CASE, INTERSECT, and EXCEPT)
7.0 2000-05-08 7.0.3 Old version, no longer maintained: 2000-11-11 Old version, no longer maintained: 2004-05 Foreign keys, SQL-92 syntax for joins
7.1 2001-04-13 7.1.3 Old version, no longer maintained: 2001-08-15 Old version, no longer maintained: 2006-04 Write-ahead log, outer joins
7.2 2002-02-04 7.2.8 Old version, no longer maintained: 2005-05-09 Old version, no longer maintained: 2007-02 PL/Python, OIDs no longer required, internationalization of messages
7.3 2002-11-27 7.3.21 Old version, no longer maintained: 2008-01-07 Old version, no longer maintained: 2007-11 Schema, table function, prepared query[102]
7.4 2003-11-17 7.4.30 Old version, no longer maintained: 2010-10-04 Old version, no longer maintained: 2010-10 Optimization on JOINs and data warehousing functions[103]
8.0 2005-01-19 8.0.26 Old version, no longer maintained: 2010-10-04 Old version, no longer maintained: 2010-10 Native server on Microsoft Windows, savepoints, tablespaces, point-in-time recovery[104]
8.1 2005-11-08 8.1.23 Old version, no longer maintained: 2010-12-16 Old version, no longer maintained: 2010-11 Performance optimization, two-phase commit, table partitioning, index bitmap scan, shared row locking, roles
8.2 2006-12-05 8.2.23 Old version, no longer maintained: 2011-09-26 Old version, no longer maintained: 2011-12 Performance optimization, online index builds, advisory locks, warm standby[105]
8.3 2008-02-04 8.3.23 Old version, no longer maintained: 2013-02-07 Old version, no longer maintained: 2013-12 Heap-only tuples, full text search,[106] SQL/XML, ENUM types, UUID types
8.4 2009-07-01 8.4.22 Old version, no longer maintained: 2014-07-24 Old version, no longer maintained: 2014-07 Windowing functions, column-level permissions, parallel database restore, per-database collation, common table expressions and recursive queries[107]
9.0 2010-09-20 9.0.23 Old version, no longer maintained: 2015-10-08 Old version, no longer maintained: 2015-09 Built-in binary streaming replication, hot standby, in-place upgrade capability, 64-bit Windows[108]
9.1 2011-09-12 9.1.24 Old version, no longer maintained: 2016-10-27 Old version, no longer maintained: 2016-09 Synchronous replication, per-column collations, unlogged tables, serializable snapshot isolation, writeable common table expressions, SELinux integration, extensions, foreign tables[109]
9.2 2012-09-10 9.2.24 Old version, no longer maintained: 2017-11-09 Old version, no longer maintained: 2017-09 Cascading streaming replication, index-only scans, native JSON support, improved lock management, range types, pg_receivexlog tool, space-partitioned GiST indexes
9.3 2013-09-09 9.3.22 Old version, yet still maintained: 2018-03-01 Old version, yet still maintained: 2018-09 Custom 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
9.4 2014-12-18 9.4.17 Old version, yet still maintained: 2018-03-01 Old version, yet still maintained: 2019-12 JSONB data type, ALTER SYSTEM statement for changing config values, ability to refresh materialized views without blocking reads, dynamic registration/start/stop of background worker processes, Logical Decoding API, GiN index improvements, Linux huge page support, database cache reloading via pg_prewarm
9.5 2016-01-07 9.5.12 Old version, yet still maintained: 2018-03-01 Old version, yet still maintained: 2021-01 UPSERT, row level security, TABLESAMPLE, CUBE/ROLLUP, GROUPING SETS, and new BRIN index[110]
9.6 2016-09-29 9.6.8 Old version, yet still maintained: 2018-03-01 Old version, yet still maintained: 2021-09 Parallel query support, PostgreSQL foreign data wrapper (FDW) improvements with sort/join pushdown, multiple synchronous standbys, faster vacuuming of large table
10 2017-10-05 10.3 Current stable version: 2018-03-01 Current stable version: 2022-10 Logical replication, declarative table partitioning, improved query parallelism
Legend:
Old version, not maintained
Old version, still maintained
Latest version
Latest preview version
Future release

See also

References

  1. ^ a b "Happy Birthday, PostgreSQL!". PostgreSQL Global Development Group. July 8, 2008.
  2. ^ "PostgreSQL: PostgreSQL 10.3, 9.6.8, 9.5.12, 9.4.17, and 9.3.22 released!". PostgreSQL. The PostgreSQL Global Development Group. March 1, 2018. Retrieved March 5, 2018.
  3. ^ "Debian -- Details of package pgadmin3 in jessie". Retrieved March 10, 2017.
  4. ^ a b "License". PostgreSQL Global Development Group. Retrieved September 20, 2010.
  5. ^ "PostgreSQL licence approved by OSI". Crynwr. February 18, 2010. Retrieved February 18, 2010.
  6. ^ a b "OSI PostgreSQL Licence". Open Source Initiative. February 20, 2010. Retrieved February 20, 2010.
  7. ^ "Debian -- Details of package postgresql in sid". debian.org.
  8. ^ "Licensing:Main". FedoraProject.
  9. ^ "PostgreSQL". fsf.org.
  10. ^ "OS X Lion Server — Technical Specifications". August 4, 2011. Retrieved November 12, 2011. Web Hosting [..] PostgreSQL
  11. ^ "Lion Server: MySQL not included". August 4, 2011. Retrieved November 12, 2011.
  12. ^ a b "Mac OS X packages". The PostgreSQL Global Development Group. Retrieved August 27, 2016.
  13. ^ "What is PostgreSQL?". PostgreSQL 9.3.0 Documentation. PostgreSQL Global Development Group. Retrieved September 20, 2013.
  14. ^ a b "Contributor Profiles". PostgreSQL Global Development Group. Retrieved March 14, 2017.
  15. ^ Audio sample, 5.6k MP3
  16. ^ 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 December 17, 2011.
  17. ^ "PostgreSQL: History". PostgreSQL Global Development Group. Retrieved August 27, 2016.
  18. ^ "Project name – statement from the core team". archives.postgresql.org. November 16, 2007. Retrieved November 16, 2007.
  19. ^ 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.
  20. ^ Pavel Stehule (June 9, 2012). "Historie projektu PostgreSQL" (in Czech).
  21. ^ "University POSTGRES, Version 4.2". July 26, 1999.
  22. ^ Page, Dave (April 7, 2015). "Re: 20th anniversary of PostgreSQL ?". pgsql-advocacy (Mailing list). Retrieved April 9, 2015.
  23. ^ Jake Edge (October 14, 2015). "A bug tracker for PostgreSQL? [LWN.net]". lwn.net. Retrieved October 20, 2017.
  24. ^ Dan R. K. Ports; Kevin Grittner (2012). "Serializable Snapshot Isolation in PostgreSQL" (PDF). Proceedings of the VLDB Endowment. 5 (12): 1850–1861. doi:10.14778/2367502.2367523.
  25. ^ PostgreSQL 9.1 with synchronous replication (news), H Online
  26. ^ Postgres-XC project page (website), Postgres-XC
  27. ^ "Postgres-R: a database replication system for PostgreSQL". Postgres Global Development Group. Retrieved August 27, 2016.
  28. ^ "Postgres-BDR". 2ndQuadrant Ltd. Retrieved August 27, 2016.
  29. ^ Marit Fischer (November 10, 2007). "Backcountry.com finally gives something back to the open source community" (Press release). Backcountry.com.
  30. ^ Bartunov, O; Sigaev, T (May 2011). SP-GiST – a new indexing framework for PostgreSQL (PDF). PGCon 2011. Ottawa, Canada. Retrieved January 31, 2016.
  31. ^ "hash: Add write-ahead logging support". PostgreSQL. March 14, 2017. Retrieved June 9, 2017.
  32. ^ Bartunov, O; Sigaev, T (May 2010). K-nearest neighbour search for PostgreSQL (PDF). PGCon 2010. Ottawa, Canada. Retrieved January 31, 2016.
  33. ^ Geoghegan, Peter (March 23, 2014). "What I think of jsonb".
  34. ^ Obe, Regina; Hsu, Leo S. (2012). "10: Replication and External Data". PostgreSQL: Up and Running (1 ed.). Sebastopol, CA: O'Reilly Media, Inc. p. 129. ISBN 978-1-4493-2633-3. Retrieved October 17, 2016. Foreign Data Wrappers (FDW) [...] are mechanisms of querying external datasources. PostgreSQL 9.1 introduced this SQL/MED standards compliant feature.
  35. ^ "PostgreSQL + Python | Psycopg". initd.org.
  36. ^ "SQL database drivers". Go wiki. golang.org. Retrieved June 22, 2015.
  37. ^ "RPostgreSQL: R Interface to the 'PostgreSQL' Database System". CRAN. cran.r-project.org. Retrieved August 3, 2017.
  38. ^ "Procedural Languages". postgresql.org. March 31, 2016. Retrieved April 7, 2016.
  39. ^ "Add a materialized view relations". March 4, 2013. Retrieved March 4, 2013.
  40. ^ "Support automatically-updatable views". December 8, 2012. Retrieved December 8, 2012.
  41. ^ "Add CREATE RECURSIVE VIEW syntax". February 1, 2013. Retrieved February 28, 2013.
  42. ^ Momjian, Bruce (2001). "Subqueries". PostgreSQL: Introduction and Concepts. Addison-Wesley. ISBN 0-201-70331-9. Retrieved September 25, 2010. {{cite book}}: External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help)
  43. ^ Bernier, Robert (February 2, 2006). "Using Regular Expressions in PostgreSQL". O'Reilly Media. Retrieved September 25, 2010.
  44. ^ "A few short notes about PostgreSQL and POODLE". hagander.net.
  45. ^ "FAQ - PostgreSQL wiki". wiki.postgresql.org. Retrieved April 13, 2017.
  46. ^ "SEPostgreSQL Documentation".
  47. ^ "NB SQL 9.3".
  48. ^ a b Josh Berkus (July 6, 2007). "PostgreSQL publishes first real benchmark". Retrieved July 10, 2007.
  49. ^ György Vilmos (September 29, 2009). "PostgreSQL history". Retrieved August 28, 2010.
  50. ^ "SPECjAppServer2004 Result". SPEC. July 6, 2007. Retrieved July 10, 2007.
  51. ^ "SPECjAppServer2004 Result". SPEC. July 4, 2007. Retrieved September 1, 2007.
  52. ^ "Managing Kernel Resources". PostgreSQL Manual. PostgreSQL.org. Retrieved November 12, 2011.
  53. ^ Greg Smith (October 15, 2010). PostgreSQL 9.0 High Performance. Packt Publishing. ISBN 978-1-84951-030-1.
  54. ^ Robert Haas (April 3, 2012). "Did I Say 32 Cores? How about 64?". Retrieved April 8, 2012.
  55. ^ Khushi, Matloob (June 2015). "Benchmarking database performance for genomic data". J Cell Biochem. 116: 877–83. doi:10.1002/jcb.25049. PMID 25560631.
  56. ^ "oi_151a Release Notes". OpenIndiana. Retrieved April 7, 2012.
  57. ^ "AArch64 planning BoF at DebConf". debian.org.
  58. ^ Souza, Rubens (June 17, 2015). "Step 5 (update): Installing PostgreSQL on my Raspberry Pi 1 and 2". Raspberry PG. Retrieved August 27, 2016.
  59. ^ "Supported Platforms". PostgreSQL Global Development Group. Retrieved April 6, 2012.
  60. ^ "pgAdmin: PostgreSQL administration and management tools". website. Retrieved November 12, 2011.
  61. ^ "pgAdmin Development Team". pgadmin.org. Retrieved June 22, 2015.
  62. ^ Dave, Page. "The story of pgAdmin". Dave's Postgres Blog. pgsnake.blogspot.co.uk. Retrieved December 7, 2014.
  63. ^ phpPgAdmin Project (April 25, 2008). "About phpPgAdmin". Retrieved April 25, 2008.
  64. ^ PostgreSQL Studio (October 9, 2013). "About PostgreSQL Studio". Retrieved October 9, 2013.
  65. ^ "TeamPostgreSQL website". October 3, 2013. Retrieved October 3, 2013.
  66. ^ oooforum.org (January 10, 2010). "Back Ends for OpenOffice". Retrieved January 5, 2011.
  67. ^ libreoffice.org (October 14, 2012). "Base features". Retrieved October 14, 2012.
  68. ^ Greg Smith; Robert Treat; Christopher Browne. "Tuning your PostgreSQL server". Wiki. PostgreSQL.org. Retrieved November 12, 2011. {{cite web}}: Unknown parameter |last-author-amp= ignored (|name-list-style= suggested) (help)
  69. ^ "pgDevOps". BigSQL.org. Retrieved May 4, 2017.
  70. ^ Emmanuel Cecchet (May 21, 2009). Building PetaByte Warehouses with Unmodified PostgreSQL (PDF). PGCon 2009. Retrieved November 12, 2011.
  71. ^ "MySpace.com scales analytics for all their friends" (PDF). case study. Aster Data. June 15, 2010. Archived from the original (PDF) on November 14, 2010. Retrieved November 12, 2011. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  72. ^ "Last Weekend's Outage". Blog. Geni. August 1, 2011.
  73. ^ "Database". Wiki. OpenStreetMap.
  74. ^ PostgreSQL affiliates .ORG domain, AU: Computer World
  75. ^ a b c W. Jason Gilmore; R.H. Treat (2006). Beginning PHP and PostgreSQL 8: From Novice to Professional. Apress. ISBN 978-1-43020-136-6. Retrieved August 30, 2017.
  76. ^ Sony Online opts for open-source database over Oracle, Computer World
  77. ^ A Web Commerce Group Case Study on PostgreSQL (PDF) (1.2 ed.), PostgreSQL
  78. ^ "Architecture Overview". Reddit software wiki. Reddit. March 27, 2014. Retrieved November 25, 2014.
  79. ^ "PostgreSQL at Skype". Skype Developer Zone. 2006. Retrieved October 23, 2007.
  80. ^ "How Much Are You Paying For Your Database?". Sun Microsystems blog. 2007. Retrieved December 14, 2007.
  81. ^ "Database – MusicBrainz". MusicBrainz Wiki. Retrieved February 5, 2011.
  82. ^ Duncavage, Daniel P (July 13, 2010). "NASA needs Postgres-Nagios help".
  83. ^ Roy, Gavin M (2010). "PostgreSQL at myYearbook.com" (talk). USA East: PostgreSQL Conference.
  84. ^ "Keeping Instagram up with over a million new users in twelve hours". Instagram-engineering.tumblr.com. May 17, 2011. Retrieved July 7, 2012.
  85. ^ "Postgres at Disqus". Retrieved May 24, 2013.
  86. ^ Matthew Kelly (March 27, 2015). At The Heart Of A Giant: Postgres At TripAdvisor. PGConf US 2015. (Presentation video)
  87. ^ "Yandex.Mail's successful migration from Oracle to Postgres [pdf] | Hacker News". news.ycombinator.com. Retrieved September 28, 2016.
  88. ^ a b S. Riggs; G. Ciolli; H. Krosing; G. Bartolini (2015). PostgreSQL 9 Administration Cookbook - Second Edition. Packt. ISBN 978-1-84951-906-9. Retrieved September 5, 2017.
  89. ^ "Met Office swaps Oracle for PostgreSQL". computerweekly.com. Retrieved September 5, 2017.
  90. ^ Oracle Database
  91. ^ "Open Source Software". FlightAware. Retrieved November 22, 2017.
  92. ^ Alex Williams (April 1, 2013). "Heroku Forces Customer Upgrade To Fix Critical PostgreSQL Security Hole". TechCrunch.
  93. ^ Barb Darrow (November 11, 2013). "Heroku gussies up Postgres with database roll-back and proactive alerts". GigaOM.
  94. ^ Craig Kerstiens (September 26, 2013). "WAL-E and Continuous Protection with Heroku Postgres". Heroku blog.
  95. ^ "EnterpriseDB Offers Up Postgres Plus Cloud Database". Techweekeurope.co.uk. January 27, 2012. Retrieved July 7, 2012.
  96. ^ O'Doherty, Paul; Asselin, Stephane (2014). "3: VMware Workspace Architecture". VMware Horizon Suite: Building End-User Services. VMware Press Technology. Upper Saddle River, NJ: VMWare Press. p. 65. ISBN 978-0-13-347910-2. Retrieved September 19, 2016. In addition to the open source version of PostgreSQL, VMware offers vFabric Postgres, or vPostgres. vPostgres is a PostgreSQL virtual appliance that has been tuned for virtual environments.
  97. ^ Al Sargent (May 15, 2012). "Introducing VMware vFabric Suite 5.1: Automated Deployment, New Components, and Open Source Support". VMware blogs.
  98. ^ Jeff (November 14, 2013). "Amazon RDS for PostgreSQL – Now Available". Amazon Web Services Blog.
  99. ^ Alex Williams (November 14, 2013). "PostgreSQL Now Available On Amazon's Relational Database Service". TechCrunch.
  100. ^ "Amazon Aurora Update – PostgreSQL Compatibility | AWS Blog". aws.amazon.com. Retrieved December 1, 2016.
  101. ^ "Versioning policy". PostgreSQL Global Development Group. Retrieved June 1, 2016.
  102. ^ Vaas, Lisa (December 2, 2002). "Databases Target Enterprises". eWeek. Retrieved October 29, 2016.
  103. ^ Krill, Paul (November 20, 2003). "PostgreSQL boosts open source database". InfoWorld. Retrieved October 21, 2016.
  104. ^ Krill, Paul (January 19, 2005). "PostgreSQL open source database boasts Windows boost". InfoWorld. Retrieved November 2, 2016.
  105. ^ Weiss, Todd R. (December 5, 2006). "Version 8.2 of open-source PostgreSQL DB released". Computerworld. Retrieved October 17, 2016.
  106. ^ Gilbertson, Scott (February 5, 2008). "PostgreSQL 8.3: Open Source Database Promises Blazing Speed". Wired. Retrieved October 17, 2016.
  107. ^ Huber, Mathias (July 2, 2009). "PostgreSQL 8.4 Proves Feature-Rich". Linux Magazine. Retrieved October 17, 2016.
  108. ^ Brockmeier, Joe (September 30, 2010). "Five Enterprise Features in PostgreSQL 9". Linux.com. Linux foundation. Retrieved February 6, 2017.
  109. ^ Timothy Prickett Morgan (September 12, 2011). "PostgreSQL revs to 9.1, aims for enterprise". The Register. Retrieved February 6, 2017.
  110. ^ Richard, Chirgwin (January 7, 2016). "Say oops, UPSERT your head: PostgreSQL version 9.5 has landed". The Register. Retrieved October 17, 2016.

Further reading

Wikimedia Commons has media related to PostgreSQL.
Wikibooks has a book on the topic of: PostgreSQL
Retrieved from "https://en.wikipedia.org/w/index.php?title=PostgreSQL&oldid=829666139"