PostgreSQL Database Directory, Links. Programming, Administration, DBAs, Design, Support, Maintenance Reference, Resources @ eIT.in

Add Links: If you have a web site that you wish to include in this database, do let us know the details by sending a note about your URL to narsi@esource.in. We’ll quickly review the web site, and if found relevant, add it to the database. We look forward to web site owners and link exchange partners to submit URL. Thanks!

Looking for an outsourcing partner for database programming, applications development and database administration? Have you talked to us?

Other IT Web Sites from eIT.in

Content derived from Wikipedia article on PostgreSQL

PostgreSQL - From Wikipedia, the free encyclopedia

PostgreSQL

Developer: PostgreSQL Global Development Group

Latest release: 8.1.5 / October 16, 2006

OS: Cross-platform

Use: RDBMS

License: BSD

Website: www.postgresql.org

PostgreSQL is a free object-relational database server (database management system), released under a flexible BSD-style license. It offers an alternative to other database systems. Similar to other open-source projects such as Apache, Linux, and Mediawiki, PostgreSQL is not controlled by any single company, but relies on a global community of developers and companies to develop it.

PostgreSQL's unusual-looking name makes some readers pause when trying to pronounce it, especially those who pronounce SQL as "sequel". PostgreSQL's developers pronounce it "post-gress-Q-L". (Audio sample, 5.6k MP3). It is also common to hear it abbreviated as simply "postgres", which was its original name. The name refers to the project's origins as a "post-Ingres" database, the original authors having also developed Ingres.

Contents

1 Features

1.1 Functions

1.2 Indexes

1.3 Triggers

1.4 MVCC

1.5 Rules

1.6 Data types

1.7 User-defined objects

1.8 Inheritance

1.9 Other features

1.10 Add-ons

2 History

3 Prominent users

4 See also

5 References

6 External links

Features

Functions

Functions allow blocks of code to be executed by the server. Although these blocks can be written in SQL, the lack of basic programming operations, such as branching and looping, has driven the adoption of other languages inside of functions. Some of the languages can even execute inside of triggers. Functions in PostgreSQL can be written in the following languages:

A built-in language called PL/pgSQL resembles Oracle's procedural language PL/SQL

Scripting languages are supported through PL/Perl, plPHP, PL/Python, PL/Ruby, PL/sh, PL/Tcl and PL/Scheme

Compiled languages C, C++, or Java (via PL/Java)

The statistical language R through PL/R

Functions can be defined to execute with the privileges of either the caller or the user who defined the function. Functions are sometimes referred to as stored procedures, although there is a slight technical distinction between the two.

Indexes

User-defined indexes can be created, or the built-in B-tree, hash and GiST indices can be used. Indexes in PostgreSQL also support the following features:

PostgreSQL is capable of scanning indexes backwards when needed; you never need a separate index to support ORDER BY field DESC.

Expressional indexes can be created with an index of the result of an expression or function, instead of simply the value of a column.

Partial indexes, which only index part of a table, can be created by adding a WHERE clause to the end of the CREATE INDEX statement. This allows a smaller index to be created.

Bitmap index scans are supported as of version 8.1. This involves reading multiple indexes and generating a bitmap that expresses their intersection with the tuples that match the selection criteria. This provides a way of composing indexes together; on a table with 20 columns, there are, in principle, 20! indexes that could be defined - which is far too many to actually use. If you create one index on each column, bitmap scans can compose arbitrary combinations of those indexes at query time for each column that seems worth considering as a constraint.

Triggers

Triggers are fully supported and can be attached to tables but not to views. Views can have rules, though. Multiple triggers are fired in alphabetical order. In addition to calling functions written in the native PL/PgSQL, triggers can also invoke functions written in other languages like PL/Perl.

MVCC

PostgreSQL manages concurrency through a system known as Multi-Version Concurrency Control (MVCC), which gives each user a "snapshot" of the database, allowing changes to be made without being visible to other users until a transaction is committed. This largely eliminates the need for read locks, and ensures the database maintains the ACID principles in an efficient manner.

Rules

Rules allow the "query tree" of an incoming query to be rewritten. One common usage is to implement updatable views.

Data types

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

Arbitrary precision numerics

Unlimited length text

Geometric primitives

IP and IPv6 addresses

CIDR blocks, and MAC address data types

Arrays

In addition, users can create their own data types which can usually be made fully indexable via PostgreSQL's GiST infrastructure.

Examples of these are the Geographic information system (GIS) data types from the PostGIS project for PostgreSQL.

User-defined objects

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

Indices

Operators (and existing ones can be overloaded)

Aggregates

Domains

Casts

Conversions

Inheritance

