Array ( [0] => {{Short description|Free and open-source object relational database management system}} [1] => {{Use mdy dates|date=February 2019}} [2] => {{Infobox software [3] => | name = PostgreSQL [4] => | logo = Postgresql elephant.svg [5] => | logo caption = ''The World's Most Advanced Open Source Relational Database''{{cite web|title=PostgreSQL|quote=PostgreSQL: The World's Most Advanced Open Source Relational Database|url=https://www.postgresql.org|access-date=2019-09-21}} [6] => [7] => | developer = PostgreSQL Global Development Group [8] => | released = {{Start date and age|1996|07|08|br=yes|df=yes}} [9] => | latest release version = {{wikidata|property|edit|reference|P548=Q2804309|P348}} [10] => | latest release date = {{start date and age|{{wikidata|qualifier|P548=Q2804309|P348|P577}}}} [11] => | latest preview version = [12] => | latest preview date = [13] => | programming language = [[C (programming language)|C]] [14] => | genre = [[Relational database|RDBMS]] [15] => | license = PostgreSQL License ([[free and open-source]], [[Permissive software licence|permissive]]) [16] => }} [17] => {{Infobox software license [18] => | name = PostgreSQL License [19] => | image = [20] => | caption = PostgreSQL License [21] => | author = [22] => | version = [23] => | publisher = PostgreSQL Global Development Group
Regents of the University of California [24] => | date = [25] => | OSI approved = Yes [26] => | Debian approved = Yes{{Cite web|title=Debian -- Details of package postgresql in sid|url=https://packages.debian.org/unstable/postgresql|access-date=2021-01-25|website=packages.debian.org}}{{cite web |url=https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing |title=Licensing:Main |work=FedoraProject}} [27] => | FSF approved = Yes{{cite web |url=https://directory.fsf.org/wiki/PostgreSQL |title=PostgreSQL |work=fsf.org}} [28] => | GPL compatible = Yes [29] => | copyleft = No [30] => | linking = Yes [31] => | website = {{URL|postgresql.org/about/licence}} [32] => }} [33] => [34] => '''PostgreSQL''' ({{IPAc-en|ˈ|p|oʊ|s|t|ɡ|ɹ|ɛ|s|_|ˌ|k|juː|_|ˈ|ɛ|l}}, {{respell|POHST|gres|_|kyoo|_|el}}),{{cite web | url=https://wiki.postgresql.org/wiki/FAQ#What_is_PostgreSQL.3F_How_is_it_pronounced.3F_What_is_Postgres.3F | title=FAQ: What is PostgreSQL? How is it pronounced? What is Postgres? | work=PostgreSQL Wiki | publisher=PostgreSQL community | access-date=October 2, 2021}} also known as '''Postgres''', is a [[free and open-source software|free and open-source]] [[relational database management system]] (RDBMS) emphasizing [[extensibility]] and [[SQL]] compliance. [35] => PostgreSQL features [[transaction processing|transactions]] with [[atomicity (database systems)|atomicity]], [[consistency (database systems)|consistency]], [[isolation (database systems)|isolation]], [[durability (database systems)|durability]] ([[ACID]]) properties, automatically updatable [[view (SQL)|view]]s, [[materialized view]]s, [[database trigger|triggers]], [[foreign key]]s, and [[stored procedure]]s. [36] => It is supported on all major [[operating systems]], including [[Linux]], [[FreeBSD]], [[OpenBSD]], [[macOS]], and [[Microsoft Windows|Windows]], and handles a range of workloads from single machines to [[data warehouse]]s or [[web services]] with many [[concurrent user]]s. [37] => [38] => The PostgreSQL Global Development Group focuses only on developing a [[database engine]] and closely related components. [39] => This core is, technically, what comprises PostgreSQL itself, but there is an extensive developer community and ecosystem that provides other important feature sets that might, traditionally, be provided by a proprietary software vendor. [40] => These include special-purpose database engine features, like those needed to support a [[Spatial database|geospatial]] [41] => {{cite web [42] => |url=https://postgis.net/ [43] => |title=PostGIS [44] => |author= [45] => |date=2023-12-18 [46] => |website=postgis.net [47] => |access-date=2023-12-18 [48] => |quote=PostGIS extends the capabilities of the PostgreSQL relational database by adding support for storing, indexing, and querying geospatial data.}} [49] => or [[Temporal database|temporal]] [50] => {{cite web [51] => |url=https://wiki.postgresql.org/wiki/Temporal_Extensions [52] => |title=Temporal Extensions [53] => |author= [54] => |date=2023-12-18 [55] => |website=PostgreSQL Wiki [56] => |access-date=2023-12-18 [57] => |quote=Postgres can be extended to become a Temporal Database. Such databases track the history of database content over time, automatically retaining said history and allowing it to be altered and queried.}} [58] => database or features which emulate other database products. [59] => {{cite web [60] => |url=https://github.com/orafce/orafce [61] => |title=Orafce - Oracle's compatibility functions and packages [62] => |author= [63] => |date=2023-12-17 [64] => |website=GitHub.com [65] => |access-date=2023-12-18 [66] => |quote=Functions and operators that emulate a subset of functions and packages from the Oracle RDBMS.}} [67] => [68] => {{cite web [69] => |url=https://github.com/MigOpsRepos/pg_dbms_job#readme [70] => |title=pg_dbms_job [71] => |author= [72] => |date=2023-11-08 [73] => |website=GitHub.com [74] => |access-date=2023-12-18 [75] => |quote=PostgreSQL extension to schedules and manages jobs in a job queue similar to Oracle DBMS_JOB package.}} [76] => [77] => {{cite web [78] => |url=https://wiltondb.com/ [79] => |title=WiltonDB [80] => |author= [81] => |date=2023 [82] => |website=WiltonDB [83] => |access-date=2023-12-18 [84] => |quote=WiltonDB [is] packaged for Windows. It strives to be usable as a drop-in replacement to Microsoft SQL Server.}} [85] => [86] => {{cite web [87] => |url=https://babelfishpg.org/ [88] => |title=Babelfish for PostgreSQL [89] => |author= [90] => |website=babelfishpg.org [91] => |access-date=2023-12-18 [92] => |quote=Babelfish for PostgreSQL ... provides the capability for PostgreSQL to understand queries from applications written for Microsoft SQL Server.}} [93] => [94] => Also available from third parties are a wide variety of user and machine interface features, such as [[graphical user interface]]s [95] => {{cite web [96] => |url=https://wiki.postgresql.org/wiki/PostgreSQL_Clients [97] => |title=PostgreSQL Clients [98] => |author= [99] => |date=2023-10-18 [100] => |website=wiki.postgresql.org [101] => |access-date=2023-12-18 [102] => |quote=This page is a partial list of interactive SQL clients (GUI or otherwise) ... that you can type SQL in to and get results from them.}} [103] => [104] => {{cite web [105] => |url=https://wiki.postgresql.org/wiki/Design_Tools [106] => |title=Design Tools [107] => |author= [108] => |date=2023-10-23 [109] => |website=wiki.postgresql.org [110] => |access-date=2023-12-18 [111] => |quote=Tools to help with designing a schema, via creating Entity-Relationship diagrams and similar. Most are GUI.}} [112] => [113] => {{cite web [114] => |url=https://wiki.postgresql.org/wiki/Community_Guide_to_PostgreSQL_GUI_Tools [115] => |title=Community Guide to PostgreSQL GUI Tools [116] => |author= [117] => |date=2023-12-01 [118] => |website=wiki.postgresql.org [119] => |access-date=2023-12-18 [120] => |quote=This page is a list of miscellaneous utilities that work with Postgres (ex: data loaders, comparators etc.).}} [121] => or [[Load balancing (computing)|load balancing]] and [[high availability]] toolsets. [122] => {{cite web [123] => |url=https://wiki.postgresql.org/wiki/Replication,_Clustering,_and_Connection_Pooling [124] => |title=Replication, Clustering, and Connection Pooling [125] => |author= [126] => |date=2020-07-13 [127] => |website=wiki.postgresql.org [128] => |access-date=2023-12-18 [129] => |quote=There are many approaches available to scale PostgreSQL beyond running on a single server. ... There is no one-size fits all...}} [130] => [131] => The large third-party PostgreSQL support network of people, companies, products, and projects, even though not part of The PostgreSQL Development Group, are essential to the PostgreSQL database engine's adoption and use and make up the PostgreSQL ecosystem writ large.This is recognized by the liberal permission to use the PostgreSQL name, as approved (for fair use, when '''not''' confusing people about a legal relationship with the actual PostgreSQL project) when used in support of PostgreSQL, subject to the PostgreSQL Trademark Policy: [132] => {{cite web [133] => |url=https://www.postgresql.org/about/policies/trademarks/ [134] => |title=Trademark Policy [135] => |author= [136] => |website=PostgreSQL.org [137] => |date=2020-12-08 [138] => |access-date=2023-12-17 [139] => |quote=We will try to work with you to permit uses [of the PostgreSQL name] that support the PostgreSQL project and our Community.}} [140] => [141] => PostgreSQL was originally named POSTGRES, referring to its origins as a successor to the [[Ingres (database)|Ingres]] database developed at the [[University of California, Berkeley]]. In 1996, the project was renamed PostgreSQL to reflect its support for [[SQL]]. After a review in 2007, the development team decided to keep the name PostgreSQL and the alias Postgres. [142] => [143] => == History == [144] => 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. He returned to Berkeley in 1985, and began a post-Ingres project to address the problems with contemporary database systems that had become increasingly clear during the early 1980s. He won the [[Turing Award]] in 2014 for these and other projects,{{Cite web |url=https://amturing.acm.org/award_winners/stonebraker_1172121.cfm |title=Michael Stonebraker – A.M. Turing Award Winner |quote=Techniques pioneered in Postgres were widely implemented [..] Stonebraker is the only Turing award winner to have engaged in serial entrepreneurship on anything like this scale, giving him a distinctive perspective on the academic world. |website=amturing.acm.org |language=en |access-date=March 20, 2018}} and techniques pioneered in them. [145] => [146] => The new project, POSTGRES, aimed to add the fewest features needed to completely support [[data type]]s. These features included the ability to define types and to fully describe relationships{{snd}} something used widely, 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. [147] => [148] => Starting in 1986, published papers described the basis of the system, and a prototype version was shown at the 1988 ACM [[SIGMOD]] Conference. The team released version 1 to a small number of users in June 1989, followed by 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 managersA Brief History of PostgreSQL [https://www.postgresql.org/docs/9.3/history.html "Version 3 appeared in 1991 and added support for multiple storage managers, an improved query executor, and a rewritten rule system."]. ''postgresql.org''. ''The PostgreSQL Global Development Group'', Retrieved on March 18, 2020. and an improved query engine. By 1993, the number of users began to overwhelm the project with requests for support and features. After releasing version 4.2 on June 30, 1994{{snd}} primarily a cleanup{{snd}} the project ended. Berkeley released POSTGRES under an [[MIT License]] variant, which enabled other developers to use the code for any use. At the time, POSTGRES used an Ingres-influenced [[QUEL query languages|POSTQUEL query language]] interpreter, which could be interactively used with a [[console application]] named ''monitor''. [149] => [150] => 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 ''monitor'' console was also replaced by psql. Yu and Chen announced the first version (0.01) to [[beta tester]]s 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. [151] => [152] => On July 8, 1996, Marc Fournier at Hub.org Networking Services provided the first non-university development server for the open-source development effort. With the participation of Bruce Momjian and Vadim B. Mikheev, work began to stabilize the code inherited from Berkeley. [153] => [154] => 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. The first PostgreSQL release formed version 6.0 on January 29, 1997. Since then developers and volunteers around the world have maintained the software as The PostgreSQL Global Development Group. [155] => [156] => The project continues to make releases available under its [[free and open-source software]] PostgreSQL License. Code comes from contributions from proprietary vendors, support companies, and open-source programmers. [157] => [158] => == Multiversion concurrency control (MVCC) == [159] => PostgreSQL manages [[concurrency control|concurrency]] through [[multiversion concurrency control]] (MVCC), which gives each transaction a "snapshot" of the database, allowing changes to be made without affecting other transactions. This largely eliminates the need for read locks, and ensures the database maintains [[ACID (computer science)|ACID]] principles. PostgreSQL offers four levels of [[isolation (database systems)|transaction isolation]]: Read Uncommitted, 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) method. The PostreSQL MVCC implementation is prone to performance issues that require tuning when under a heavy write load which updates existing rows.{{Cite web|url=https://ottertune.com/blog/the-part-of-postgresql-we-hate-the-most|title=The part of PostgreSQL we hate the most |website= OtterTune|type= blog | author1= Bohan Zhang |author2= Andy Pavlo| date=2023}} [160] => [161] => == Storage and replication == [162] => [163] => === Replication === [164] => PostgreSQL includes built-in binary replication based on shipping the changes ([[Write-ahead logging|write-ahead logs]] (WAL)) 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, increasing load. [165] => [166] => PostgreSQL includes built-in synchronous replication 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 workloads that do not require such guarantees, and may not be wanted for all data as it slows down performance due to the requirement of the confirmation of the transaction reaching the synchronous standby. [167] => [168] => Standby servers can be synchronous or asynchronous. Synchronous standby servers can be specified in the configuration which determines which servers are candidates for synchronous replication. The first in the list that is actively streaming will be used as the current synchronous server. When this fails, the system fails over to the next in line. [169] => [170] => Synchronous [[multi-master replication]] is not included in the PostgreSQL core. Postgres-XC which is based on PostgreSQL provides scalable synchronous multi-master replication. It is licensed under the same license as PostgreSQL. A related project is called [[Postgres-XL]]. Postgres-R is yet another [[Fork (software development)|fork]]. Bidirectional replication (BDR) is an asynchronous multi-master replication system for PostgreSQL. [171] => [172] => Tools such as repmgr make managing replication clusters easier. [173] => [174] => Several asynchronous trigger-based replication packages are available. These remain useful even after introduction of the expanded core abilities, for situations where binary replication of a full database cluster is inappropriate: [175] => [176] => * [[Slony-I]] [177] => * Londiste, part of SkyTools (developed by [[Skype]]) [178] => * Bucardo multi-master replication (developed by [[Backcountry.com]]) [179] => * [[SymmetricDS]] multi-master, multi-tier replication [180] => [181] => === Indexes === [182] => PostgreSQL includes built-in support for regular [[B-tree]] and [[hash table]] indexes, and four index access methods: generalized search trees ([[GiST]]), generalized [[inverted index]]es (GIN), Space-Partitioned GiST (SP-GiST) and [[Block Range Index]]es (BRIN). In addition, user-defined index methods can be created, although this is quite an involved process. Indexes in PostgreSQL also support the following features: [183] => [184] => * [[Expression index]]es can be created with an index of the result of an expression or function, instead of simply the value of a column. [185] => * [[Partial index]]es, 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. [186] => * The planner is able to use multiple indexes together to satisfy complex queries, using temporary in-memory [[bitmap index]] operations (useful for [[data warehouse]] applications for joining a large [[fact table]] to smaller [[dimension table]]s such as those arranged in a [[star schema]]). [187] => * [[k-nearest neighbors algorithm|''k''-nearest neighbors]] (''k''-NN) indexing (also referred to KNN-GiST) provides efficient searching of "closest values" to that specified, useful to finding similar words, or close objects or locations with [[Geographic data and information|geospatial]] data. This is achieved without exhaustive matching of values. [188] => * Index-only scans often allow the system to fetch data from indexes without ever having to access the main table. [189] => * [[Block Range Index]]es (BRIN). [190] => [191] => === Schemas === [192] => PostgreSQL schemas are [[namespace]]s, allowing objects of the same kind and name to co-exist in a single database. [193] => They are not to be confused with a [194] => [[database schema]] -- the abstract, structural, organizational specification which defines how every table's data relates to data within other tables. [195] => All PostgreSQL database objects, except for a few global objects such as [[#Security|roles]] and [[tablespace]]s, exist within a schema. [196] => They cannot be nested, schemas cannot contain schemas. [197] => The permission system controls access to schemas and their content. [198] => By default, newly created databases have only a single schema called ''public'' but other schemas can be added and the public schema isn't mandatory. [199] => [200] => A {{code|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 {{code|$user, public}} ({{code|$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. [201] => [202] => Non-existent schemas, or other schemas not accessible to the logged-in user, that are listed in search_path are silently skipped during object lookup. [203] => [204] => New objects are created in whichever valid schema (one that can be accessed) appears first in the search_path. [205] => [206] => === Data types === [207] => A wide variety of native [[data type]]s are supported, including: [208] => [209] => * Boolean [210] => * [[Arbitrary-precision arithmetic|Arbitrary-precision]] numerics [211] => * Character (text, varchar, char) [212] => * Binary [213] => * Date/time (timestamp/time with/without time zone, date, interval) [214] => * Money [215] => * Enum [216] => * Bit strings [217] => * Text search type [218] => * Composite [219] => * HStore, an extension enabled key-value store within PostgreSQL{{Cite web |url=https://www.linuxjournal.com/content/postgresql-nosql-database |title=PostgreSQL, the NoSQL Database | Linux Journal |website=www.linuxjournal.com}} [220] => * Arrays ([[dynamic array|variable-length]] and can be of any data type, including text and composite types) up to 1 GB in total storage size [221] => * Geometric primitives [222] => * [[IPv4]] and [[IPv6]] addresses [223] => * [[Classless Inter-Domain Routing]] (CIDR) blocks and [[MAC address]]es [224] => * [[XML]] supporting [[XPath]] queries [225] => * [[Universally unique identifier]] (UUID) [226] => * JavaScript Object Notation ([[JSON]]), and a faster [[binary code|binary]] JSONB (not the same as [[BSON]]) [227] => [228] => In addition, users can create their own data types which can usually be made fully indexable via PostgreSQL's indexing infrastructures{{snd}} GiST, GIN, SP-GiST. Examples of these include the [[geographic information system]] (GIS) data types from the [[PostGIS]] project for PostgreSQL. [229] => [230] => 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. [231] => [232] => 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 time between {{nowrap|10:00 am}} and {{nowrap|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. [233] => [234] => 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 {{kbd|[]}} and {{kbd|()}} characters respectively. (e.g., {{code|[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. [235] => [236] => === User-defined objects === [237] => New types of almost all objects inside the database can be created, including: [238] => [239] => * Casts [240] => * Conversions [241] => * Data types [242] => * [[Data domain]]s [243] => * Functions, including aggregate functions and window functions [244] => * Indexes including custom indexes for custom types [245] => * Operators (existing ones can be [[Operator overloading|overloaded]]) [246] => * Procedural languages [247] => [248] => === Inheritance === [249] => 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. {{code|lang="sql" | SELECT * FROM ONLY parent_table;}}. Adding a column in the parent table will cause that column to appear in the child table. [250] => [251] => 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. [252] => [253] => This feature is not fully supported. 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. [254] => [255] => Inheritance provides a way to map the features of generalization hierarchies depicted in [[entity–relationship model|entity relationship diagrams]] (ERDs) directly into the PostgreSQL database. [256] => [257] => === Other storage features === [258] => * [[Referential integrity]] constraints including [[foreign key]] constraints, column [[Constraint satisfaction|constraints]], and row checks [259] => * Binary and textual large-object storage [260] => * [[Tablespace]]s [261] => * Per-column collation [262] => * Online backup [263] => * Point-in-time recovery, implemented using write-ahead logging [264] => * In-place upgrades with pg_upgrade for less downtime [265] => [266] => == Control and connectivity == [267] => [268] => === Foreign data wrappers === [269] => PostgreSQL can link to other systems to retrieve data via foreign data wrappers (FDWs).{{cite book [270] => |last1=Obe [271] => |first1=Regina [272] => |last2=Hsu [273] => |first2=Leo S. [274] => |chapter=10: Replication and External Data [275] => |title=PostgreSQL: Up and Running [276] => |url=https://books.google.com/books?id=Q8jkIZkMTPcC [277] => |edition=1 [278] => |location=Sebastopol, CA [279] => |publisher=[[O'Reilly Media|O'Reilly Media, Inc.]] [280] => |date=2012 [281] => |page=129 [282] => |isbn=978-1-4493-2633-3 [283] => |access-date=October 17, 2016 [284] => |quote=Foreign Data Wrappers (FDW) [...] are mechanisms of querying external datasources. PostgreSQL 9.1 introduced this [[SQL/MED]] standards compliant feature. [285] => }} [286] => These can take the form of any data source, such as a file system, another [[relational database]] management system (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. [287] => [288] => === Interfaces === [289] => PostgreSQL supports a binary [[communication protocol]] that allows applications to connect to the database server. The protocol is versioned (currently 3.0, as of PostgreSQL 7.4) and has a detailed specification.{{cite web [290] => | url = https://www.postgresql.org/docs/current/protocol.html [291] => | title = Frontend/Backend Protocol [292] => | author = [293] => | website = postgresql.org [294] => | date = November 9, 2023 [295] => | access-date = 2023-12-17 [296] => | quote = This document describes version 3.0 of the protocol, implemented in PostgreSQL 7.4 and later. [297] => }} [298] => [299] => The official client implementation of this communication protocol is a [[C (programming language)|C]] [[API]], libpq.{{cite web [300] => | url = https://www.postgresql.org/docs/16/libpq.html [301] => | title = libpq [302] => | author = [303] => | website = postgresql.org [304] => | date = November 9, 2023 [305] => | access-date = 2023-12-17 [306] => }} In addition, the officially supported [[ECPG]] tool allows SQL commands to be embedded in C code.{{cite web [307] => | url = https://www.postgresql.org/docs/16/ecpg.html [308] => | title = Embedded SQL in C [309] => | author = [310] => | website = postgresql.org [311] => | date = November 9, 2023 [312] => | access-date = 2023-12-17 [313] => }} Both are part of the standard PostgreSQL distribution.{{cite web [314] => | url = https://www.postgresql.org/docs/16/client-interfaces.html [315] => | title = Client Interfaces [316] => | author = [317] => | website = postgresql.org [318] => | date = November 9, 2023 [319] => | access-date = 2023-12-17 [320] => }} [321] => [322] => Third-party libraries for connecting to PostgreSQL are available for many [[programming language]]s, including [[C++]],{{cite web|title=libpqxx|url=http://pqxx.org/development/libpqxx/|access-date=April 4, 2020}} [[Java (programming language)|Java]],{{cite web|title=PostgreSQL JDBC Driver|url=https://jdbc.postgresql.org/|access-date=April 4, 2020}} [[Julia (programming language)|Julia]],{{Cite web|date=2021-06-30|title=[ANN] PostgresORM.jl: Object Relational Mapping for PostgreSQL|url=https://discourse.julialang.org/t/ann-postgresorm-jl-object-relational-mapping-for-postgresql/63847|access-date=2021-08-26|website=JuliaLang|language=en}}{{Cite web|title=GitHub - invenia/LibPQ.jl: A Julia wrapper for libpq|url=https://github.com/invenia/LibPQ.jl|access-date=2021-08-26|website=GitHub|language=en}} [[Python (programming language)|Python]], [[Node.js]],{{cite web|title=node-postgres|url=https://node-postgres.com/|access-date=April 4, 2020}} [[Go (programming language)|Go]],{{cite web |title=SQL database drivers |url=https://github.com/golang/go/wiki/SQLDrivers#drivers |website=Go wiki |publisher=golang.org |access-date=June 22, 2015}} and [[Rust (programming language)|Rust]].{{cite web|title=Rust-Postgres|url=https://crates.io/crates/postgres|access-date=April 4, 2020}} [323] => [324] => === Procedural languages === [325] => Procedural languages allow developers to extend the database with custom [[subroutine]]s (functions), often called ''[[stored procedure]]s''. These functions can be used to build [[database trigger]]s (functions invoked on modification of certain data) and custom data types and [[aggregate function]]s.{{cite web|url=https://www.postgresql.org/docs/current/server-programming.html|title=Server Programming|access-date=19 May 2019|website=PostgreSQL documentation}} Procedural languages can also be invoked without defining a function, using a DO command at SQL level.{{cite web|url=https://www.postgresql.org/docs/current/sql-do.html|title=DO|access-date=19 May 2019|website=PostgreSQL documentation}} [326] => [327] => Languages are divided into two groups: Procedures written in ''safe'' languages are [[Sandbox (computer security)|sandboxed]] and can be safely created and used by any user. Procedures written in ''unsafe'' languages can only be created by [[superuser]]s, because they allow bypassing a database's security restrictions, but can also access sources external to the database. Some languages like Perl provide both safe and unsafe versions. [328] => [329] => PostgreSQL has built-in support for three procedural languages: [330] => [331] => * Plain SQL (safe). Simpler SQL functions can get [[inline expansion|expanded inline]] into the calling (SQL) query, which saves function call overhead and allows the query optimizer to "see inside" the function. [332] => * Procedural Language/PostgreSQL ([[PL/pgSQL]]) (safe), which resembles Oracle's Procedural Language for SQL ([[PL/SQL]]) procedural language and SQL/Persistent Stored Modules ([[SQL/PSM]]). [333] => * [[C (programming language)|C]] (unsafe), which allows loading one or more custom [[shared library]] 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. [334] => [335] => In addition, PostgreSQL allows procedural languages to be loaded into the database through extensions. Three language extensions are included with PostgreSQL to support [[Perl]], [[Tcl]], and [[Python (programming language)|Python]]. For Python, the current {{nowrap|Python 3}} is used, and the discontinued {{nowrap|Python 2}} is no longer supported as of PostgreSQL 15. Both were supported previously, defaulting to {{nowrap|Python 2}}, while old and new versions couldn't be used in the same session.{{cite web|url=https://www.postgresql.org/docs/current/plpython.html|title=PL/Python - Python Procedural Language|access-date=October 23, 2022|website=PostgreSQL documentation}} External projects provide support for many other languages,{{cite web |date=March 31, 2016 |title=Procedural Languages |publisher=postgresql.org |url=https://www.postgresql.org/docs/current/static/external-pl.html |access-date=April 7, 2016}} including PL/[[Java (programming language)|Java]], [[JavaScript]] (PL/V8), PL/[[Julia (programming language)|Julia]],{{Cite web|date=2020-03-08|title=PL/Julia extension ( minimal )|url=https://discourse.julialang.org/t/pl-julia-extension-minimal/34232/2|access-date=2021-08-26|website=JuliaLang|language=en}} PL/[[R (programming language)|R]],{{Cite web|url=https://github.com/postgres-plr/plr|title=postgres-plr/plr|date=June 17, 2021|via=GitHub}} PL/[[Ruby (programming language)|Ruby]], and others. [336] => [337] => === Triggers === [338] => Triggers are events triggered by the action of SQL [[data manipulation language]] (DML) statements. For example, an [[Insert (SQL)|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 (SQL)|UPDATE]] statements. [339] => [340] => 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 [[View (SQL)|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. [341] => [342] => === Asynchronous notifications === [343] => 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 (computer science)|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. [344] => [345] => Many 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. [346] => [347] => PostgreSQL can act as an effective, persistent [[publish–subscribe pattern|"pub/sub" server]] or job server by combining LISTEN with FOR UPDATE SKIP LOCKED.{{cite web |last1=Chartier |first1=Colin |title=System design hack: Postgres is a great pub/sub & job server |url=https://layerci.com/blog/postgres-is-the-answer/ |website=LayerCI blog |date=November 8, 2019 |access-date=November 24, 2019}}{{cite web |title=Release 9.5 |url=https://www.postgresql.org/docs/9.5/release-9-5.html |website=postgresql.org|date=February 11, 2021 }}{{cite web |last1=Ringer |first1=Craig |title=What is SKIP LOCKED for in PostgreSQL 9.5? |url=https://www.2ndquadrant.com/en/blog/what-is-select-skip-locked-for-in-postgresql-9-5/ |website=2nd Quadrant |date=April 13, 2016 |access-date=November 24, 2019}} [348] => [349] => === Rules === [350] => Rules allow the "query tree" of an incoming query to be rewritten; they are an, automatically invoked, [[Macro (computer science)|macro language]] for SQL. "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 and before query planning. [351] => [352] => The functionality rules provide was, in almost every way, later duplicated with the introduction of newer types of triggers. [353] => The use of triggers is usually preferred over rules as it is easier to reason about trigger behavior and interactions than when equivalent rules are used. [354] => [355] => === Other querying features === [356] => * [[Database transaction|Transactions]] [357] => * [[Full-text search]] [358] => * Views [359] => ** Materialized views [360] => ** Updateable views [361] => ** Recursive views [362] => * Inner, outer (full, left, and right), and cross [[Join (SQL)|joins]] [363] => * Sub-[[Select (SQL)|selects]] [364] => ** Correlated sub-queries [365] => * [[Regular expression]]s [366] => * [[Hierarchical and recursive queries in SQL#Common table expression|Common table expressions]] and writable common table expressions [367] => * Encrypted connections via [[Transport Layer Security]] (TLS); current versions do not use vulnerable SSL, even with that configuration option [368] => * Domains [369] => * [[Savepoint]]s [370] => * [[Two-phase commit protocol|Two-phase commit]] [371] => * The Oversized-Attribute Storage Technique (TOAST) is used to transparently store large table attributes (such as big MIME attachments or XML messages) in a separate area, with automatic compression. [372] => * [[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. [373] => [374] => === Concurrency model === [375] => PostgreSQL server is [[process (computing)|process]]-based (not threaded), and uses one operating system process per database session. Multiple sessions are automatically spread across all available CPUs by the operating system. Many types of queries can also be parallelized across multiple background worker processes, taking advantage of multiple CPUs or cores.{{Cite web |url=https://lwn.net/Articles/689387/ |title=PostgreSQL 9.6 Beta and PGCon 2016 |last=Berkus |first=Josh |date=June 2, 2016 |website=LWN.net}} Client applications can use threads and create multiple database connections from each thread.{{Cite web |url=https://wiki.postgresql.org/wiki/FAQ#How_does_PostgreSQL_use_CPU_resources.3F |title=FAQ – PostgreSQL wiki |website=wiki.postgresql.org |language=en |access-date=April 13, 2017}} [376] => [377] => == Security == [378] => PostgreSQL manages its internal security on a per-[[Role-oriented programming|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 allow or prevent the visibility/creation/alteration/deletion of objects at the database, [[#Schemas|schema]], table, and row levels. [379] => [380] => 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 [[Security-Enhanced Linux]] (SELinux) security policy.{{Cite web |url=https://wiki.postgresql.org/wiki/SEPostgreSQL_Documentation |title=SEPostgreSQL Documentation – PostgreSQL wiki |website=wiki.postgresql.org}}{{Cite web |url=https://selinuxproject.org/page/NB_SQL_9.3 |title=NB SQL 9.3 - SELinux Wiki |website=selinuxproject.org}} [381] => [382] => PostgreSQL natively supports a broad number of external authentication mechanisms, including: [383] => [384] => * Password: either [[Salted Challenge Response Authentication Mechanism|SCRAM-SHA-256]],{{cite web |title = PostgreSQL 10 Documentation: Appendix E. Release Notes |date=August 12, 2021|url=https://www.postgresql.org/docs/10/release-10.html#id-1.11.6.16.3}} [[MD5]] or plain-text [385] => * [[Generic Security Services Application Program Interface]] (GSSAPI) [386] => * [[Security Support Provider Interface]] (SSPI) [387] => * [[Kerberos (protocol)|Kerberos]] [388] => * [[Ident protocol|ident]] (maps O/S user-name as provided by an ident server to database user-name) [389] => * Peer (maps local user name to database user name) [390] => * [[Lightweight Directory Access Protocol]] (LDAP) [391] => ** [[Active Directory]] (AD) [392] => * [[RADIUS]] [393] => * Certificate [394] => * [[Pluggable authentication module]] (PAM) [395] => [396] => 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. [397] => [398] => 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 [[Transport Layer Security]] (TLS). [399] => [400] => == Standards compliance == [401] => PostgreSQL claims high, but not complete, conformance with the latest [[SQL|SQL standard]] ("as of the version 15 release in October 2022, PostgreSQL conforms to at least 170 of the 179 mandatory features for [[SQL:2016]] Core conformance", and no other databases fully conformed to it{{Cite web|title=PostgreSQL: About|url=https://www.postgresql.org/about/|access-date=2021-08-26|website=www.postgresql.org}}). One exception is the handling of unquoted identifiers like table or column names. In PostgreSQL they are folded, internally, to lower case characters whereas the standard says that unquoted identifiers should be folded to upper case. Thus, {{code|Foo}} should be equivalent to {{code|FOO}} not {{code|foo}} according to the standard. Other shortcomings concern the absence of temporal tables allowing automatic logging of row versions during transactions with the possibility of browsing in time (FOR SYSTEM TIME predicate),{{citation needed |date=February 2022}} although relatively SQL compliant third-party extensions are available. [402] => [403] => == Benchmarks and performance == [404] => {{Update|date=April 2024|reason=Performance information based on soft- and hardware of 9 years ago is basically useless|part=section|updated=2015-06-01}} [405] => Many informal performance studies of PostgreSQL have been done. Performance improvements aimed at improving scalability began heavily with version 8.1. Simple benchmarks between version 8.0 and version 8.4 showed that the latter was more than ten times faster on read-only workloads and at least 7.5 times faster on both read and write workloads. [406] => [407] => 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. 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. [408] => [409] => 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. [410] => [411] => 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]]. PostgreSQL.org provides advice on basic recommended performance practice in a [[wiki]]. [412] => [413] => In April 2012, Robert Haas of EnterpriseDB demonstrated PostgreSQL 9.2's linear CPU scalability using a server with 64 cores. [414] => [415] => 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 ability of both databases was almost equivalent.{{cite journal |first=Matloob |last=Khushi |pmid=25560631 |title=Benchmarking database performance for genomic data |journal=J Cell Biochem |date=June 2015 |volume=116 |issue=6 |doi=10.1002/jcb.25049 |pages=877–83|arxiv=2008.06835 |s2cid=27458866 }} [416] => [417] => == Platforms == [418] => PostgreSQL is available for the following operating systems: [[Linux]] (all recent distributions), [[64-bit computing|64-bit]] [[AArch64|ARM]] and [[x86-64]] installers available and tested for [[macOS]] (OS X) version 10.12 and newer, [[Microsoft Windows|Windows]] (with installers available and tested for 64-bit [[Windows Server 2019]] and 2016; some older PostgreSQL versions were tested back to [[Windows Server 2012 R2|Windows 2012 R2]]{{Cite web|url=https://www.postgresql.org/download/windows/|title=PostgreSQL: Windows installers|website=www.postgresql.org|access-date=2021-08-26}}), [[FreeBSD]], [[OpenBSD]],{{cite web |url=http://ports.su/databases/postgresql,-main |title=postgresql-client-10.5p1 – PostgreSQL RDBMS (client) |work=[[OpenBSD ports]] |date=October 4, 2018 |access-date=October 10, 2018}} [[NetBSD]], and these without official (though unofficial likely available) binary executables, [[Solaris (operating system)|Solaris]],{{Cite web |title=Installing and Configuring PostgreSQL - Oracle Solaris Cluster Data Service for PostgreSQL Guide |url=https://docs.oracle.com/cd/E19680-01/html/821-1534/ciajejfa.html |access-date=2023-02-04 |website=docs.oracle.com}} [[IBM AIX|AIX]], and [[HP-UX]].{{Cite web |title=HP-UX Porting and Archive Centre {{!}} postgresql-12.4 |url=http://hpux.connect.org.uk/hppd/hpux/Users/postgresql-12.4/ |access-date=2023-02-04 |website=hpux.connect.org.uk}} Most other (modern) Unix-like systems do also work. [419] => [420] => PostgreSQL can be expected to work on any of the following [[instruction set architecture]]s (and operating systems): 64-bit [[x86-64]] and [[32-bit computing|32-bit]] [[x86]] on [[Windows XP]] (or later) and other operating systems; these are supported on other than Windows: 64-bit [[AArch64|ARM]] and the older 32-bit [[ARM architecture family|ARM]], including older such as [[ARMv6]] in [[Raspberry Pi]]), [[z/Architecture]], [[IBM System/390|S/390]], [[PowerPC]] (incl. 64-bit [[Power ISA]]), [[SPARC]] (also 64-bit), IA-64 [[Itanium]] ([[HP-UX]]), [[MIPS architecture|MIPS]] and [[PA-RISC]]. It was also known to work on some other platforms (while not been tested on for years, i.e. for latest versions). [421] => [422] => == Database administration == [423] => {{See also|Comparison of database administration tools}} [424] => [425] => Open source front-ends and tools for administering PostgreSQL include: [426] => [427] => ; {{anchor|psql}}psql: The primary [[Front and back ends|front-end]] for PostgreSQL is the {{code|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. [428] => ; {{anchor|pgAdmin}}pgAdmin: The pgAdmin package is a free and open-source [[graphical user interface]] (GUI) administration tool for PostgreSQL, which is supported on many computer platforms. 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]]{{cite web | url=https://packages.debian.org/jessie/pgadmin3 | title=Debian -- Details of package pgadmin3 in jessie | access-date=March 10, 2017}} 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,{{cite web |title=pgAdmin Development Team |url=http://www.pgadmin.org/development/team.php |website=pgadmin.org |access-date=June 22, 2015}} announced that with the shift towards web-based models, work has begun on pgAdmin 4 with the aim to facilitate cloud deployments.{{cite web |last1=Dave |first1=Page |title=The story of pgAdmin |url=http://pgsnake.blogspot.co.uk/2014/12/the-story-of-pgadmin.html |website=Dave's Postgres Blog |publisher=pgsnake.blogspot.co.uk |access-date=December 7, 2014|date=December 7, 2014 }} In 2016, pgAdmin 4 was released. The pgAdmin 4 backend was written in [[Python (programming language)|Python]], using Flask and the [[Qt (software)|Qt framework]].{{cite web |title=pgAdmin 4 README |website=[[GitHub]] |url=https://github.com/postgres/pgadmin4/blob/master/README |access-date=August 15, 2018}} [429] => ; 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. [430] => ; 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. [431] => ; 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 autocompletion, 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 connection]]s. Installers are available for Windows, Macintosh, and Linux, and a simple cross-platform archive that runs from a script. [432] => ; LibreOffice, OpenOffice.org: [[LibreOffice]] and [[OpenOffice.org]] Base can be used as a front-end for PostgreSQL. [433] => ; pgBadger: The pgBadger PostgreSQL log analyzer generates detailed reports from a PostgreSQL log file. [434] => ; 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.{{cite web |title=pgDevOps |url=https://www.bigsql.org/pgdevops/ |website=BigSQL.org |access-date=May 4, 2017 |archive-url=https://web.archive.org/web/20170401220832/http://www1.bigsql.org/pgdevops/ |archive-date=April 1, 2017 |url-status=dead}} [435] => ; Adminer: [[Adminer]] is a simple web-based administration tool for PostgreSQL and others, written in PHP. [436] => ; pgBackRest: pgBackRest is a backup and restore tool for PostgreSQL that provides support for full, differential, and incremental backups.{{Cite web|url=https://github.com/pgbackrest/pgbackrest|title=pgbackrest/pgbackrest|website=GitHub|date=November 21, 2021}} [437] => ; pgaudit: pgaudit is a PostgreSQL extension that provides detailed session and/or object audit logging via the standard logging facility provided by PostgreSQL.{{Cite web|url=https://github.com/pgaudit/pgaudit|title=pgaudit/pgaudit|website=GitHub|date=November 21, 2021}} [438] => ; wal-e: Wal-e is a backup and restore tool for PostgreSQL that provides support for physical (WAL based) backups, written in Python{{Cite web|url=https://github.com/wal-e/wal-e|title=wal-e/wal-e|date=June 24, 2021|via=GitHub}} [439] => [440] => 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. [441] => [442] => == Notable users == [443] => [445] => [446] => Notable organizations and products that use PostgreSQL as the primary database include: [447] => [448] => * [[Microsoft]], used for a petabyte-scale “Release Quality View” (RQV) analytics dashboard, which tracks quality of Windows updates analyzing 20K types of metrics from over 800M Windows devices. [449] => * In 2009, the social-networking website [[Myspace]] used [[Aster Data Systems]]'s nCluster database for data warehousing, which was built on unmodified PostgreSQL. [450] => * [[Geni.com]] uses PostgreSQL for their main genealogy database. [451] => * [[OpenStreetMap]], a collaborative project to create a free editable map of the world. [452] => * [[Afilias]], domain registries for [[.org]], [[.info]] and others. [453] => * [[Sony Online]] multiplayer online games. [454] => * [[BASF]], shopping platform for their agribusiness portal. [455] => * [[Reddit]] social news website. [456] => * [[Skype]] VoIP application, central [[business]] databases.{{Cite web |url=https://wiki.postgresql.org/images/a/a9/Postgresql-at-skype.pdf |title=PostgreSQL @Skype |last=Pihlak |first=Martin |website=wiki.postgresql.org |access-date=January 16, 2019}} [457] => * [[Sun xVM]], Sun's virtualization and datacenter automation suite. [458] => * [[MusicBrainz]], open online music encyclopedia. [459] => * The [[International Space Station]] – to collect telemetry data in orbit and replicate it to the ground. [460] => * [[MyYearbook]] social-networking site. [461] => * [[Instagram]], a mobile photo-sharing service. [462] => * [[Disqus]], an online discussion and commenting service. [463] => * [[TripAdvisor]], travel-information website of mostly user-generated content. [464] => * [[Yandex]], a Russian internet company switched its Yandex.Mail service from Oracle to Postgres.{{Cite web |url=https://news.ycombinator.com/item?id=12489055 |title=Yandex.Mail's successful migration from Oracle to Postgres [pdf] |website=Hacker News: news.ycombinator.com |access-date=September 28, 2016}} [465] => * [[Amazon Redshift]], part of AWS, a columnar [[online analytical processing]] (OLAP) system based on [[ParAccel]]'s Postgres modifications. [466] => * [[National Oceanic and Atmospheric Administration]]'s (NOAA) [[National Weather Service]] (NWS), Interactive Forecast Preparation System (IFPS), a system that integrates data from the [[NEXRAD]] [[weather radar]]s, surface, and [[hydrology]] systems to build detailed localized forecast models.{{cite book |author=W. Jason Gilmore |author2=R.H. Treat |title=Beginning PHP and PostgreSQL 8: From Novice to Professional |url=https://books.google.com/books?id=BiRC4JtQzFIC&pg=PA577 |access-date=August 30, 2017 |year=2006 |publisher=Apress |isbn=978-1-43020-136-6}}{{cite book |author=S. Riggs |author2=G. Ciolli |author3=H. Krosing |author4=G. Bartolini |title=PostgreSQL 9 Administration Cookbook - Second Edition |url=https://books.google.com/books?id=rYrwCAAAQBAJ&pg=PA3 |access-date=September 5, 2017 |year=2015 |publisher=Packt |isbn=978-1-84951-906-9}} [467] => * [[United Kingdom]]'s national weather service, [[Met Office]], has begun swapping Oracle for PostgreSQL in a strategy to deploy more open source technology.{{Cite news |url=https://www.computerweekly.com/ezine/Computer-Weekly/The-Met-Office-turns-to-open-source/Met-Office-swaps-Oracle-for-PostgreSQL |title=Met Office swaps Oracle for PostgreSQL |website=computerweekly.com |date=June 17, 2014|access-date=September 5, 2017}} [468] => * [[WhitePages.com]] had been using Oracle and [[MySQL]], but when it came to moving its core directories in-house, it turned to PostgreSQL. Because WhitePages.com needs to combine large sets of data from multiple sources, PostgreSQL's ability to load and index data at high rates was a key to its decision to use PostgreSQL. [469] => * [[FlightAware]], a flight tracking website.{{cite web |title=Open Source Software |url=https://flightaware.com/about/code/ |website=FlightAware |access-date=November 22, 2017}} [470] => * [[Grofers]], an online grocery delivery service.{{Cite news |url=https://lambda.grofers.com/ansible-at-grofers-part-2-managing-postgresql-c4069ce5855b |title=Ansible at Grofers (Part 2) — Managing PostgreSQL |date=February 28, 2017 |work=Lambda - The Grofers Engineering Blog |access-date=September 5, 2018}} [471] => * ''[[The Guardian]]'' migrated from [[MongoDB]] to PostgreSQL in 2018.{{Cite news |last1=McMahon |first1=Philip |last2=Chiorean |first2=Maria-Livia |last3=Coleman |first3=Susie |last4=Askoolum |first4=Akash |url=https://www.theguardian.com/info/2018/nov/30/bye-bye-mongo-hello-postgres |title=Digital Blog: Bye bye Mongo, Hello Postgres |date=November 30, 2018 |work=[[The Guardian]] |language=en-GB |issn=0261-3077}} [472] => * [[YugabyteDB]] implements the PostgreSQL query layer as its default SQL mode [473] => * [[OpenAI]] uses PostgreSQL as part of its primary API service.{{Cite web |title=Elevated Errors on API and ChatGPT |url=https://status.openai.com/incidents/n254wyd7nml7 |access-date=December 2, 2023}} [474] => [475] => == Service implementations == [476] => Some notable vendors offer PostgreSQL as [[software as a service]]: [477] => [478] => * [[Heroku]], a [[platform as a service]] provider, has supported PostgreSQL since the start in 2007. They offer value-add features like full database ''roll-back'' (ability to restore a database from any specified time), which is based on WAL-E, open-source software developed by Heroku. [479] => * 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]]. Since 2015, Postgres Advanced Server has been offered as ApsaraDB for PPAS, a relational database as a service on Alibaba Cloud.{{Cite web|date=2018-09-26|title=Alibaba Cloud Expands Technical Partnership with EnterpriseDB|url=https://www.milestonepartners.com/alibaba-cloud-expands-technical-partnership-with-enterprisedb/|access-date=2020-06-09|website=Milestone Partners|language=en-US}} [480] => * [[VMware]] has offered vFabric Postgres (also termed vPostgres{{cite book [481] => |last1=O'Doherty [482] => |first1=Paul [483] => |last2=Asselin [484] => |first2=Stephane [485] => |chapter=3: VMware Workspace Architecture [486] => |title=VMware Horizon Suite: Building End-User Services [487] => |url=https://books.google.com/books?id=1mTYAwAAQBAJ [488] => |series=VMware Press Technology [489] => |location=Upper Saddle River, NJ [490] => |publisher=VMware Press [491] => |date=2014 [492] => |page=65 [493] => |isbn=978-0-13-347910-2 [494] => |access-date=September 19, 2016 [495] => |quote=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.}}) for private clouds on [[VMware vSphere]] since May 2012. The company announced End of Availability (EOA) of the product in 2014.{{Cite web |date=1 September 2014 |title=VMware vFabric Suite EOA |url=https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/VMware-vFabric-Suite-EOA-FAQ.pdf |access-date=17 December 2023 }} [496] => * In November 2013, [[Amazon Web Services]] announced the addition of PostgreSQL to their [[Amazon Relational Database Service|Relational Database Service]] offering. [497] => * In November 2016, [[Amazon Web Services]] announced the addition of PostgreSQL compatibility to their cloud-native [[Amazon Aurora]] managed database offering.{{Cite web |url=https://aws.amazon.com/blogs/aws/amazon-aurora-update-postgresql-compatibility/ |title=Amazon Aurora Update – PostgreSQL Compatibility |website=AWS Blog |access-date=December 1, 2016|date=November 30, 2016 }} [498] => * In May 2017, [[Microsoft Azure]] announced Azure Databases for PostgreSQL.{{Cite web |url=https://azure.microsoft.com/en-us/blog/azure-database-for-mysql-public-preview/|title=Announcing Azure Database for PostgreSQL| website=Azure Blog|date=May 10, 2017 |access-date=June 19, 2019}} [499] => * In May 2019, [[Alibaba Cloud]] announced PolarDB for PostgreSQL.{{Cite web|url=https://developpaper.com/aliyun-polardb-released-major-updates-to-support-one-click-migration-of-databases-such-as-oracle-to-the-cloud/|title=Aliyun PolarDB released major updates to support one-click migration of databases such as Oracle to the cloud|date=July 6, 2019|website=Develop Paper}} [500] => * [[Jelastic]] [[Multicloud]] [[Platform as a Service]] has provided container-based PostgreSQL support since 2011. It also offers automated asynchronous master-slave replication of PostgreSQL. [501] => * In June 2019, [[IBM Cloud]] announced IBM Cloud Hyper Protect DBaaS for PostgreSQL.{{Cite web|title=IBM Cloud Hyper Protect DBaaS for PostgreSQL documentation|url=https://cloud.ibm.com/docs/hyper-protect-dbaas-for-postgresql?topic=hyper-protect-dbaas-for-postgresql-gettingstarted|access-date=2020-06-24|website=cloud.ibm.com|language=en-us}} [502] => * In September 2020, Crunchy Data announced Crunchy Bridge.{{Cite web|title=Crunchy Data Continues PostgreSQL Support with the Release of Crunchy Bridge|url=https://www.dbta.com/Editorial/News-Flashes/Crunchy-Data-Continues-PostgreSQL-Support-with-the-Release-of-Crunchy-Bridge-142951|date=September 18, 2020}} [503] => * In June 2022, Neon.tech announced Neon Serverless Postgres.{{Cite web|title=SELECT 'Hello, World' Serverless Postgres built for the cloud|url=https://neon.tech/blog/hello-world|date=June 15, 2022}} [504] => [505] => == Release history == [506] => {| class="wikitable" [507] => |- [508] => |+ Release history [509] => |- [510] => ! scope="col" | Release [511] => ! scope="col" | First release [512] => ! scope="col" | Latest minor version [513] => ! scope="col" | Latest release [514] => ! scope="col" | End of
life{{cite web |title=Versioning policy |publisher=PostgreSQL Global Development Group |url=https://www.postgresql.org/support/versioning/ |access-date=October 4, 2018}} [515] => ! scope="col" | Milestones [516] => |- [517] => ! scope="row" | 6.0 [518] => | style=white-space:nowrap | 1997-01-29 [519] => | {{NA}} [520] => | {{NA}} [521] => | {{NA}} [522] => | First formal release of PostgreSQL, unique indexes, pg_dumpall utility, ident authentication [523] => |- [524] => ! scope="row" | 6.1 [525] => | style=white-space:nowrap | 1997-06-08 [526] => | {{Version |o |6.1.1 |style=text-align:center; white-space:nowrap}} [527] => | 1997-07-22 [528] => | {{NA}} [529] => | Multicolumn indexes, sequences, money data type, GEQO (GEnetic Query Optimizer) [530] => |- [531] => ! scope="row" | 6.2 [532] => | 1997-10-02 [533] => | {{Version |o |6.2.1 |style=text-align:center}} [534] => | 1997-10-17 [535] => | {{NA}} [536] => | JDBC interface, triggers, server programming interface, constraints [537] => |- [538] => ! scope="row" | 6.3 [539] => | 1998-03-01 [540] => | {{Version |o |6.3.2 |style=text-align:center}} [541] => | 1998-04-07 [542] => | 2003-03-01 [543] => | SQL-92 subselect ability, PL/pgTCL [544] => |- [545] => ! scope="row" | 6.4 [546] => | 1998-10-30 [547] => | {{Version |o |6.4.2 |style=text-align:center}} [548] => | 1998-12-20 [549] => | 2003-10-30 [550] => | VIEWs (then only read-only) and RULEs, [[PL/pgSQL]] [551] => |- [552] => ! scope="row" | 6.5 [553] => | 1999-06-09 [554] => | {{Version |o |6.5.3 |style=text-align:center}} [555] => | style=white-space:nowrap | 1999-10-13 [556] => | style=white-space:nowrap | 2004-06-09 [557] => | [[Multiversion concurrency control|MVCC]], temporary tables, more SQL statement support (CASE, INTERSECT, and EXCEPT) [558] => |- [559] => ! scope="row" | 7.0 [560] => | 2000-05-08 [561] => | {{Version |o |7.0.3 |style=text-align:center}} [562] => | 2000-11-11 [563] => | 2004-05-08 [564] => | Foreign keys, SQL-92 syntax for joins [565] => |- [566] => ! scope="row" | 7.1 [567] => | 2001-04-13 [568] => | {{Version |o |7.1.3 |style=text-align:center}} [569] => | 2001-08-15 [570] => | 2006-04-13 [571] => | Write-ahead log, outer joins [572] => |- [573] => ! scope="row" | 7.2 [574] => | 2002-02-04 [575] => | {{Version |o |7.2.8 |style=text-align:center}} [576] => | 2005-05-09 [577] => | 2007-02-04 [578] => | PL/Python, [[Object identifier|OIDs]] no longer required, [[Internationalization and localization|internationalization]] of messages [579] => |- [580] => ! scope="row" | 7.3 [581] => | 2002-11-27 [582] => | {{Version |o |7.3.21 |style=text-align:center}} [583] => | 2008-01-07 [584] => | 2007-11-27 [585] => | Schema, table function, [[prepared query]]{{cite magazine |first=Lisa |last=Vaas |date=December 2, 2002 |title=Databases Target Enterprises |url=https://www.eweek.com/c/a/Database/Databases-Target-Enterprises |magazine=[[eWeek]] |access-date=October 29, 2016}} [586] => |- [587] => ! scope="row" | 7.4 [588] => | 2003-11-17 [589] => | {{Version |o |7.4.30 |style=text-align:center}} [590] => | 2010-10-04 [591] => | 2010-10-01 [592] => | Optimization on JOINs and [[data warehouse]] functions{{cite magazine |last=Krill |first=Paul |date=November 20, 2003 |title=PostgreSQL boosts open source database |url=https://www.infoworld.com/article/2670451/database/postgresql-boosts-open-source-database.html |magazine=[[InfoWorld]] |access-date=October 21, 2016}} [593] => |- [594] => ! scope="row" | 8.0 [595] => | 2005-01-19 [596] => | {{Version |o |8.0.26 |style=text-align:center}} [597] => | 2010-10-04 [598] => | 2010-10-01 [599] => | Native server on [[Microsoft Windows]], [[savepoint]]s, [[tablespace]]s, [[point-in-time recovery]]{{cite magazine |last=Krill |first=Paul |date=January 19, 2005 |title=PostgreSQL open source database boasts Windows boost |url=https://www.infoworld.com/article/2668622/operating-systems/postgresql-open-source-database-boasts-windows-boost.html |magazine=[[InfoWorld]] |access-date=November 2, 2016}} [600] => |- [601] => ! scope="row" | 8.1 [602] => | 2005-11-08 [603] => | {{Version |o |8.1.23 |style=text-align:center}} [604] => | 2010-12-16 [605] => | 2010-11-08 [606] => | Performance optimization, two-phase commit, table [[Partition (database)|partitioning]], index bitmap scan, shared row locking, roles [607] => |- [608] => ! scope="row" | 8.2 [609] => | 2006-12-05 [610] => | {{Version |o |8.2.23 |style=text-align:center}} [611] => | 2011-12-05 [612] => | 2011-12-05 [613] => | Performance optimization, online index builds, advisory locks, warm standby{{cite magazine |last=Weiss |first=Todd R. |date=December 5, 2006 |title=Version 8.2 of open-source PostgreSQL DB released |url=https://www.computerworld.com/article/2548483 |magazine=[[Computerworld]] |access-date=October 17, 2016}} [614] => |- [615] => ! scope="row" | 8.3 [616] => | 2008-02-04 [617] => | {{Version |o |8.3.23 |style=text-align:center}} [618] => | 2013-02-07 [619] => | 2013-02-07 [620] => | Heap-only tuples, [[full text search]],{{cite magazine |last=Gilbertson |first=Scott |date=February 5, 2008 |title=PostgreSQL 8.3: Open Source Database Promises Blazing Speed |url=https://www.wired.com/2008/02/postgresql_8dot3_open_source_database_promises_blazing_speed/ |magazine=[[Wired (magazine)|Wired]] |access-date=October 17, 2016}} [[SQL/XML]], ENUM types, [[Universally unique identifier|UUID]] types [621] => |- [622] => ! scope="row" | 8.4 [623] => | 2009-07-01 [624] => | {{Version |o |8.4.22 |style=text-align:center}} [625] => | 2014-07-24 [626] => | 2014-07-24 [627] => | [[Window_function_%28SQL%29|Window functions]], column-level permissions, parallel database restore, per-database collation, [[common table expressions]] and recursive queries{{cite magazine |last=Huber |first=Mathias |date=July 2, 2009 |title=PostgreSQL 8.4 Proves Feature-Rich |url=https://www.linux-magazine.com/Online/News/PostgreSQL-8.4-Proves-Feature-Rich/(language)/eng-US |magazine=[[Linux Magazine]] |access-date=October 17, 2016}} [628] => |- [629] => ! scope="row" | 9.0 [630] => | 2010-09-20 [631] => | {{Version |o |9.0.23 |style=text-align:center}} [632] => | 2015-10-08 [633] => | 2015-10-08 [634] => | Built-in binary streaming [[Replication (computing)|replication]], [[hot standby]], in-place upgrade ability, 64-bit Windows{{cite web |url=https://www.linux.com/news/five-enterprise-features-postgresql-9 |title=Five Enterprise Features in PostgreSQL 9 |last=Brockmeier |first=Joe |date=September 30, 2010 |website=[[Linux.com]] |publisher=[[Linux Foundation]] |access-date=February 6, 2017}} [635] => |- [636] => ! scope="row" | 9.1 [637] => | 2011-09-12 [638] => | {{Version |o |9.1.24 |style=text-align:center}} [639] => | 2016-10-27 [640] => | 2016-10-27 [641] => | [[Synchronous replication]], per-column [[collation]]s, unlogged tables, [[serializable snapshot isolation]], writeable common table expressions, [[Security-Enhanced Linux|SELinux]] integration, extensions, foreign tables{{cite magazine |author=Timothy Prickett Morgan |date=September 12, 2011 |title=PostgreSQL revs to 9.1, aims for enterprise |url=https://www.theregister.co.uk/2011/09/12/postgresql_9_1_cloud_server/ |magazine=[[The Register]] |access-date=February 6, 2017}} [642] => |- [643] => ! scope="row" | 9.2 [644] => | 2012-09-10{{Cite web |url=https://www.postgresql.org/about/news/1415/ |title=PostgreSQL: PostgreSQL 9.2 released |website=www.postgresql.org|date=September 10, 2012 }} [645] => | {{Version |o |9.2.24 |style=text-align:center}} [646] => | 2017-11-09 [647] => | 2017-11-09 [648] => | Cascading streaming replication, index-only scans, native [[JSON]] support, improved lock management, range types, pg_receivexlog tool, space-partitioned GiST indexes [649] => |- [650] => ! scope="row" | 9.3 [651] => | 2013-09-09 [652] => | {{Version |o |9.3.25 |style=text-align:center}} [653] => | 2018-11-08 [654] => | 2018-11-08 [655] => | 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 view]]s, replication improvements [656] => |- [657] => ! scope="row" | 9.4 [658] => | 2014-12-18 [659] => | {{Version |o |9.4.26 |style=text-align:center}} [660] => | 2020-02-13 [661] => | 2020-02-13 [662] => | 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, reintroducing Hstore as the column type of choice for document-style data.{{Cite web |url=https://www.infoq.com/news/2013/11/Nested-Hstore |title=Reintroducing Hstore for PostgreSQL |website=InfoQ}} [663] => |- [664] => ! scope="row" | 9.5 [665] => | 2016-01-07 [666] => | {{Version |o |9.5.25 |style=text-align:center}} [667] => | 2021-02-11 [668] => | 2021-02-11 [669] => | UPSERT, row level security, TABLESAMPLE, CUBE/ROLLUP, GROUPING SETS, and new [[Block Range Index|BRIN]] index{{cite magazine |last=Richard |first=Chirgwin |date=January 7, 2016 |title=Say oops, UPSERT your head: PostgreSQL version 9.5 has landed |url=https://www.theregister.co.uk/2016/01/07/postgresql_95_lands/ |magazine=[[The Register]] |access-date=October 17, 2016}} [670] => |- [671] => ! scope="row" | 9.6 [672] => | 2016-09-29 [673] => | {{Version |o |9.6.24 |style=text-align:center}} [674] => | 2021-11-11 [675] => | 2021-11-11 [676] => | Parallel query support, PostgreSQL foreign data wrapper (FDW) improvements with sort/join pushdown, multiple synchronous standbys, faster vacuuming of large table [677] => |- [678] => ! scope="row" | 10 [679] => | 2017-10-05 [680] => | {{Version |o |10.23 |style=text-align:center}} [681] => | 2022-11-10 [682] => | 2022-11-10 [683] => | Logical replication,{{Cite web |url=https://www.postgresql.org/docs/10/logical-replication.html |title=PostgreSQL: Documentation: 10: Chapter 31. Logical Replication |website=www.postgresql.org|date=August 12, 2021 }} declarative table partitioning, improved query parallelism [684] => |- [685] => ! scope="row" | 11 [686] => | 2018-10-18 [687] => | {{Version |o |11.22 |style=text-align:center}} [688] => | 2023-11-09 [689] => | 2023-11-09 [690] => | Increased robustness and performance for partitioning, transactions supported in stored procedures, enhanced abilities for query parallelism, just-in-time (JIT) compiling for expressions{{cite web |title=PostgreSQL 11 Released |date=October 18, 2018 |url=https://www.postgresql.org/about/news/1894/ |access-date=October 18, 2018}}{{cite web |title=PostgreSQLRelease Notes |url=https://www.postgresql.org/docs/11/static/release-11.html |access-date=October 18, 2018}} [691] => |- [692] => ! scope="row" | 12 [693] => | 2019-10-03 [694] => | {{Version |co |12.18 |style=text-align:center}} [695] => | 2024-02-08 [696] => | 2024-11-14 [697] => | Improvements to query performance and space utilization; SQL/JSON path expression support; generated columns; improvements to internationalization, and authentication; new pluggable table storage interface.{{Cite news|url=https://www.postgresql.org/about/news/1976/|title=PostgreSQL: PostgreSQL 12 Released!|newspaper=Postgresql News|date=October 3, 2019}} [698] => |- [699] => ! scope="row" | 13 [700] => | 2020-09-24 [701] => | {{Version |co |13.14 |style=text-align:center}} [702] => | 2024-02-08 [703] => | 2025-11-13 [704] => | Space savings and performance gains from de-duplication of B-tree index entries, improved performance for queries that use aggregates or partitioned tables, better query planning when using extended statistics, parallelized vacuuming of indexes, incremental sorting{{Cite web|url=https://www.postgresql.org/docs/13/release-13.html|title=PostgreSQL 13 Release Notes|website=www.postgresql.org|date=August 12, 2021}}{{Cite web|url=https://www.postgresql.org/about/news/postgresql-13-released-2077/|title=PostgreSQL 13 Released!|website=www.postgresql.org|date=September 24, 2020}} [705] => |- [706] => ! scope="row" | 14 [707] => | 2021-09-30 [708] => | {{Version |co |14.11 |style=text-align:center; white-space:nowrap}} [709] => | 2024-02-08 [710] => | 2026-11-12 [711] => | Added SQL-standard SEARCH and CYCLE clauses for common table expressions, allow DISTINCT to be added to GROUP BY{{Cite web|url=https://www.postgresql.org/docs/14/release-14.html|title=PostgreSQL 14 Release Notes|website=www.postgresql.org|date=November 11, 2021}}{{Cite web|url=https://www.postgresql.org/about/news/postgresql-14-released-2318/|title=PostgreSQL 14 Released!|website=www.postgresql.org|date=September 30, 2021}} [712] => |- [713] => ! scope="row" | 15 [714] => | 2022-10-13 [715] => | {{Version |co |15.6 |style=text-align:center}} [716] => | 2024-02-08 [717] => | 2027-11-11 [718] => | Implements SQL-standard [[Merge (SQL)|MERGE]] statement. PL/Python now only supports current {{nowrap|Python 3}}, and {{code|plpythonu}} now means {{nowrap|Python 3}}, no longer the discontinued {{nowrap|Python 2}}. [719] => |- [720] => ! scope="row" | 16 [721] => | 2023-09-14 [722] => | {{Version |c |16.2 |style=text-align:center; white-space:nowrap}} [723] => | 2024-02-08 [724] => | 2028-11-09 [725] => | Improvements to logical replication, pg_stat_io view (for I/O metrics){{cite web | url=https://www.postgresql.org/about/news/postgresql-16-released-2715/ | title=PostgreSQL 16 Released! | date=September 14, 2023 }} [726] => |- [727] => !17 [728] => |Sep 2024{{Cite web |title=PostgreSQL: Roadmap |url=https://www.postgresql.org/developer/roadmap/ |access-date=2024-02-15 |website=www.postgresql.org}} [729] => | {{Version |p |17.0 |style=text-align:center; white-space:nowrap}} [730] => | {{NA}} [731] => | {{NA}} [732] => | {{NA}} [733] => |} [734] => {{Version |l |show=111111}} [735] => {{Timeline PostgreSQL}} [736] => [737] => == See also == [738] => {{Portal|Free and open-source software}} [739] => [740] => * [[Comparison of relational database management systems]] [741] => * [[Database scalability]] [742] => * [[List of databases using MVCC]] [743] => * [[LLVM]] (llvmjit is the JIT engine used by PostgreSQL) [744] => [745] => == References == [746] => {{reflist|refs= [747] => {{cite web |url=https://www.postgresql.org/about/news/978/ |title=Happy Birthday, PostgreSQL! |date=July 8, 2008 |publisher=PostgreSQL Global Development Group}} [748] => {{cite web |date=February 18, 2010 |title=PostgreSQL licence approved by OSI |url=http://www.crynwr.com/cgi-bin/ezmlm-cgi?17:mmp:969 |publisher=Crynwr |access-date=February 18, 2010 |archive-url=https://web.archive.org/web/20160808093031/http://www.crynwr.com/cgi-bin/ezmlm-cgi?17:mmp:969 |archive-date=August 8, 2016 |url-status=dead}} [749] => {{cite web |publisher=Open Source Initiative |date=February 20, 2010 |title=OSI PostgreSQL Licence |url=https://www.opensource.org/licenses/postgresql |access-date=February 20, 2010}} [750] => {{cite web |url=https://www.postgresql.org/about/licence |title=License |publisher=PostgreSQL Global Development Group |access-date=September 20, 2010}} [751] => {{cite web |url=https://www.postgresql.org/docs/current/static/intro-whatis.html |title=What is PostgreSQL? |work=PostgreSQL 9.3.0 Documentation |publisher=PostgreSQL Global Development Group |access-date=September 20, 2013}} [752] => [753] => [754] => {{cite web |url=https://www.postgresql.org/community/contributors/ |title=Contributor Profiles |publisher=PostgreSQL Global Development Group |access-date=March 14, 2017}} [755] => [756] => {{Cite web|url=https://www.postgresql.org/files/postgresql.mp3|title=Audio sample, 5.6k MP3}} [757] => {{cite web |date=November 16, 2007 |title=Project name – statement from the core team |publisher=archives.postgresql.org |url=http://archives.postgresql.org/pgsql-advocacy/2007-11/msg00109.php |access-date=November 16, 2007}} [758] => {{cite conference |last1=Stonebraker |first1=M. |last2=Rowe |first2=L. A. |date=May 1986 |title=The design of POSTGRES |conference=Proc. 1986 ACM [[SIGMOD]] Conference on Management of Data |location=Washington, DC |url=http://db.cs.berkeley.edu/papers/ERL-M85-95.pdf |access-date=December 17, 2011}} [759] => {{cite web |url=https://www.postgresql.org/about/history/ |title=PostgreSQL: History |publisher=PostgreSQL Global Development Group |access-date=August 27, 2016 |archive-url=https://web.archive.org/web/20170326020245/https://www.postgresql.org/about/history/ |archive-date=March 26, 2017 |url-status=dead}} [760] => {{cite conference |url=http://db.cs.berkeley.edu/papers/ERL-M87-13.pdf |title=The POSTGRES data model |last1=Stonebraker |first1=M. |last2=Rowe |first2=L. A. |publisher=Morgan Kaufmann Publishers |conference=Proceedings of the 13th International Conference on Very Large Data Bases |location=Brighton, England |isbn=0-934613-46-X |pages=83–96}} [761] => {{cite web |author=Pavel Stehule |date=9 June 2012 |title=Historie projektu PostgreSQL |language=cs |url=http://postgres.cz/wiki/Historie_projektu_PostgreSQL}} [762] => {{cite web |url=http://db.cs.berkeley.edu/postgres.html |title=University POSTGRES, Version 4.2 |date=July 26, 1999}} [763] => {{cite mailing list |url=https://www.postgresql.org/message-id/CA+OCxozS_cuaLw=nfS=GdJZmS7ygjhdtZbqVt17wPLfCOtFY4g@mail.gmail.com |title=Re: 20th anniversary of PostgreSQL ? |date=April 7, 2015 |access-date=April 9, 2015 |mailing-list=pgsql-advocacy |last=Page |first=Dave}} [764] => {{cite journal |title=Serializable Snapshot Isolation in PostgreSQL |author=Dan R. K. Ports |author2=Kevin Grittner |year=2012 |journal=Proceedings of the VLDB Endowment |volume=5 |issue=12 |pages=1850–1861 |url=http://drkp.net/drkp/papers/ssi-vldb12.pdf |doi=10.14778/2367502.2367523 |arxiv=1208.4179|bibcode=2012arXiv1208.4179P |s2cid=16006111}} [765] => {{citation |publisher=H Online |url=http://www.h-online.com/open/news/item/PostgreSQL-9-1-with-synchronous-replication-1341228.html |type=news |title=PostgreSQL 9.1 with synchronous replication}} [766] => {{cite conference |last1=Bartunov |first1=O |last2=Sigaev |first2=T |date=May 2011 |title=SP-GiST – a new indexing framework for PostgreSQL |conference=PGCon 2011 |location=Ottawa, Canada |url=http://www.pgcon.org/2011/schedule/attachments/197_pgcon-2011.pdf |access-date=January 31, 2016}} [767] => {{cite conference |last1=Bartunov |first1=O |last2=Sigaev |first2=T |date=May 2010 |title=K-nearest neighbour search for PostgreSQL |conference=PGCon 2010 |location=Ottawa, Canada |url=http://www.pgcon.org/2010/schedule/attachments/168_pgcon-2010-1.pdf |access-date=January 31, 2016}} [768] => {{cite web |publisher=Postgres-XC |url=http://postgres-xc.sourceforge.net/ |type=website |title=Postgres-XC project page |url-status=dead |archive-url=https://web.archive.org/web/20120701122448/http://postgres-xc.sourceforge.net/ |archive-date=July 1, 2012 |df=mdy-all}} [769] => {{cite press release |author=Marit Fischer |date=November 10, 2007 |title=Backcountry.com finally gives something back to the open source community |publisher=Backcountry.com |url=http://www.backcountrycorp.com/corporate/section/3/press/a511/Backcountry-finally-gives-something-back-to-the-open-source-community.html |url-status=dead |archive-url=https://web.archive.org/web/20101226124550/http://www.backcountrycorp.com/corporate/section/3/press/a511/Backcountry-finally-gives-something-back-to-the-open-source-community.html |archive-date=December 26, 2010 |df=mdy-all}} [770] => {{cite web |first=Peter |last=Geoghegan |date=March 23, 2014 |title=What I think of jsonb |url=http://pgeoghegan.blogspot.com/2014/03/what-i-think-of-jsonb.html}} [771] => {{cite web |url=http://initd.org/psycopg/ |title=PostgreSQL + Python | Psycopg |work=initd.org}} [772] => {{cite web |date=March 4, 2013 |title=Add a materialized view relations |url=https://www.postgresql.org/message-id/E1UCJDN-00042x-0w@gemulon.postgresql.org |access-date=March 4, 2013}} [773] => {{cite web |date=December 8, 2012 |title=Support automatically-updatable views |url=http://archives.postgresql.org/pgsql-committers/2012-12/msg00154.php |access-date=December 8, 2012}} [774] => {{cite web |date=February 1, 2013 |title=Add CREATE RECURSIVE VIEW syntax |url=https://www.postgresql.org/message-id/E1U17NB-0006c6-DX@gemulon.postgresql.org |access-date=February 28, 2013}} [775] => {{cite book |url=https://www.postgresql.org/files/documentation/books/aw_pgsql/15467.html |title=PostgreSQL: Introduction and Concepts | chapter-url=https://www.postgresql.org/files/documentation/books/aw_pgsql/node81.html |chapter=Subqueries |last=Momjian |first=Bruce |publisher=Addison-Wesley |isbn=0-201-70331-9 |year=2001 |access-date=September 25, 2010 |archive-url=https://web.archive.org/web/20100809013228/http://www.postgresql.org/files/documentation/books/aw_pgsql/15467.html |archive-date=August 9, 2010 |url-status=dead |df=mdy-all}} [776] => {{cite web |url=http://www.oreillynet.com/pub/a/databases/2006/02/02/postgresq_regexes.html |title=Using Regular Expressions in PostgreSQL |last=Bernier |first=Robert |publisher=[[O'Reilly Media]] |date=February 2, 2006 |access-date=September 25, 2010}} [777] => {{cite web |url=http://blog.hagander.net/archives/222-A-few-short-notes-about-PostgreSQL-and-POODLE.html |title=A few short notes about PostgreSQL and POODLE |work=hagander.net}} [778] => {{cite web |last=Berkus |first=Josh |date=July 6, 2007 |title=PostgreSQL publishes first real benchmark |url=http://blogs.ittoolbox.com/database/soup/archives/postgresql-publishes-first-real-benchmark-17470 |access-date=July 10, 2007 |archive-url=https://web.archive.org/web/20070712092901/http://blogs.ittoolbox.com/database/soup/archives/postgresql-publishes-first-real-benchmark-17470 |archive-date=July 12, 2007 |url-status=dead |df=mdy-all}} [779] => {{cite web |last=Vilmos |first=György |date=September 29, 2009 |title=PostgreSQL history |url=http://suckit.blog.hu/2009/09/29/postgresql_history |access-date=August 28, 2010}} [780] => {{cite web |publisher=[[SPEC]] |date=July 6, 2007 |title=SPECjAppServer2004 Result |url=http://www.spec.org/jAppServer2004/results/res2007q3/jAppServer2004-20070606-00065.html |access-date=July 10, 2007}} [781] => {{cite web |publisher=[[SPEC]] |date=July 4, 2007 |title=SPECjAppServer2004 Result |url=http://www.spec.org/jAppServer2004/results/res2007q3/jAppServer2004-20070703-00073.html |access-date=September 1, 2007}} [782] => {{cite web |work=PostgreSQL Manual |publisher=PostgreSQL.org |url=https://www.postgresql.org/docs/current/static/kernel-resources.html |title=Managing Kernel Resources |access-date=November 12, 2011}} [783] => {{cite web |publisher=PostgreSQL.org |author=Greg Smith |author2=Robert Treat |author3=Christopher Browne |name-list-style=amp |url=https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server |work=Wiki |title=Tuning your PostgreSQL server |access-date=November 12, 2011}} [784] => {{cite web |author=Robert Haas |date=April 3, 2012 |title=Did I Say 32 Cores? How about 64? |url=http://rhaas.blogspot.com/2012/04/did-i-say-32-cores-how-about-64.html |access-date=April 8, 2012}} [785] => {{cite web |url=http://lists.debian.org/debian-devel/2012/07/msg00536.html |title=AArch64 planning BoF at DebConf |work=debian.org}} [786] => {{cite web |title=Supported Platforms |publisher=PostgreSQL Global Development Group |url=https://www.postgresql.org/docs/current/static/supported-platforms.html |access-date=April 6, 2012}} [787] => {{cite web |title=pgAdmin: PostgreSQL administration and management tools |work=website |url=http://www.pgadmin.org/ |access-date=November 12, 2011}} [788] => {{cite web |author=phpPgAdmin Project |date=April 25, 2008 |title=About phpPgAdmin |url=http://phppgadmin.sourceforge.net/?page=about |access-date=April 25, 2008}} [789] => {{cite web |author=PostgreSQL Studio |date=October 9, 2013 |title=About PostgreSQL Studio |url=http://www.postgresqlstudio.org/about/ |access-date=October 9, 2013 |archive-url=https://web.archive.org/web/20131007084849/http://www.postgresqlstudio.org/about/ |archive-date=October 7, 2013 |url-status=dead |df=mdy-all}} [790] => {{cite web |date=October 3, 2013 |title=TeamPostgreSQL website |url=http://www.teampostgresql.com |access-date=October 3, 2013}} [791] => {{cite web |author=oooforum.org |date=January 10, 2010 |title=Back Ends for OpenOffice |url=http://www.oooforum.org/forum/viewtopic.phtml?p=356180 |archive-url=https://web.archive.org/web/20110928093709/http://www.oooforum.org/forum/viewtopic.phtml?p=356180 |url-status=dead |archive-date=September 28, 2011 |access-date=January 5, 2011}} [792] => {{cite web |author=libreoffice.org |date=October 14, 2012 |title=Base features |url=http://www.libreoffice.org/features/base/ |access-date=October 14, 2012 |url-status=dead |archive-url=https://web.archive.org/web/20120107063659/http://www.libreoffice.org/features/base/ |archive-date=January 7, 2012 |df=mdy-all}} [793] => {{cite book |author=Greg Smith |title=PostgreSQL 9.0 High Performance |date=15 October 2010 |publisher=[[Packt Publishing]] |isbn=978-1-84951-030-1 |url=http://www.packtpub.com/postgresql-90-high-performance/book}} [794] => {{cite conference |author=Emmanuel Cecchet |date=May 21, 2009 |title=Building PetaByte Warehouses with Unmodified PostgreSQL |conference=PGCon 2009 |url=http://www.pgcon.org/2009/schedule/attachments/135_PGCon%202009%20-%20Aster%20v6.pdf |access-date=November 12, 2011}} [795] => {{cite web |title=MySpace.com scales analytics for all their friends |series=case study |publisher=Aster Data |url=http://www.asterdata.com/resources/assets/cs_Aster_Data_4.0_MySpace.pdf |date=June 15, 2010 |url-status=live |archive-url=https://web.archive.org/web/20101114141918/http://asterdata.com/resources/assets/cs_Aster_Data_4.0_MySpace.pdf |archive-date=November 14, 2010 |access-date=November 12, 2011}} [796] => {{cite web |date=August 1, 2011 |title=Last Weekend's Outage |publisher=Geni |work=Blog |url=http://www.geni.com/blog/last-weekends-outage-368211.html}} [797] => {{cite web |author=Claire Giordano | publisher=Microsoft Tech Community |date=October 31, 2019 |title=Architecting petabyte-scale analytics by scaling out Postgres on Azure with the Citus extension |work=Blog |url=https://techcommunity.microsoft.com/t5/azure-database-for-postgresql/architecting-petabyte-scale-analytics-by-scaling-out-postgres-on/ba-p/969685}} [798] => {{cite web |work=Wiki |url=https://wiki.openstreetmap.org/wiki/Database |title=Database |publisher=OpenStreetMap}} [799] => {{citation |url=https://www.computerworld.com.au/index.php?id=760310963 |title=PostgreSQL affiliates .ORG domain |date=August 24, 2023 |publisher=Computer World |place=Australia}} [800] => {{citation |url=https://www.computerworld.com/databasetopics/data/software/story/0,10801,109722,00.html |publisher=Computer World |title=Sony Online opts for open-source database over Oracle}} [801] => {{cite web |url=https://www.postgresql.org/files/about/casestudies/wcgcasestudyonpostgresqlv1.2.pdf |publisher=PostgreSQL |edition=1.2 |title=A Web Commerce Group Case Study on PostgreSQL}} [802] => {{cite web |date=27 March 2014 |title=Architecture Overview |work=Reddit software wiki |publisher=Reddit |url=https://github.com/reddit/reddit/wiki/Architecture-Overview#reddit-the-software |access-date=November 25, 2014}} [803] => {{cite web |year=2007 |title=How Much Are You Paying For Your Database? |publisher=Sun Microsystems blog |url=http://blogs.sun.com/marchamilton/entry/how_much_are_you_paying |access-date=December 14, 2007 |archive-url=https://web.archive.org/web/20090307032257/http://blogs.sun.com/marchamilton/entry/how_much_are_you_paying |archive-date=March 7, 2009 |url-status=dead |df=mdy-all}} [804] => {{cite web |url=http://musicbrainz.org/doc/Database |title=Database – MusicBrainz |publisher=MusicBrainz Wiki |access-date=February 5, 2011}} [805] => {{cite web |date=July 13, 2010 |author=Duncavage, Daniel P |title=NASA needs Postgres-Nagios help |url=http://archives.postgresql.org/pgsql-general/2010-07/msg00394.php}} [806] => {{cite web |author=Roy, Gavin M |title=PostgreSQL at myYearbook.com |location=USA East |year=2010 |type=talk |url=https://www.postgresqlconference.org/2010/east/talks/postgresql_at_myyearbook.com |publisher=PostgreSQL Conference |url-status=dead |archive-url=https://web.archive.org/web/20110727183016/https://www.postgresqlconference.org/2010/east/talks/postgresql_at_myyearbook.com |archive-date=July 27, 2011 |df=mdy-all}} [807] => {{cite web |url=http://instagram-engineering.tumblr.com/post/20541814340/keeping-instagram-up-with-over-a-million-new-users-in#replicationread-slaves |title=Keeping Instagram up with over a million new users in twelve hours |publisher=Instagram-engineering.tumblr.com |date=May 17, 2011 |access-date=July 7, 2012}} [808] => {{cite web |url=https://speakerdeck.com/mikeclarke/pgcon-2013-keynote-postgres-at-disqus |title=Postgres at Disqus |access-date=May 24, 2013}} [809] => {{cite conference |url=http://www.pgconf.us/2015/event/95/ |title=At the Heart of a Giant: Postgres at TripAdvisor |last=Kelly |first=Matthew |date=March 27, 2015 |conference=PGConf US 2015 |access-date=July 23, 2015 |archive-url=https://web.archive.org/web/20150723181100/http://www.pgconf.us/2015/event/95/ |archive-date=July 23, 2015 |url-status=dead}} ([https://www.youtube.com/watch?v=YquXmwZNnfg Presentation video]) [810] => {{cite news |date=1 April 2013 |author=Alex Williams |title=Heroku Forces Customer Upgrade To Fix Critical PostgreSQL Security Hole |work=TechCrunch |url=https://techcrunch.com/2013/04/01/heroku-forces-customer-upgrade-to-fix-critical-postgresql-security-hole/}} [811] => {{cite news |date=11 November 2013 |author=Barb Darrow |title=Heroku gussies up Postgres with database roll-back and proactive alerts |url=http://gigaom.com/2013/11/11/heroku-gussies-up-postgres-with-database-roll-back-and-proactive-alerts/ |publisher=GigaOM}} [812] => {{cite web |date=26 September 2013 |author=Craig Kerstiens |title=WAL-E and Continuous Protection with Heroku Postgres |publisher=Heroku blog |url=https://blog.heroku.com/archives/2013/9/26/wal_e_and_continuous_protection_with_heroku_postgres}} [813] => {{cite web |url=http://www.techweekeurope.co.uk/news/enterprisedb-offers-up-postgres-plus-cloud-database-57030 |title=EnterpriseDB Offers Up Postgres Plus Cloud Database |publisher=Techweekeurope.co.uk |date=January 27, 2012 |access-date=July 7, 2012}} [814] => {{cite news |date=15 May 2012 |author=Al Sargent |title=Introducing VMware vFabric Suite 5.1: Automated Deployment, New Components, and Open Source Support |url=https://blogs.vmware.com/vfabric/2012/05/announcing-vmware-vfabric-suite-51.html |publisher=VMware blogs}} [815] => {{cite news |date=14 November 2013 |author=Jeff |title=Amazon RDS for PostgreSQL – Now Available |publisher=Amazon Web Services Blog |url=http://aws.typepad.com/aws/2013/11/amazon-rds-for-postgresql-now-available.html}} [816] => {{cite news |date=14 November 2013 |author=Alex Williams |title=PostgreSQL Now Available On Amazon's Relational Database Service |work=TechCrunch |url=https://techcrunch.com/2013/11/14/postgressql-now-available-on-amazons-relational-database-service/}} [817] => {{cite web |url=http://www.postgres-r.org/ |title=Postgres-R: a database replication system for PostgreSQL |publisher=Postgres Global Development Group |access-date=August 27, 2016 |archive-url=https://web.archive.org/web/20100329215559/http://www.postgres-r.org/ |archive-date=March 29, 2010 |url-status=dead}} [818] => {{cite web |url=http://2ndquadrant.com/en/resources/bdr/ |title=Postgres-BDR |publisher=2ndQuadrant Ltd |access-date=August 27, 2016}} [819] => {{cite web |url=http://raspberrypg.org/2015/06/step-5-update-installing-postgresql-on-my-raspberry-pi-1-and-2/ |title=Step 5 (update): Installing PostgreSQL on my Raspberry Pi 1 and 2 |first=Rubens |last=Souza |date=June 17, 2015 |access-date=August 27, 2016 |website=Raspberry PG}} [820] => {{cite web |url=https://dzone.com/articles/asynchronous-master-slave-replication-of-postgresq |title=Asynchronous Master-Slave Replication of PostgreSQL Databases in One Click |publisher=DZone |access-date=May 26, 2017}} [821] => {{cite web |url=https://www.postgresql.org/docs/current/static/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS |title=Case sensitivity of identifiers |date=November 11, 2021 |publisher=PostgreSQL Global Development Group}} [822] => {{cite web |url=https://www.postgresql.org/download/macosx/ |title=Mac OS X packages |publisher=The PostgreSQL Global Development Group |access-date=August 27, 2016}} [823] => }} [824] => [825] => == Further reading == [826] => {{Refbegin}} [827] => * {{cite book |title=PostgreSQL: Up and Running |first1=Regina |last1=Obe |first2=Leo |last2=Hsu |date=July 8, 2012 |publisher=[[O'Reilly Media|O'Reilly]] |isbn=978-1-4493-2633-3 |url=http://www.postgresonline.com/store.php?asin=1449326331}} [828] => * {{cite book |title=PostgreSQL Server Programming |edition=second |first1=Hannu |last1=Krosing |first2=Kirk |last2=Roybal |date=June 15, 2013 |publisher=[[Packt Publishing]] |isbn=978-1-84951-698-3 |url=http://www.2ndquadrant.com/books/}} [829] => * {{cite book |title=PostgreSQL 9 Administration Cookbook |edition=second |first1=Simon |last1=Riggs |first2=Hannu |last2=Krosing |date=October 27, 2010 |publisher=[[Packt Publishing]] |isbn=978-1-84951-028-8 |url=http://www.2ndquadrant.com/books/}} [830] => * {{cite book |title=PostgreSQL 9 High Performance |first=Greg |last=Smith |date=October 15, 2010 |publisher=[[Packt Publishing]] |isbn=978-1-84951-030-1 |url=http://www.2ndquadrant.com/books/}} [831] => * {{cite book |title=Beginning PHP and PostgreSQL 8: From Novice to Professional |first1=W. Jason |last1=Gilmore |first2=Robert |last2=Treat |date=February 27, 2006 |publisher=[[Apress]] |isbn=1-59059-547-5 |url=http://www.apress.com/book/view/1590595475 |pages=896 |access-date=April 28, 2009 |archive-url=https://web.archive.org/web/20090708113944/http://www.apress.com/book/view/1590595475 |archive-date=July 8, 2009 |url-status=dead |df=mdy-all}} [832] => * {{cite book |title=PostgreSQL |edition=second |first=Korry |last=Douglas |date=August 5, 2005 |publisher=[[Sams Publishing|Sams]] |isbn=0-672-32756-2 |url=http://www.informit.com/store/product.aspx?isbn=0672327562 |pages=1032}} [833] => * {{cite book |title=Beginning Databases with PostgreSQL |edition=second |first1=Neil |last1=Matthew |first2=Richard |last2=Stones |date=April 6, 2005 |publisher=[[Apress]] |isbn=1-59059-478-9 |url=http://www.apress.com/book/view/9781590594780 |pages=664 |access-date=April 28, 2009 |archive-url=https://web.archive.org/web/20090409150911/http://www.apress.com/book/view/9781590594780 |archive-date=April 9, 2009 |url-status=dead |df=mdy-all}} [834] => * {{cite book |title=Practical PostgreSQL |first1=John C. |last1=Worsley |first2=Joshua D. |last2=Drake |date=January 2002 |publisher=[[O'Reilly Media]] |isbn=1-56592-846-6 |url=https://archive.org/details/practicalpostgre00wors/page/636 |pages=[https://archive.org/details/practicalpostgre00wors/page/636 636] |url-access=registration }} [835] => {{Refend}} [836] => [837] => == External links == [838] => {{Commons category}} [839] => {{Wikibooks|PostgreSQL}} [840] => * {{Official website}}, and [https://wiki.postgresql.org/ wiki] [841] => * A [https://www.postgresql.org/download/product-categories/ Software Catalog] of related projects and products [842] => * The official [https://git.postgresql.org/gitweb/?p=postgresql.git Main Source Code Repository (for browsing)], and the [https://wiki.postgresql.org/wiki/Developer_FAQ Developer FAQ] [843] => * The official [https://www.postgresql.org/docs/current/docguide.html Reference for PostgreSQL Documentation Authors] [844] => * All official [https://git.postgresql.org/ PostgreSQL Source Code Repositories] [845] => * {{Curlie|Computers/Software/Databases/PostgreSQL}} [846] => * {{GitHub|postgres|PostgreSQL}} [847] => [848] => {{Software in the Public Interest}} [849] => {{Authority control}} [850] => [851] => [[Category:PostgreSQL| ]] [852] => [[Category:Client-server database management systems]] [853] => [[Category:Cross-platform software]] [854] => [[Category:Free database management systems]] [855] => [[Category:Free software programmed in C]] [856] => [[Category:ORDBMS software for Linux]] [857] => [[Category:Relational database management software for Linux]] [858] => [[Category:Software that uses Meson]] [859] => [[Category:Vector databases]] [] => )
good wiki

PostgreSQL

PostgreSQL is a popular open-source relational database management system (RDBMS) that is widely used for storing and analyzing structured data. It was first developed at the University of California, Berkeley in 1986 and has since evolved into a powerful and feature-rich database solution.

More about us

About

It was first developed at the University of California, Berkeley in 1986 and has since evolved into a powerful and feature-rich database solution. PostgreSQL is known for its robustness, reliability, and extensibility, making it a preferred choice for many large-scale applications and enterprises. It supports a wide range of data types, including numeric, character, text, boolean, date, time, and geospatial data, and offers various advanced features like transactional integrity, multi-version concurrency control, and point-in-time recovery. One of the key advantages of PostgreSQL is its adherence to the SQL standard, ensuring compatibility with other database systems and making it easy to migrate data from other RDBMS. Additionally, PostgreSQL boasts a vast ecosystem of extensions and plugins that provide additional functionalities, such as full-text search, JSON support, geographic information systems (GIS), and time-series data. The architecture of PostgreSQL follows a client-server model, where multiple clients can connect to a single server and perform concurrent data operations. It supports various programming languages such as C, C++, Java, Python, and others, making it versatile for application development. PostgreSQL has gained significant popularity and a strong community of developers and contributors over the years. The community actively maintains and updates the system, ensuring its security, stability, and performance. This collaborative approach has led to frequent releases and continuous improvement of the database system. Overall, PostgreSQL offers a reliable and flexible solution for data storage and management, and its popularity continues to grow as more users recognize its capabilities and advantages over other RDBMS alternatives.

Expert Team

Vivamus eget neque lacus. Pellentesque egauris ex.

Award winning agency

Lorem ipsum, dolor sit amet consectetur elitorceat .

10 Year Exp.

Pellen tesque eget, mauris lorem iupsum neque lacus.

You might be interested in

AArch64

AArch64 is a 64-bit instruction set architecture (ISA) developed by ARM Holdings specifically for its ARMv8-A processors.

C++

C++ is a general-purpose programming language that was developed in 1979 by Bjarne Stroustrup.

FreeBSD

FreeBSD is a free and open-source operating system based on the BSD (Berkeley Software Distribution) UNIX operating system.

GitHub

GitHub is a web-based platform used for version control and collaboration in software development projects.

Hydrology

Hydrology is the scientific study of the movement, distribution, and management of water on Earth and other planets, including the water cycle, water resources, and drainage basin sustainability.

IPv4

The Wikipedia page for IPv4 provides an overview of the Internet Protocol version 4 (IPv4), which is a widely used network layer protocol for sending and receiving data packets over the internet.

IPv6

IPv6 is the latest version of Internet Protocol (IP) that is designed to replace IPv4, which is running out of available addresses.

JavaScript

JavaScript is a programming language commonly used for creating interactive and dynamic websites.

Linux

Linux is a free and open-source operating system based on the Unix operating system.

Microsoft

Microsoft Corporation is an American multinational technology company founded by Bill Gates and Paul Allen in 1975.

OpenStreetMap

OpenStreetMap (OSM) is a collaborative mapping project that aims to create a free and editable map of the world.

SQL

SQL (Structured Query Language) is a standard programming language for managing and manipulating relational databases.