Tables can be set to inherit their characteristics from a "parent" table. Data is shared between "parent" and "child(ren)" tables. Tuples inserted or deleted in the "child" table will respectively be inserted or deleted in the "parent" table. Also adding a column in the parent table will cause that column to appear in the child table as well. This feature is not fully supported yet -- in particular, table constraints are not currently inheritable. This means that attempting to insert the id of a row from a child table into table that has a foreign key constraint referencing a parent table will fail because postgres doesn't recognize that the id from the child table is also a valid id in the parent table.

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

Other features

Referential integrity constraints including foreign key constraints, column constraints, and row checks

Views

Full, inner, and outer (left and right) joins

Sub-selects

Transactions

A high level of compliance with the SQL:2003 standard

Encrypted connections via SSL

Binary and textual large-object storage

Online backup

Domains

Tablespaces

Savepoints

Point-in-time recovery

Two-phase commit

TOAST (The Oversized-Attribute Storage Technique) is used to transparently store large table attributes (such as big MIME attachments or XML messages) in a separate area, with automatic compression.

Regular expressions [1]

Add-ons

Geographic objects via PostGIS. GPL.

Full text search via Tsearch2 and OpenFTS. GPL.

Several asynchronous master/slave replication packages, including Slony-I (BSD license) and Mammoth Replicator (closed source, max 50 slaves, US $1,000 for one master and one slave).

XML/XSLT support via XPath Extensions in the contrib section. GPL.

History

PostgreSQL has had a lengthy evolution, starting with the Ingres project at UC Berkeley. The project leader, Michael Stonebraker, had left Berkeley to commercialize Ingres in 1982, but eventually returned to academia. After returning to Berkeley in 1985, Stonebraker started a post-Ingres project to address the problems with contemporary database systems that had become increasingly clear during the early 1980s. The code bases of Postgres and Ingres started (and remain) completely separated.

The resulting project, named Postgres, aimed to introduce the minimum number of features needed to add complete support for types. These features included the ability to define types, but also the ability to fully describe relationships – something used widely before this time 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.

Starting in 1986 the team released a number of papers describing the basis of the system, and by 1988 the project had a prototype version up and running. 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. 1991's version 3 re-wrote the rules system again, but also added support for multiple storage managers and for an improved query engine. By 1993 a huge number of users existed and began to overwhelm the project with requests for support and features. After releasing a Version 4 — primarily as a cleanup — the project ended.

Although the Postgres project had officially ended, the BSD license (under which Berkeley had released Postgres) enabled Open Source developers to obtain copies and to develop the system further. In 1994 two UC Berkeley graduate students, Andrew Yu and Jolly Chen, added a SQL language interpreter to replace the earlier Ingres-based QUEL system, creating Postgres95. The code was subsequently released to the web to find its own way in the world.

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

1996 saw a re-naming of the project: in order to reflect the database's new SQL query language, Postgres95 became PostgreSQL. The first PostgreSQL release formed version 6.0 in January 1997. Since then, a group of database developers and volunteers from around the world, coordinating via the Internet, have maintained the software.

Although the license allowed for the commercialization of Postgres, the Postgres code did not develop commercially with the same rapidity as Ingres — somewhat surprisingly considering the advantages Postgres offered. The main offshoot originated when Paula Hawthorn (an original Ingres team member who moved from Ingres) and Michael Stonebraker formed Illustra Information Technologies to commercialize Postgres.

In 2001, Command Prompt, Inc. released Mammoth PostgreSQL, the oldest surviving commercial PostgreSQL distribution. They actively support the PostgreSQL community through developer sponsorships and projects including PL/Perl, PL/php, and hosting of community projects such as the PostgreSQL Build Farm.

In January 2005, PostgreSQL received backing by another database vendor. Pervasive Software, well known for their Btrieve product which was nearly ubiquitous on the Novell NetWare platform, announced commercial support & community participation. Since then, EnterpriseDB has announced similar involvement, with a particular focus on adding functionality to allow applications written to work with Oracle to be more readily run atop PostgreSQL. Greenplum has been sponsoring efforts to provide enhancements directed at Data Warehouse and Business Intelligence applications, notably including the BizGres project.

In October 2005, John Loiacono, executive vice-president of software at Sun Microsystems, commented that "We're not going to OEM Microsoft but we are looking at PostgreSQL right now," although no specifics have yet been released.

In November 2005, Sun Microsystems announced support for PostgreSQL. As of June 2006, Sun Solaris 10 6/06 ships PostgreSQL.

In July 2006, Pervasive left the PostgreSQL support market.[2]

Prominent users

.org domain registry [3]

Sony Online (ComputerWorld Article) (March 20, 2006)

whitepages.com

Wisconsin Circuit Court Access with 6 * 180GB DBs replicated in real time

Skype (PostgreSQL Users)

See also

Free software Portal

PostgreSQL Management Tools

List of relational database management systems

Comparison of relational database management systems

References

Matthew, Neil, Stones, Richard. Beginning Databases with PostgreSQL, Second Edition. ISBN 1-59059-478-9.

Gilmore, W. Jason, Treat, Robert. Beginning PHP and PostgreSQL 8: From Novice to Professional. ISBN 1-59059-547-5.

Worsley, John C., Drake, Joshua D.. Practical PostgreSQL. ISBN 1-56592-846-6.

Douglas, Korry. PostgreSQL. ISBN 0-672-32756-2.

Topics in database management systems (DBMS) ( view • talk • edit )

Concepts

Database normalization | Referential integrity | Relational DBMS | Distributed DBMS | ACID

Objects

Topics in SQL

Comparison of syntax

Implementations of database management systems

Types of implementations

Products

Components

Query language | Query optimizer | Query plan | ODBC | JDBC

Lists

List of object-oriented database management systems

List of relational database management systems

List of truly relational database management systems

End of Wikipedia content, http://en.wikipedia.org/wiki/PostgreSQL

Web Resources for PostgreSQL

PostgreSQL

More eIT.in References

· Databases

o Ingres

o Sybase

o MiniSQL

o Unidata

o VSAM

o CA-IDMS

o Yard

o Paradox

o FoxPro Database

o Dataflux

o MyBase

o dBase

o LEAP

o MultiDB Express

Main Sections @ eIT.in

Software

· Free & Open Source Software

· Operating Systems

o Mainframe & Legacy Operating Systems

· Midrange

· Mainframe Operating Systems

· Databases

· Programming & Development Directory

o Programming Languages

§ The A-Z of Programming Languages

§ A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z

· Internet & Web

§ Web Servers

§ Application Servers

§ Server Side Scripting

§ Web Services

Computer Hardware
Networking & Communications Technologies
IT Strategy & Design
IT in Industries & Businesses
IT in Functions & Business Processes

IT Infrastructure
Tech Support
IT, Software Industry, Trade & Business Network
IT, Software Industry News & Updates

About eIT.in

eIT.in is a comprehensive directory for everything IT & Software. It contains over 500 categories, and well over 10,000 web resources

eIT.in provides directory and web links resources for the IT, software, programming & software development domains. It is intended to be useful for application, applications programmers & developers, software technology programmer & developer, databases software development, administrators & DBAs, application developers, strategy architect, design specialists and architects, migration, integration, customization consultants and customisation analysts, administration, maintenance & support professionals, outsourcing consultant, bespoke solutions programming developers & coders, project management & functional analyst, and for system administrators, testing & quality control engineers. It will make an effort to provide resources on tutorial/tutorials, guide, guides, tips, faq, faqs on these topics.

eIT.in content is available under GPL: All directory content at mainframe.in is under the General Public License (GPL). Under this license, anyone is free to copy & use any amount of directory content @ eIT.in, make changes to it and use it in any way they wish, as long as they also allow the same rights to anyone else for this content. The concept of GPL has been adapted from the GNU GPL of the Free Software Movement. To those who wish to use content from eIT.in, our only request is that they acknowledge the source and provide a link back to eIT.in. This is only a request!

Countries & Cities Where eIT.in Provides Assistance

eIT Cities: Bangalore, Chennai, Mumbai, Bhubaneswar, Mysore, Kolkaka, Delhi, Pune, Trivandrum, Hyderabad

You are the $$$ Section of eIT.in

Reference

GeoDig – Get Local!

Have you checked out the GeoDig directories for over 30 countries? GeoDig provides useful local and regional web resources for over 200 cities around the world. See the list of cities and countries for which GeoDig provides locality-specific web resources.

North America

USA - Alabama (AL) > Birmingham; Alaska; Arkansas (AR) > Little Rock; Arizona (AZ) > Phoenix, Las Vegas, Tucson; California (CA) > Los Angeles, San Francisco, Sacramento, Fresno, Bakersfield; Colorado, CO > Denver; Connecticut, CT > Hartford; District of Columbia, DC > Washington DC; Delaware (DE) > Wilmington; Florida > Miami, Orlando, Tampa, Orlando, Sarasota, West Palm Beach, Jacksonville; Georgia > Atlanta; Hawaii > Honolulu; Idaho; Illinois > Chicago; Indiana > Indianapolis; Iowa; Kansas (KS); Kentucky (KY) > Louisville; Louisiana (LA) > New Orleans, Baton Rouge; Maine; Maryland (MD) > Baltimore; Massachusetts > Boston, Springfield; Michigan > Detroit, Grand Rapids; Minnesota > Minneapolis-St. Paul; Mississippi (MS); Missouri (MO) > Kansas City, St. Louis; Montana; Nebraska (NE) > Omaha; Nevada (NV) > Las Vegas; New Hampshire; New Jersey (NJ) > Jersey City, Newark; New Mexico (NM) > Albuquerque; New York > New York, Buffalo, Rochester, Albany, Syracuse; North Carolina (NC) > Raleigh-Durham, Charlotte, Greensboro; North Dakota; Ohio> Columbus, Cincinnati, Cleveland, Toledo, Youngstown, Dayton; Oklahoma (OK) > Oklahoma City, Tulsa; Oregon > Portland; Pennsylvania > Philadelphia, Allentown, Pittsburgh, Harrisburg, Scranton, ; Rhode Island (RI) > Providence; South Carolina (SC) > Greenville; South Dakota; Tennessee (TN) > Knoxville, Memphis, Nashville; Texas > Austin, Dallas, Houston, San Antonio, El Paso, Austin, McAllen; Utah (UT) > Salt Lake City; Vermont; Virginia (VA) > Norfolk, Richmond; Washington > Seattle; West Virginia; Wisconsin (WI) > Milwaukee; Wyoming

Canada - Vancouver, Montreal, Toronto, Calgary, Ottawa-Gatineau, Edmonton, Quebec City, Winnipeg, Hamilton, London

You are the $$$ Section of eIT.in

Europe - UK - London, Glasgow, Manchester, Birmingham, Liverpool, Sheffield, Leeds, Bristol, Edinburgh, Leicester; France - Paris, Marseille, Lyon, Toulouse, Nice, Nantes, Strasbourg, Montpellier, Bordeaux; Germany - Frankfurt (Frankfurt am Main), Munich (München), Berlin, Düsseldorf, Hamburg, Cologne (Köln), Essen, Dortmund, Stuttgart, Bremen, Duisburg, Hannover, Nürnberg (Nuremberg), Dresden, Leipzig; Italy - Milan (Milano), Rome (Roma), Napoli (Naples), Torino (Turin), Palermo, Bologna, Firenze (Florence), Genova (Genoa); Spain - Madrid, Barcelona, Valencia, Sevilla, Zaragoza, Malaga, Murcia, Las Palmas, Bilbao; Scandinavia - Finland - Helsinki (Helsingin), Espoo, Tampere (Tampereen), Vantaa, Turku, Oulu, Sweden - Stockholm, Goteborg (Göteborg), Malmo (Malmö), Uppsala, Vasteras (Västerås), Denmark - Copenhagen (Københavns), Aarhus (Århus), Odense, Aalborg (Ålborg), Norway - Oslo, Bergen, Stavanger, Trondheim; Benelux - Belgium - Brussels (Brussel), Antwerp (Antwerpen), Ghent (Gent, Gand), Charleroi, Liège (Liege), Netherlands - Amsterdam, Rotterdam, Utrecht, Eindhoven, Tilburg, ‘s-Gravenhage (sGravenhage), Groningen, Luxembourg - Luxembourg City; Portugal – Lisbon; Greece – Athens; Hungary – Budapest; Poland – Warsaw; Switzerland - Zürich (Zurich), Geneva (Geneve, Genève), Basel, Bern (Berne), Lausanne; Austria - Linz, Vienna (Wien), Graz, Linz, Salzburg, Innsbruck; Ireland – Dublin

Asia - India - Mumbai, New Delhi, Bangalore; China & Hong Kong - Hong Kong, Beijing, Shanghai, Tianjin, Wuhan, Shenyang, Guangzhou, Harbin, Xian; Japan - Tokyo, Osaka, Yokohama, Nagoya, Sapporo, Kyoto, Kobe, Fukuoka, Kawasaki, Hiroshima; South Korea - Seoul, Pusa, Taegu, Incheon, Taejeon, Taiwan - Taipei; Malaysia - Kuala Lumpur; Singapore; Russia - Moscow, St Petersburg

You are the $$$ Section of eIT.in

Middle East - Turkey - Istanbul, Israel - Tel Aviv

Oceania - Australia - Sydney, Melbourne, Brisbane, Perth, Adelaide

Africa - South Africa - Johannesburg, Cape Town, Durban

eIT.in is a product of eSource India & Sourcing India

Other eSource & Sourcing sites: IT & Software (Dir, SAP), BPO, Chemicals, Textiles, Plant Oils, dotMobi, Billion Dollar Questions,

Biodiesel Encyclopedia, Linens, ideOS, Follars – Free, Open-source Dollars, Quali5.com – Own A Keyword Forever, AntiSE, Serkai, Leather & Hide, GeoDig