PostgreSQL wiki - User contributions [en]

Parallel Recovery

2022-05-09T07:29:59Z

Dfetter: Touched up a few spelling issues

[[File:MyPicture_github.jpg]]

My Wiki home: [[Koichi]]

email: koichi.dbms_at_gmail.com

Other topics: [[Distributed deadlock detection]]
== '''Parallel Recovery''' ==
 

=== PostgreSQL redo log (WAL) outline ===

In PostgreSQL, WAL (write-ahead log) is used for recovery and log-shipping replication. Outline is described in [https://www.postgresql.org/docs/current/wal-intro.html this documentation page]. The outline of WAL is:

* Every updating backend process must write its redo log to WAL before it really updates data files.
* Each WAL record (piece of updating data record) has to reach stable storage before the data is synch'ed to the storage.

WAL is used in recovery and log-shipping replication. In recovery, the WAL is used as follows:

* Each WAL record is read from WAL segments in the written order,
* Read WAL record is applied to corresponding data block. This is called "redo" or "replay".
* To maintain redo consistency, redo was done in single thread.

In the case of log-shipping replication, each WAL record is:

* Transferred to each replica in the written order and
* Replayed at replica in a single thread just as in recovery
* When replay reaches a consistent state, it allows postmaster to begin read transactions, while following WAL records reach and are replayed.
 

----

=== Issues around serialized replay ===

At present, WAL records are replayed strictly in written order in a single thread, while they are generated by multiple backend processes in parallel. The issues are:

* Recovery/replay performance is much worse than performance to write WALs. Recovery can take longer than the period WAL records were written.
* Replication lag can be long when the master has heavy updating workloads.
 

----

=== Can replay be done in parallel ? ===

If we apply several rules about recovery order, yes. The rules are:

* For a given data block, WAL records must be applied in the written order.
* For a given transaction, when we apply WAL record terminating the transaction (commit/abort/prepare for commit), all the associated WAL records must have been replayed,
* In the case of multi-block WAL, it should be applied only by one worker. For this purpose, such WAL record is assigned to all the block workers responsible for each block involved. When block worker picks up multi-block WAL and if it is not the last thread, it should wait until the last thread picking up this record actually replay it. If a thread is the last to pick up multi-block WAL record, it replays the record and send sync to other waiging workers.
* To replay specific WAL record such as updating timeline, it should wait until all the preceding WAL records are replayed This may not be necessary but it looks safer at present to have such condition for certain set of WAL records.
* Replayed LSN at pg_controldata will be updated when all the preceding WAL records are replayed.
 

----

=== Implementation Note ===
 
==== Worker configuration ====

* Because current recovery is done in startup process, parallel replay threads are implemented as its child process.
* Now we have following processes for this purpose:
** Startup process: read WAL record from WAL segment/walsender and perform overall control,
** Dispatching worker: analyze and dispatch WAL records,
** Error page registration: collects error pages from other worker. Current implementation is using hash functions based on memory context, which is not simple to port it to shared memory. We can replace this with simpler configuration if we can manage such information using shared memory.
** Transaction worker: replays WAL record which does not have any block information to update.
** Block worker: replays block information (mostly HEAP/HEAP2).

We can have more than one block workers. Other workers consists of single process each.
 
==== Shared information and locks ====

To pass and share information such as WAL record and status, shared memory defined in <code>storage/dsm.h</code> is used.

To protect these data, spin lock defined in <code>storage/spin.h</code> is used.

 
==== Synchronization among workers ====

For light-weight synchronization among workers, unix-domain udp socket is used. This can be replaced with <code>stoage/latch.h</code>.
 
==== New GUC ====

Following GUC parameters are added:

* <code>parallel_replay</code> (bool)
* <code>parallel_replay_test</code> (bool, just internal) enable additional code to work to attach workers with gdb for test.
* <code>num_preplay_workers</code> (int) number of total replay workers.
* <code>num_preplay_queue</code> (int) number of queues holding outstanding WAL records,
* <code>num_preplay_max_txn</code> (int) number of max outstanding transaction allowed in recovery. Max_connections or larger. In the case of replication slave, must be master's max_connections or larger.
* <code>preplay_buffers</code> (int)
 

----

=== Current code ===

Current code is available from [https://github.com/koichi-szk/postgres.git Koichi's GITHub repository]. Branch is <code>parallel_replay_14_2</code>.

 

----

=== Current code status ===

No test yet. The code just pass the build and under the review before testing. Now a couple of functions need improvement/development and some others are influenced by this change.

'''Any cooperation for discussion/test/development is very very welcome.''' You can contact to koichi.dbms_at_gmail.com.

Please understand that the repo can be incomplete due to occasional work.

Further addition is:

* To add a code to have WAL record in text format (like pg_waldump) and hold it to some portion of the memory to help the test. <code>xlog_outrec()</code> looks very useful for this purpose. At present, this is enabled with <code>WAL_DEBUG</code> flag.

Query Parsing

2021-03-19T07:47:43Z

Dfetter: /* TODO */

== Query Parsing ==

There are quite a few use cases where it'd be of great help if you could access the query tree Postgres uses internally for processing queries.

For example, when you need to do non-trivial operations on queries, like:

* Filtering out queries containing specific tables
* Reformatting & pretty-printing query strings
* Modifying or removing parts of the query string, e.g. rename a column

The [http://www.postgresql.org/docs/current/static/overview.html Postgres documentation] gives a good overview how query execution is handled and what the intermediate tree representations of a query string are.

=== Approaches ===

==== Using Postgres internals ====

Postgres already offers tooling to create a query tree from a given query string.

<code>raw_parser</code> takes a query statement as input and will return a parse tree. This parse tree can then be pretty-printed by using <code>nodeToString</code>.

An example can be seen [https://github.com/pganalyze/queryparser/blob/master/queryparser.c here], this can be easily implemented in a [http://www.postgresql.org/docs/current/static/extend-extensions.html Postgres extension] as well as seen [https://github.com/pganalyze/queryparser/blob/master/extension/annotate_query.c here].

<code>
SELECT * FROM foo where bar = 42 ORDER BY id DESC LIMIT 23;
(
{SELECT
:distinctClause <>
:intoClause <>
:targetList (
{RESTARGET
:name <>
:indirection <>
:val
{COLUMNREF
:fields (
{A_STAR
}
)
:location 7
}
:location 7
}
)
:fromClause (
{RANGEVAR
:schemaname <>
:relname foo
:inhOpt 2
:relpersistence p
:alias <>
:location 14
}
)
:whereClause
{AEXPR
:name ("=")
:lexpr
{COLUMNREF
:fields ("bar")
:location 24
}
:rexpr
{A_CONST
:val 42
:location 30
}
:location 28
}
:groupClause <>
:havingClause <>
:windowClause <>
:valuesLists <>
:sortClause (
{SORTBY
:node
{COLUMNREF
:fields ("id")
:location 42
}
:sortby_dir 2
:sortby_nulls 0
:useOp <>
:location -1
}
)
:limitOffset <>
:limitCount
{A_CONST
:val 23
:location 56
}
:lockingClause <>
:withClause <>
:op 0
:all false
:larg <>
:rarg <>
}
)
</code>

This approach isn't without caveats though, since the nodeToString code is used only for printing out planned query trees. These trees are rewritten to contain only contain nodes ultimately needed by the [http://www.postgresql.org/docs/current/static/executor.html Executor]. This means that all nodes not expected in later stages of query execution can't be printed, for example INSERT/UPDATE/DELETE nodes - since later on these are all aggregated in a <code>ModifyStmt</code> node.

==== pg_query ====

[https://github.com/pganalyze/pg_query pg_query] is a Ruby gem which can generate query trees in JSON representation. It accomplishes this by using a patched Postgres version which on one hand addresses the shortcomings outlined above, and on the other hand it provides a new function [https://github.com/pganalyze/postgres/blob/172e1dfc81705e9b14d81e8ef56c54b10ddfcd65/src/backend/nodes/outfuncs_json.c#L3502 <code>nodeToJSONString</code>] which turns a query tree into a JSON representation instead of the native Postgres format.

The Ruby bindings are just glue code around the Postgres code. More information can be found in this [https://pganalyze.com/blog/parse-postgresql-queries-in-ruby.html blog post]

<code>
#<PgQuery:0x000000009673a0
@query="SELECT * FROM foo where bar = 42 ORDER BY id DESC LIMIT 23;",
@parsetree=
[{"SELECT"=>
{"distinctClause"=>nil,
"intoClause"=>nil,
"targetList"=>
[{"RESTARGET"=>
{"name"=>nil,
"indirection"=>nil,
"val"=>{"COLUMNREF"=>{"fields"=>[{"A_STAR"=>{}}], "location"=>7}},
"location"=>7}}],
"fromClause"=>
[{"RANGEVAR"=>
{"schemaname"=>nil,
"relname"=>"foo",
"inhOpt"=>2,
"relpersistence"=>"p",
"alias"=>nil,
"location"=>14}}],
"whereClause"=>
{"AEXPR"=>
{"name"=>["="],
"lexpr"=>{"COLUMNREF"=>{"fields"=>["bar"], "location"=>24}},
"rexpr"=>{"A_CONST"=>{"val"=>42, "location"=>30}},
"location"=>28}},
"groupClause"=>nil,
"havingClause"=>nil,
"windowClause"=>nil,
"valuesLists"=>nil,
"sortClause"=>
[{"SORTBY"=>
{"node"=>{"COLUMNREF"=>{"fields"=>["id"], "location"=>42}},
"sortby_dir"=>2,
"sortby_nulls"=>0,
"useOp"=>nil,
"location"=>-1}}],
"limitOffset"=>nil,
"limitCount"=>{"A_CONST"=>{"val"=>23, "location"=>56}},
"lockingClause"=>nil,
"withClause"=>nil,
"op"=>0,
"all"=>false,
"larg"=>nil,
"rarg"=>nil}}],
@warnings=[]>
</code>

==== pgpool-II ====

pgpool-II is a middleware for Postgresql which in it's simplest use-case is an connection broker between client and database servers.

To be able to do advanced query routing it needs to understand the queries it gets sent form the query. To be able to do that, the pgpool project forked the parser and implemented their own node <code>outFuncs</code> to be able to recreated a query string from a given query tree.

If you want to create your own as correct as possible Postgres query pretty-printer this might be a good starting point.

==== sqlparse ====

[https://pypi.python.org/pypi/sqlparse sqlparse] is a Python module which implements a non-validating SQL parser suitable for parsing, splitting and formatting SQL statements. It provides the backbone for http://sqlformat.org/ - a SQL pretty printer.

Introspection into the queries is quite limited and since it's not specifically targeted at Postgres it's capabilities are quite limited when it comes to drilling down into query trees.

== TODO ==

To make life easier for people using query trees the following things need to be addressed in Postgres core:

* Implement outFuncs for all node types and not only those seen in a post-planning state.
* Ship alternate outFuncs suitable for generating e.g. JSON trees instead of the native Postgres tree format.

[[Category:Development]]

Speaker Bureau

2020-10-09T05:27:44Z

Dfetter:

In order to help with the challenge of finding speakers for meetups please add your name to this page if you are willing to speak at a meetup. Currently (2020) the meetups will be virtual. At a minimum add your name, topic(s) and timezone. Feel free to add anything else you feel is relevant.

I'd invite anyone who wants to mentor new speakers to add their name as mentor as well.

* Dave Cramer: Java and Postgresql, Logical Decoding, mentor
* Jonathan Katz: SCRAM, PostgreSQL + Kubernetes, PostgreSQL 13, Range Types + Applications, Building an App with a bunch of Postgres features (Logical decoding, CTEs, functions, range types, etc.), Data Types
* Stephen Frost: Security, PostgreSQL, other stuff
* Keith Fiske: Partitioning, Extensions, Administration, PG History & Features, Monitoring
* David Christensen: Replication, Bucardo, CTEs.
* David Fetter: PostgreSQL as a control plane, Fun with Foreign Data Wrappers, Hacking for Beginners

Logical Decoding Plugins

2020-04-18T20:28:15Z

Dfetter: /* JSON format plugins */

[https://www.postgresql.org/docs/current/static/logicaldecoding.html Logical decoding] provides the ability to stream modifications made via SQL to external consumers.

To be able to use logical decoding you need to install a plugin into postgresql to transform the WAL internal representation to a format the client can use.

=== JSON format plugins ===

==== wal2json ====

https://github.com/eulerto/wal2json

JSON output plugin for changeset extraction

"change": [
{
"kind": "insert",
"schema": "public",
"table": "table_with_pk",
"columnnames": ["a", "b", "c"],
"columntypes": ["int4", "varchar", "timestamp"],
"columnvalues": [1, "Backup and Restore", "2015-08-27 16:46:35.818038"]
}]

==== decoding-json ====

https://github.com/leptonix/decoding-json

This plugin receives the changes from WAL and decodes them to JSON.

{"type":"transaction.begin","xid":"2010561","committed":"2015-04-22 19:23:35.714443+00"}
{"type":"table","name":"abc","change":"INSERT","data":{"a":6,"b":7,"c":42}}
{"type":"table","name":"abc","change":"UPDATE","key":{"a":6,"b":7},"data":{"a":6,"b":7,"c":13}}

==== decoder_json ====

https://github.com/ildus/decoder_json

Uses libjansson for json generation rather than native postgresql code

==== jsoncdc ====

https://github.com/instructure/jsoncdc

Written in rust

==== wal2mongo ====

Translates changesets into a format consumable directly by MongoDB

https://github.com/HighgoSoftware/wal2mongo

=== Protobuf Format Plugins ===

==== decoderbufs ====

https://github.com/xstevens/decoderbufs

decoderbufs is a PostgreSQL logical decoder output plugin to deliver data as Protocol Buffers.

==== postgres-decoderbufs ====

https://github.com/debezium/postgres-decoderbufs

A fork of xstevens/decoderbufs for use as a [http://debezium.io/ debezium] connector

==== pg_pb3_ld ====

https://github.com/johto/pg_pb3_ld

work in progress

=== Avro Format Plugins ===

==== Bottled Water ====

https://github.com/confluentinc/bottledwater-pg

Streams into Kafka. No longer supported.

=== SQL Format Plugins ===

==== decoder_raw ====

https://github.com/michaelpq/pg_plugins/tree/master/decoder_raw

This output plugin for logical replication generates raw queries based
on the logical changes it finds. Those queries can be consumed as they
are by any remote source.

=== Miscellaneous Plugins ===

==== test_decoding ====

[https://www.postgresql.org/docs/current/static/test-decoding.html contrib/test_decoding] is example code for a logical decoding output plugin. It describes itself as "doesn't do anything especially useful, but can serve as a starting point for developing your own decoder".

People have written code to parse the output from this plugin, but that doesn't make it a good idea:

* https://github.com/davecramer/LogicalDecode - java
* https://github.com/lisael/pylogicaldecoding - python
* https://github.com/kibae/pg-logical-replication - node.js

==== osm-logical ====

https://github.com/zerebubuth/osm-logical

Toy code for use with openstreetmaps. Looks to be based on test_decoding.

==== pglogical ====

https://www.2ndquadrant.com/en/resources/pglogical/

pglogical is a logical replication system, implemented as a postgresql extension

==== transicator ====

https://github.com/apigee-labs/transicator

transicator reads from a single logical decoding connection and replicates change out to many (thousands) of intermittently connected clients via a REST API

Logical Decoding Plugins

2020-04-18T20:25:46Z

Dfetter: Changed to current URL

[https://www.postgresql.org/docs/current/static/logicaldecoding.html Logical decoding] provides the ability to stream modifications made via SQL to external consumers.

To be able to use logical decoding you need to install a plugin into postgresql to transform the WAL internal representation to a format the client can use.

=== JSON format plugins ===

==== wal2json ====

https://github.com/eulerto/wal2json

JSON output plugin for changeset extraction

"change": [
{
"kind": "insert",
"schema": "public",
"table": "table_with_pk",
"columnnames": ["a", "b", "c"],
"columntypes": ["int4", "varchar", "timestamp"],
"columnvalues": [1, "Backup and Restore", "2015-08-27 16:46:35.818038"]
}]

==== decoding-json ====

https://github.com/leptonix/decoding-json

This plugin receives the changes from WAL and decodes them to JSON.

{"type":"transaction.begin","xid":"2010561","committed":"2015-04-22 19:23:35.714443+00"}
{"type":"table","name":"abc","change":"INSERT","data":{"a":6,"b":7,"c":42}}
{"type":"table","name":"abc","change":"UPDATE","key":{"a":6,"b":7},"data":{"a":6,"b":7,"c":13}}

==== decoder_json ====

https://github.com/ildus/decoder_json

Uses libjansson for json generation rather than native postgresql code

==== jsoncdc ====

https://github.com/instructure/jsoncdc

Written in rust

=== Protobuf Format Plugins ===

==== decoderbufs ====

https://github.com/xstevens/decoderbufs

decoderbufs is a PostgreSQL logical decoder output plugin to deliver data as Protocol Buffers.

==== postgres-decoderbufs ====

https://github.com/debezium/postgres-decoderbufs

A fork of xstevens/decoderbufs for use as a [http://debezium.io/ debezium] connector

==== pg_pb3_ld ====

https://github.com/johto/pg_pb3_ld

work in progress

=== Avro Format Plugins ===

==== Bottled Water ====

https://github.com/confluentinc/bottledwater-pg

Streams into Kafka. No longer supported.

=== SQL Format Plugins ===

==== decoder_raw ====

https://github.com/michaelpq/pg_plugins/tree/master/decoder_raw

This output plugin for logical replication generates raw queries based
on the logical changes it finds. Those queries can be consumed as they
are by any remote source.

=== Miscellaneous Plugins ===

==== test_decoding ====

[https://www.postgresql.org/docs/current/static/test-decoding.html contrib/test_decoding] is example code for a logical decoding output plugin. It describes itself as "doesn't do anything especially useful, but can serve as a starting point for developing your own decoder".

People have written code to parse the output from this plugin, but that doesn't make it a good idea:

* https://github.com/davecramer/LogicalDecode - java
* https://github.com/lisael/pylogicaldecoding - python
* https://github.com/kibae/pg-logical-replication - node.js

==== osm-logical ====

https://github.com/zerebubuth/osm-logical

Toy code for use with openstreetmaps. Looks to be based on test_decoding.

==== pglogical ====

https://www.2ndquadrant.com/en/resources/pglogical/

pglogical is a logical replication system, implemented as a postgresql extension

==== transicator ====

https://github.com/apigee-labs/transicator

transicator reads from a single logical decoding connection and replicates change out to many (thousands) of intermittently connected clients via a REST API

PostgreSQL vs SQL Standard

2020-03-01T20:09:02Z

Dfetter: /* Major features simply not implemented yet */

This page attempts to document those instances where PostgreSQL deviates from standard SQL. It is not necessarily complete, and doesn't attempt to include all cases where an optional feature is not implemented or only partially implemented.

== Issues not yet classified ==

=== NOT NULL constraints on composite-type columns ===

The spec defines a <code>NOT NULL</code> column constraint as being equivalent to <code>CHECK(column IS NOT NULL)</code>, thus importing the semantics of composite-type null tests.

PostgreSQL treats <code>NOT NULL</code> as a simple "is not the null value" test, and therefore allows a row value with some null fields to be stored contrary to the spec.

=== COALESCE on row types ===

The spec defines <code>COALESCE(X,Y)</code> as a syntactic transformation to <code>CASE WHEN X IS NOT NULL THEN X ELSE Y END</code> (it leaves open the question of whether X is really evaluated twice by disallowing non-deterministic expressions or expressions with side effects in this context). A consequence of this is that the rather odd rules for null tests of row types are applied.

PostgreSQL applies only the "is not the null value" test to X. Accordingly, if X is a row value containing null columns, PostgreSQL will return X, while the spec would require returning Y.

 

== Fixable issues ==

These are cases where PG's behavior differs from the spec, but there appears to be no major obstacle to changing it to conform.

=== Wrong return type for extract() ===

The spec requires that <code>extract()</code> return an exact numeric type.

PostgreSQL returns an approximate numeric type (<code>double precision</code>).

There are obviously some backward compatibility concerns that would have to be considered before changing this one, but they don't look serious.

Note: date/time types support 'infinity' but numeric doesn't, so that would have to be resolved first.

=== Obsolete syntax for substring() ===

The spec has a form of substring() which is: <code>substring(<string> SIMILAR <pattern>[ ESCAPE <escape char>])</code>.

PostgreSQL does not support this form but does support the same functionality under the form <code>substring(<string> FROM <pattern> FOR <escape char>)</code>, which used to be correct back in 1999 when PostgreSQL implemented it.

Note that the escape character is required, otherwise the function uses regular expressions instead of <code>SIMILAR TO</code> pattern matching!

 

== Issues with some block to implementation ==

These are cases where PG's behavior differs from the spec, or where an otherwise desirable feature is missing, but there is some technical issue that would make it harder to implement.

=== LISTAGG() ===

<code>LISTAGG()</code> is the standard SQL equivalent of our <code>string_agg()</code>, but it uses the ordered-set aggregate syntax.

Implementing this in the most straightforward way would require erasing many of the existing distinctions between ordered-set aggregate syntax and conventional aggregate syntax. Currently we require that ordered-set aggs be called using <code>WITHIN GROUP</code>, while ordinary aggs must not use <code>WITHIN GROUP</code> but may have an embedded <code>ORDER BY</code> clause in their arguments (as per the standard <code>ARRAY_AGG()</code>).

<code>LISTAGG()</code> does not have the semantics of an ordered-set aggregate, so implementing it other than as a special case would mean allowing ordinary aggs to be called using <code>WITHIN GROUP</code> as an alternative to their normal syntax.

=== Data change delta tables ===

These are the standard's closest equivalent to our <code>RETURNING</code> and writable CTEs, but the visibility and trigger firing rules appear to be different to those of wCTEs, so one can't be implemented in terms of the other.

=== Identifier lengths ===

The spec requires that identifiers be allowed up to 18 characters even if the "long identifiers" feature is not declared; if it is, then the limit is 128 characters. Note that this limit is in characters and not bytes.

PostgreSQL limits the significant length of an identifier to 63 '''bytes''' unless specified otherwise at compile time; this isn't enough for 18 unicode characters.

Currently we use the fixed-length <code>name</code> type for names; making it larger would significantly inflate the sizes of many system catalogs, while making it variable length would be a compatibility issue (e.g. changing the order of columns in many system catalogs to put the name field after the fixed-length fields).

=== DISTINCT aggregates as window functions ===

PostgreSQL does not allow <code>DISTINCT</code> in aggregates when they are invoked as window functions.

The existing implementation of <code>DISTINCT</code> would be quite hard to adapt to window functions.

=== Deferrable CHECK and NOT NULL ===

The spec defines <code>NOT NULL</code> in terms of <code>CHECK</code>, and allows <code>CHECK</code> constraints to be deferrable.

PostgreSQL currently does all these checks before actually inserting the new or modified row.

=== FULL OUTER JOIN conditions ===

The spec allows any join condition for a <code>FULL OUTER JOIN</code>.

PostgreSQL currently limits such conditions to ones that are implementable without constructing explicit <code>UNION</code> operations; that is, the condition must be hashable, mergeable, or constant.

Adding support for arbitrary full joins (which would likely require constructing a <code>UNION</code> of the inner join and the two anti-joins) seems like a lot of work for minimal gain.

 
== Issues with some block at design level ==

These are cases where PG's behavior differs from the spec, or where an otherwise desirable feature is missing, but there is some technical issue that makes it hard to even decide how to implement it.

=== ANY() and SOME() aggregates ===

PostgreSQL supports <code>every()</code> from the standard, and provides <code>bool_or</code> as a nonstandard spelling of the <code>ANY</code>/<code>SOME</code> aggregate function, but two syntax conflicts make it impossible to parse the standard's <code>ANY</code> syntax:

# PostgreSQL allows <code>= ANY (array_expression)</code> as a form of quantified comparison predicate (this is an extension to the spec)
# PostgreSQL allows subselects in all contexts to have additional parentheses, which the spec does not allow

The spec's syntax for <code>ANY(expression)</code> as an aggregate function can be parsed unambiguously only because the spec's version of <code>ANY</code> as a quantified comparison predicate must have the keyword <code>SELECT</code> immediately following the <code>ANY(</code>.

=== Unreserved keywords as select-list aliases without AS ===

The spec requires that <code>SELECT 1 ZONE</code> be equivalent to <code>SELECT 1 AS ZONE</code>. PostgreSQL accepts only the latter form or alternatively requires the identifier to be quoted.

The main syntax ambiguity here is caused by the presence of postfix operators in PostgreSQL syntax; <code>SELECT 1 ! ZONE</code> would be ambiguous between treating the operator as postfix or infix (we take it as being infix in this case by using precedence rules). Additional ambiguities exist with compound type names using <code>NATIONAL</code>, <code>VARYING</code>, or <code>WITHOUT</code> (which would likely have to be made reserved words, as they are in the spec). <code>WITHIN</code>, <code>FILTER</code>, and <code>OVER</code>, and the datetime component names, which are not currently reserved in PostgreSQL, would also need to become reserved words. Since adding so many more reserved words is likely to break existing queries, this isn't considered a particularly viable solution.

=== DROP DOMAIN … CASCADE ===

The spec says that <code>DROP DOMAIN … CASCADE</code> does not drop any columns, but simply changes any columns of the domain type to instead use the base type with the addition of the domain's defaults and constraints.

PostgreSQL drops columns of the domain type.

The issue here is that we can reach a <code>DROP DOMAIN</code> by cascading from a drop of another object, such as a schema containing the domain or a function referenced in the domain's default or constraints. Supporting the standard behavior would therefore mean altering objects in ways that add new dependencies from within the code that traverses the existing dependencies, which seems problematic.

=== Temporary tables ===

In the spec, temporary tables are persistent schema objects whose ''data'' (and only the data) is temporary and per-session. Implementing these in PostgreSQL would actually have substantial advantages (catalog bloat when using temp tables heavily is a common problem); but PostgreSQL's existing behavior is very well-entrenched and changing it would cause compatibility issues.

(One approach sometimes suggested would be to use the spec's method if <code>GLOBAL</code> was specified when creating the table.)

=== Mandatory parens in VALUES ===

The spec allows <code>VALUES 1,2,3</code> (as an explicit table with 1 column, 3 rows).

PostgreSQL requires parens on each row: <code>VALUES (1),(2),(3)</code>.

It looks like the only obstacle here is that <code>VALUES</code> would need to become a reserved word.

 
== Issues where we explicitly choose to disregard the spec (WONTFIX) ==

=== Identifier case ===

PostgreSQL folds unquoted identifiers to lowercase, not the uppercase that the spec requires.

=== Constraint name scope ===

PostgreSQL treats the scope of a table or column constraint name as being the table it belongs to. The spec requires that such names be unique over the whole schema.

PostgreSQL's behavior here severely limits the usefulness of several <code>information_schema</code> views, which are defined on the assumption of schema-wide constraint name uniqueness.

=== TIMESTAMP WITH TIME ZONE ===

PostgreSQL's timestamp with time zone type is very different from the standard one.

# <code>timestamp '2018-06-01 00:00:00+1200'</code> is a timestamp without timezone, spec says it should be with timezone. PostgreSQL does not allow the type of a literal to depend on its string value.
# <code>timestamp with time zone</code> does not store a timezone offset, but is interpreted with the session timezone. The spec's timezone handling is less than useless, PostgreSQL's is actually useful.

=== AT TIME ZONE ===

Our <code>AT TIME ZONE</code> operator is somewhat different to the spec's.

The spec says:

# <code>t AT TIME ZONE z</code> where <code>t</code> is of type <code>time[stamp] without time zone</code> returns a result of the corresponding <code>with time zone</code> type.
# <code>t AT TIME ZONE z</code> where <code>t</code> is of type <code>time[stamp] with time zone</code>, the result is of the same type.

What PostgreSQL does is:

# <code>t AT TIME ZONE z</code> where <code>t</code> is of type <code>timestamp without time zone</code> returns a result of type <code>timestamp with time zone</code>.
# <code>t AT TIME ZONE z</code> where <code>t</code> is of type <code>timestamp with time zone</code> returns a result of type <code>timestamp without time zone</code>.
# <code>t AT TIME ZONE z</code> where <code>t</code> is of type <code>time with time zone</code> returns a result of type <code>time with time zone</code>.
# <code>t AT TIME ZONE z</code> where <code>t</code> is of type <code>time without time zone</code> casts the value of <code>t</code> to type <code>time with time zone</code> and then proceeds as the previous option.

This permits various transforms which are simply not possible in the spec's crippled timezone support, such as converting a wallclock time from one location to another via two applications of <code>AT TIME ZONE</code>.

=== INTERVAL ===

The standard interval type assumes that all days are the same length, and therefore intervals can be divided into "year-month" and "day-second" values; only one of which can be present in any single interval value or column.

PostgreSQL's interval type has three fields: months,days,[micro]seconds and allows all three to be present simultaneously.

Rationale: the spec's lack of usable timezone support makes its interval type useless too.

=== Transaction management ===

The spec's model of the relationship between the database and its clients differs from PostgreSQL's (and most other databases for that matter). This leaves the spec's requirements concerning how transactions begin and end as somewhat inconsistent, with some statements being defined as implicitly starting transactions and others not (and some may or may not implicitly start transactions depending on variable content).

PostgreSQL treats all client requests (which may contain multiple statements) as being wrapped in a transaction (auto-committing at the end of the request) except where <code>BEGIN</code> or <code>START TRANSACTION</code> is used explicitly.

=== Default transaction isolation level ===

The spec declares <code>SERIALIZABLE</code> to be the default isolation level, but PostgreSQL defaults to <code>READ COMMITTED</code>.

=== Default transaction access mode ===

The spec says that if the <code>READ UNCOMMITTED</code> isolation level is specified, but no access mode is specified, then the default access mode is <code>READ ONLY</code>. PostgreSQL uses the <code>default_transaction_read_only</code> setting instead.

=== Object ownership scope ===

The standard controls ownership of objects only at the schema level; objects inside a schema belong to the schema's owner.

PostgreSQL tracks ownership at individual object level.

Rationale: this PG behavior dates back to before it had schemas, and is much more flexible than the standard's approach.

=== Trigger firing order ===

The standard says that trigger firing order on a table depends on creation order of the triggers.

PostgreSQL fires triggers in order of name.

Rationale: documentation says "this was judged to be more convenient".

=== Trigger firing relative to referential constraint actions ===

The spec requires that when a referential action (e.g. <code>CASCADE</code> or <code>SET NULL</code>) causes a <code>BEFORE</code> trigger to be fired, the referential action is actually performed before firing the trigger.

One possible motivation for this is to ensure that the trigger function doesn't see the inconsistent intermediate state of the database in which the FK is violated.

Nevertheless, PostgreSQL always runs the <code>BEFORE</code> trigger before doing the operation.

In addition, the spec requires that referential constraints are enforced before <code>AFTER</code> triggers. PostgreSQL instead enforces them via triggers with names of the form <code>"RI_ConstraintTrigger_…"</code> which are executed in name order with respect to other triggers (see [[#Trigger_firing_order|this item]]).

=== LIKE with no escape clause ===

The standard says that <code>LIKE</code> has no escape character if the <code>ESCAPE</code> clause was not specified.

PostgreSQL treats a missing <code>ESCAPE</code> clause as if it were <code>ESCAPE '\'</code>.

Rationale: historical.

=== Declared type of string literals ===

The standard says that the type of a string literal is fixed-length character string, i.e. <code>character(n)</code> where <code>n</code> is the length of the literal.

PostgreSQL treats untyped literals as being of unknown type and deduces the type from context (even in contexts where the spec does not provide for contextual typing). If no type is deduced, the value is treated either as <code>text</code> or <code>unknown</code> type depending on context and PostgreSQL version.

=== Trailing spaces in character(n) ===

Trailing spaces in char(n) values are removed in contexts where the spec requires they be kept.

An example is that <code>LIKE</code> will remove trailing spaces from a <code>character(n)</code> pattern parameter (but not from the first parameter).

Rationale: PG actually converts char(n) to text in most contexts and all the relevant functions and operators take text args, rather than having separate versions for char(n).

=== FETCH FIRST 0 ROWS ===

The spec requires an error to be generated for specifying a limit of 0. We generate errors only for values strictly less than 0.

=== Early enforcement of non-deferrable UNIQUE ===

The spec says that <code>UNIQUE</code> (and <code>PRIMARY KEY</code>) constraints are enforced at statement end and not row-by-row when in immediate mode, with no distinction between non-deferrable constraints and deferrable constraints currently set to immediate mode.

PostgreSQL enforces non-deferrable constraints row-by-row, and deferrable constraints in immediate mode at statement end. This is a compromise between wanting to preserve the hard semantic guarantees of uniqueness in row-by-row mode (relied on by the planner in order to prove result uniqueness), while allowing conflicting updates (e.g. <code>UPDATE … SET uniq = uniq + 1</code> where really necessary.

=== Lexing of string literals and comments ===

PostgreSQL rejects all of these:


<code><pre>
select 'foo'
/**/ 'bar' from ...

select 'foo' /**/ 'bar' from ...

select U&'foo' UESCAPE /**/ 'x' from ...

select 'foo' as U&"foo" UESCAPE /**/ 'x' from ...

select U&'foo' /**/ UESCAPE 'x' from ...

select 'foo' as U&"foo" /**/ UESCAPE 'x' from ...
</pre></code>

The first of those is certainly legal in the spec; the remainder are more debatable since the spec is rather unclear.

Regarding the second case:

<blockquote>
<code>5.3 <literal></code> 
Syntax Rules 
7) In a <code><character string literal></code>, <code><national character string literal></code>, <code><Unicode character string literal></code>, or <code><binary string literal></code>, a <code><separator></code> shall contain a <code><newline></code>.
</blockquote>

But SQL2016 also says:

<blockquote>
<code>5.2 <token> and <separator></code> 
Syntax Rules 
11) SQL text containing one or more instances of <code><comment></code> is equivalent to the same SQL text with the <code><comment></code> replaced with <code><newline></code>.
</blockquote>

which implies that the input should have been accepted.

Regarding the remaining cases:

<blockquote>
<code>5.2 <token> and <separator></code> 
<code><separator> ::= { <comment> | <white space> }...</code> 
Syntax Rules 
7) Any <code><token></code> may be followed by a <code><separator></code>.
</blockquote>

<blockquote>
<code>5.3 <literal></code> 
Syntax Rules 
11) In a <code><Unicode character string literal></code>, there shall be no
<code><separator></code> between the "U" and the <code><ampersand></code> nor between the
<code><ampersand></code> and the <code><quote></code>.
</blockquote>

which seems to imply that <code><separator></code> around the <code>UESCAPE</code> would be permitted; indeed, no other rule permits any kind of whitespace there.

There's no present desire to fix this because of the added complexity in the lexer. It is possible that this could be revisited if the lexer is redesigned in future.

 

== Issues where PostgreSQL actually conforms to the spec ==

These issues have been claimed or discussed as violations, but where PostgreSQL currently conforms to the spec as written. These are for reference in case they come up again; also, cases where PostgreSQL formerly violated the spec can be noted here as fixed.

=== null return from every(x) ===

In the query <code>SELECT every(x) FROM t;</code> the result will be <code>NULL</code> if <code>t</code> has no rows or all values of <code>t.x</code> are <code>NULL</code>. This is correct as per the spec, even though it's inconsistent with conventional mathematical usage (in which an AND of no terms should return true).

 
== Major features simply not implemented yet ==

* MATCH PARTIAL
* references in typed tables
* fetch first … with ties
* fetch first … percent
* more functional dependencies
* row pattern recognition
* partition join
* distinct types
* temporal tables
* generated columns (partially implemented)
* respect/ignore nulls for window functions
* "from last" for nth_value
* CAST(val AS type FORMAT 'template')
* Mutually recursive common table expressions
* many more

PL Matrix

2020-03-01T20:03:41Z

Dfetter:

This page is an attempt to document all the available Procedural Language Handlers for PostgreSQL.
''WARNING:'' The information presented here is still very much experimental and guaranteed to be out-of-date ...

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-layout: fixed;"
|- style="background: #ececec"
! style="width:16em" | Language
! Status
! Availability
! Named Parameters?
! OUT Parameters?
! (Un)Trusted
! Notes

|-
! style="text-align:block;" bgcolor="#ececec" | pl/pgsql
| bgcolor="#ddffdd" | Production
| bgcolor="#ddffdd" | in core
| bgcolor="#ddffdd" | yes
| bgcolor="#ddffdd" | yes
| bgcolor="#ddffdd" | Trusted
| bgcolor="#ddffdd" | compiled by default
|-
! style="text-align:block;" bgcolor="#ececec" | sql
| bgcolor="#ddffdd" | Production
| bgcolor="#ddffdd" | in core
| bgcolor="#ffffaa" | yes (version 9.2+)
| bgcolor="#ddffdd" | yes
| bgcolor="#ddffdd" | Trusted
| bgcolor="#ddffdd" | available by default
|-
! style="text-align:block;" bgcolor="#ececec" | pl/perl
| bgcolor="#ddffdd" | Production
| bgcolor="#ddffdd" | in core
| bgcolor="#ffdddd" | no
| bgcolor="#ffdddd" | no
| bgcolor="#ddffdd" | Trusted and Untrusted
| bgcolor="#ddffdd" |
|-
! style="text-align:block;" bgcolor="#ececec" | pl/python
| bgcolor="#ddffdd" | Production
| bgcolor="#ddffdd" | in core
| bgcolor="#ddffdd" | yes
| bgcolor="#ddffdd" | support for one OUT parameter from 8.4, multiple from 9.1
| bgcolor="#ddffdd" | Untrusted
| bgcolor="#ddffdd" |
|-
! style="text-align:block;" bgcolor="#ececec" | pl/tcl
| bgcolor="#ddffdd" | Production
| bgcolor="#ddffdd" | in core
| bgcolor="#ffdddd" | no
| bgcolor="#ffdddd" | no
| bgcolor="#ddffdd" | Trusted and Untrusted
| bgcolor="#ddffdd" |
|-
! style="text-align:block;" bgcolor="#ececec" | PL/sh
| bgcolor="#ddffdd" | Production

| bgcolor="#ddffdd" | [https://github.com/petere/plsh PL/sh]
| bgcolor="#ffffaa" | no (not useful)
| bgcolor="#ffdddd" | no
| bgcolor="#ddffdd" | Untrusted necessarily
| bgcolor="#ddffdd" |
|-
! style="text-align:block;" bgcolor="#ececec" | PL/R
| bgcolor="#ddffdd" | Production
| bgcolor="#ddffdd" | [https://joeconway.com/plr PL/R]
| bgcolor="#ddffdd" | yes
| bgcolor="#ffdddd" | no
| bgcolor="#ddffdd" | Untrusted
| bgcolor="#ddffdd" |
|-
! style="text-align:block;" bgcolor="#ececec" | pl/java
| bgcolor="#ddffdd" | Production
| bgcolor="#ddffdd" | [https://tada.github.io/pljava/ pl/java]
| bgcolor="#ddffdd" | yes
| bgcolor="#ddffdd" | yes
| bgcolor="#ffffaa" | ?
| bgcolor="#ddffdd" |
|-
! style="text-align:block;" bgcolor="#ececec" | pl/lolcode
| bgcolor="#ffffaa" | Alpha
| bgcolor="#ddffdd" | [http://pgfoundry.org/projects/pllolcode/ pl/lolcode]
| bgcolor="#ffffaa" | yes
| bgcolor="#ffffaa" | ?
| bgcolor="#ffffaa" | ?
| bgcolor="#ddffdd" |
|-
! style="text-align:block;" bgcolor="#ececec" | pl/scheme
| bgcolor="#ffffaa" | ?
| bgcolor="#ddffdd" | [https://github.com/vy/plscheme pl/scheme]
| bgcolor="#ddffdd" | yes
| bgcolor="#ddffdd" | yes
| bgcolor="#ddffdd" | Trusted and Untrusted
| bgcolor="#ddffdd" |
|-
! style="text-align:block;" bgcolor="#ececec" | pl/php
| bgcolor="#ffffaa" | Beta
| bgcolor="#ddffdd" | [https://public.commandprompt.com/documents/5 pl/php]
| bgcolor="#ffffaa" | Yes
| bgcolor="#ffffaa" | ?
| bgcolor="#ffffaa" | ?
| bgcolor="#ddffdd" |
|-
! style="text-align:block;" bgcolor="#ececec" | pl/ruby
| bgcolor="#ffffaa" | ?

| bgcolor="#ddffdd" | [http://rubyforge.org/projects/plruby/ pl/ruby]
| bgcolor="#ffffaa" | ?
| bgcolor="#ffffaa" | ?
| bgcolor="#ffffaa" | ?
| bgcolor="#ddffdd" |
|-
! style="text-align:block;" bgcolor="#ececec" | pl/lua (ng)
| bgcolor="#ddffdd" | Production
| bgcolor="#ddffdd" | [https://github.com/pllua/pllua-ng/ pl/lua (ng)]
| bgcolor="#ddffdd" | yes
| bgcolor="#ddffdd" | yes
| bgcolor="#ddffdd" | Trusted and Untrusted
| bgcolor="#ddffdd" | install with CREATE EXTENSION
|-
! style="text-align:block;" bgcolor="#ececec" | pl/pgpsm
| bgcolor="#ddffdd" | Beta
| bgcolor="#ddffdd" | [http://www.pgsql.cz/index.php/SQL/PSM pl/pgpsm]
| bgcolor="#ddffdd" | yes
| bgcolor="#ddffdd" | yes
| bgcolor="#ffffaa" | ?
| bgcolor="#ddffdd" | SQL/PSM implementation based on pl/pgsql runtime
|-
! style="text-align:block;" bgcolor="#ececec" | pl/v8
| bgcolor="#ddffdd" | Production
| bgcolor="#ddffdd" | [https://github.com/plv8/plv8 pl/v8js]
| bgcolor="#ddffdd" | yes
| bgcolor="#ddffdd" | yes
| bgcolor="#ddffdd" | Trusted
| bgcolor="#ddffdd" | install with CREATE EXTENSION
|-
! style="text-align:block;" bgcolor="#ececec" | PL/XSLT
| bgcolor="#ffffaa" | Alpha
| bgcolor="#ddffdd" | [https://github.com/petere/plxslt pl/xslt]
| bgcolor="#ddffdd" | yes
| bgcolor="#ffdddd" | no
| bgcolor="#ddffdd" | Untrusted
| bgcolor="#ddffdd" | install with CREATE EXTENSION
|-
! style="text-align:block;" bgcolor="#ececec" | PL/Julia
| bgcolor="#ffffaa" | ?
| bgcolor="#ddffdd" | [https://github.com/pljulia/pljulia pl/julia]
| bgcolor="#ddffdd" | ?
| bgcolor="#ffdddd" | ?
| bgcolor="#ddffdd" | Untrusted
| bgcolor="#ddffdd" | install with CREATE EXTENSION
|-
|}

Note: For all languages, it is allowed to place parameter names in the function parameter list declaration. What the '''Named Parameters''' column is about is whether the body of the function can refer to the parameters by those names, or whether it has to use some other notation, such as ''$1'', ''$2'', etc.

Note: All languages support parameters that are explicitly marked as IN parameters. Those that support OUT parameters also automatically handle INOUT parameters.

[[Category:Languages]]

Todo

2020-01-30T19:10:48Z

Dfetter:

<div style="margin: 1ex 1em; float: right;">
__TOC__
</div>

This list contains some known PostgreSQL bugs, some feature requests, and some things we are not even sure we want. Many of these items are hard, and some are perhaps impossible. If you would like to work on an item, please read the [[Developer FAQ]] first. There is also a [[Development_information|development information page]].

* {{TodoPending}} - marks ordinary, incomplete items
* {{TodoEasy}} - marks items that are easier to implement
* {{TodoDone}} - marks changes that are done, and will appear in the PostgreSQL 13 release.

For help on editing this list, please see [[Talk:Todo]]. Please do not add items here without discussion on the [[Mailing_Lists|mailing list]].

== Development Process ==

WARNING for Developers: Unfortunately this list does not contain all the information necessary for someone to start coding a feature. Some of these items might have become unnecessary since they were added --- others might be desirable but the implementation might be unclear. When selecting items listed below, be prepared to first discuss the value of the feature. '''Do not assume that you can select one, code it and then expect it to be committed.''' Always discuss design on Hackers list before starting to code. The flow should be:

Desirability -> Design -> Implement -> Test -> Review -> Commit

== Administration ==

{{TodoItem
|Check for unreferenced table files created by transactions that were in-progress when the server terminated abruptly
* [http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php <nowiki>Removing unreferenced files</nowiki>]
}}

{{TodoItem
|Allow log_min_messages to be specified on a per-module basis
|This would allow administrators to see more detailed information from specific sections of the backend, e.g. checkpoints, autovacuum, etc. Another idea is to allow separate configuration files for each module, or allow arbitrary SET commands to be passed to them. See also [[Logging Brainstorm]].}}

{{TodoItem
|Allow custom variables to appear in pg_settings()
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg00850.php <nowiki>Re: count(*) performance improvement ideas</nowiki>]
}}

{{TodoItem
|Have custom variables be transaction-safe
* {{MessageLink|4B577E9F.8000505@dunslane.net|Custom GUCs still a bit broken}}
* {{MessageLink|alpine.DEB.2.20.1701081007440.10378@lancre|proposal: session server side variables}}
}}

{{TodoItem
|Implement the SQL-standard mechanism whereby REVOKE ROLE revokes only the privilege granted by the invoking role, and not those granted by other roles
* [http://archives.postgresql.org/pgsql-bugs/2007-05/msg00010.php <nowiki>Re: Grantor name gets lost when grantor role dropped</nowiki>]
}}

{{TodoItem
|Prevent query cancel packets from being replayed by an attacker, especially when using SSL
* [http://archives.postgresql.org/pgsql-hackers/2008-08/msg00345.php <nowiki>Replay attack of query cancel</nowiki>]
}}

{{TodoItem
|Consider supporting incremental base backups
* http://www.postgresql.org/message-id/543D5AA7.9@2ndquadrant.it
}}

=== Configuration files ===
{{TodoSubsection}}

{{TodoItem
|Consider normalizing fractions in postgresql.conf, perhaps using '%'
* [http://archives.postgresql.org/pgsql-hackers/2007-06/msg00550.php <nowiki>Fractions in GUC variables</nowiki>]
}}

{{TodoItem
|Add external tool to auto-tune some postgresql.conf parameters
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg00000.php <nowiki>Re: Overhauling GUCS</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-11/msg00033.php <nowiki>Simple postgresql.conf wizard</nowiki>]
}}

{{TodoItem
|Allow pg_hba.conf to process include files
* [http://www.postgresql.org/message-id/86fvnm5t44.fsf@jerry.enova.com HBA files w/include support]
}}

{{TodoItem
|Create utility to compute accurate random_page_cost value
* http://archives.postgresql.org/pgsql-performance/2011-04/msg00162.php
* http://archives.postgresql.org/pgsql-performance/2011-04/msg00362.php
}}

{{TodoItem
|Allow synchronous_standby_names to be disabled after communication failure with all synchronous standby servers exceeds some timeout
|This also requires successful execution of a synchronous notification command.
* http://archives.postgresql.org/pgsql-hackers/2012-07/msg00409.php
* [http://www.postgresql.org/message-id/BF2827DCCE55594C8D7A8F7FFD3AB7713DD9A622@SZXEML508-MBX.china.huawei.com Standalone synchronous master]
* http://archives.postgresql.org/pgsql-hackers/2011-12/msg01224.php
}}

{{TodoItem
|Fix log_line_prefix to display the transaction id (%x) for statements not in a transaction block
* Currently it displays zero.
}}

{{TodoItem
|Adjust rounding behavior for numeric GUC values
* http://www.postgresql.org/message-id/53BE3815.4010203@po.ntts.co.jp
}}

{{TodoEndSubsection}}

=== Tablespaces ===
{{TodoSubsection}}

{{TodoItem
|Allow a database in tablespace t1 with tables created in tablespace t2 to be used as a template for a new database created with default tablespace t2
|Currently all objects in the default database tablespace must have default tablespace specifications. This is because new databases are created by copying directories. If you mix default tablespace tables and tablespace-specified tables in the same directory, creating a new database from such a mixed directory would create a new database with tables that had incorrect explicit tablespaces. To fix this would require modifying pg_class in the newly copied database, which we don't currently do.}}

{{TodoItem
|Allow reporting of which objects are in which tablespaces
|This item is difficult because a tablespace can contain objects from multiple databases. There is a server-side function that returns the databases which use a specific tablespace, so this requires a tool that will call that function and connect to each database to find the objects in each database for that tablespace.}}

{{TodoItem
|Allow WAL replay of CREATE TABLESPACE to work when the directory structure on the recovery computer is different from the original
* [https://www.postgresql.org/message-id/20180214042443.GB1993%40paquier.xyz Remarks about the difficulty of the item]
}}

{{TodoItem
|Allow per-tablespace quotas}}

{{TodoItem
|Allow tablespaces on RAM-based partitions for unlogged tables
* http://archives.postgresql.org/pgsql-advocacy/2011-05/msg00033.php
}}

{{TodoItem
|Allow tablespaces on RAM-based partitions for temporary objects
* [https://www.postgresql.org/message-id/20170529185308.GB28209@momjian.us Use of non-restart-safe storage by temp_tablespaces]
}}

{{TodoItem
|Allow toast tables to be moved to a different tablespace
* [http://archives.postgresql.org/pgsql-hackers/2011-05/msg00980.php moving toast table to its own tablespace]
* {{messageLink|CAFEQCbH756DyyAPQ1ykh3+b+kE1-EhWRww1WO_x5v38C-uLnUg@mail.gmail.com|patch : Allow toast tables to be moved to a different tablespace}}
}}

{{TodoItem
|Close race in DROP TABLESPACE on Windows
* http://www.postgresql.org/message-id/20141108050423.GA642055@tornado.leadboat.com
}}

{{TodoEndSubsection}}

=== Statistics Collector ===
{{TodoSubsection}}

{{TodoItem
|Testing pgstat via pg_regress is tricky and inefficient. Consider making a dedicated pgstat test-suite.
* [http://www.postgresql.org/message-id/20141216142937.GX1768@alvh.no-ip.org <nowiki>Re: REVIEW: Track TRUNCATE via pgstat</nowiki>]
}}
{{TodoItem
|Track number of WAL files ready to be archived in pg_stat_archiver
* [http://www.postgresql.org/message-id/CAB7nPqSCrcZGGy_SmpT7ubSzVGNMtphYU1JJZYyapHuN46E-Tw@mail.gmail.com <nowiki>pg_stat_archiver missing feature</nowiki>]
* [http://www.postgresql.org/message-id/53F5AB0A.5060502@dalibo.com Track number of files ready to be archived in pg_stat_archiver]
}}

{{TodoEndSubsection}}

=== SSL ===
{{TodoSubsection}}

{{TodoItem
| Allow automatic selection of SSL client certificates from a certificate store
* [http://archives.postgresql.org/pgsql-hackers/2009-05/msg00406.php <nowiki>Allow multiple certificates or keys in the postgresql.crt/.key files</nowiki>]
}}

{{TodoEndSubsection}}

=== Point-In-Time Recovery (PITR) ===
{{TodoSubsection}}

{{TodoItem
|Allow archive_mode to be changed without server restart?
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01655.php <nowiki>Enabling archive_mode without restart</nowiki>]
}}

{{TodoEndSubsection}}

=== Standby server mode ===
{{TodoSubsection}}

{{TodoItem
| Allow pg_xlogfile_name() to be used in recovery mode
* [http://archives.postgresql.org/message-id/3f0b79eb1001190135vd9f62f1sa7868abc1ea61d12@mail.gmail.com <nowiki>Streaming replication and pg_xlogfile_name()</nowiki>]
}}

{{TodoItem
| Prevent variables inherited from the server environment from being used for making streaming replication connections
* [http://archives.postgresql.org/pgsql-hackers/2010-02/msg01011.php <nowiki>Re: Parameter name standby_mode</nowiki>]
}}

{{TodoItem
| Change walsender so that it applies per-role settings
* http://archives.postgresql.org/pgsql-hackers/2010-09/msg00642.php
}}

{{TodoEndSubsection}}

== Data Types ==

{{TodoItem
|Fix data types where equality comparison is not intuitive, e.g. box
* http://archives.postgresql.org/pgsql-hackers/2011-10/msg01643.php
}}

{{TodoItem
|Add support for public SYNONYMs
* [http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php <nowiki>Proposal for SYNONYMS</nowiki>]
* http://archives.postgresql.org/pgsql-hackers/2010-11/msg02043.php
* http://archives.postgresql.org/pgsql-general/2010-12/msg00139.php
}}

{{TodoItem
|Consider a special data type for regular expressions
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg01067.php <nowiki>Why is there a tsquery data type?</nowiki>]
}}

{{TodoItem
|Allow deleting enumerated values from an existing enumerated data type
* [http://www.postgresql.org/message-id/CAO%3D2mx6uvgPaPDf-rHqG8%3D1MZnGyVDMQeh8zS4euRyyg4D35OQ@mail.gmail.com Alter or rename enum value]
}}

{{TodoItem
|Add overlaps geometric operators that ignore point overlaps
* http://archives.postgresql.org/pgsql-hackers/2010-03/msg00861.php
}}

{{TodoItem
| Add IMMUTABLE column attribute
* http://archives.postgresql.org/pgsql-hackers/2011-11/msg00623.php
}}

=== Domains ===
{{TodoSubsection}}

{{TodoItem
|Allow functions defined as casts to domains to be called during casting
* [http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php <nowiki>bug? non working casts for domain</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2006-09/msg01681.php <nowiki>TODO: Fix CREATE CAST on DOMAINs</nowiki>]
}}

{{TodoItem
|Allow values to be cast to domain types
* [http://archives.postgresql.org/pgsql-hackers/2003-06/msg01206.php <nowiki>Domain casting still doesn't work right</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg00289.php <nowiki>domain casting?</nowiki>]
* http://archives.postgresql.org/pgsql-hackers/2011-05/msg00812.php
}}

{{TodoItem
|Make domains work better with polymorphic functions
* [http://archives.postgresql.org/message-id/4887.1228700773@sss.pgh.pa.us Polymorphic types vs. domains]
* [http://archives.postgresql.org/message-id/15535.1238774571@sss.pgh.pa.us some difficulties with fixing it]
}}

{{TodoEndSubsection}}

=== Dates and Times ===
{{TodoSubsection}}

{{TodoItem
|Allow infinite intervals just like infinite timestamps
* https://www.postgresql.org/message-id/4EB095C8.1050703@agliodbs.com
}}

{{TodoItem
|Allow TIMESTAMP WITH TIME ZONE to store the original timezone information, either zone name or offset from UTC
|If the TIMESTAMP value is stored with a time zone name, interval computations should adjust based on the time zone rules.
* [https://www.postgresql.org/message-id/Pine.LNX.4.44.0410211300430.2015-100000@zigo.dhs.org <nowiki>timestamp with time zone a la sql99</nowiki>]
}}

{{TodoItem
|Have timestamp subtraction not call justify_hours()?
* [https://www.postgresql.org/message-id/21619.1160067054@sss.pgh.pa.us <nowiki>timestamp subtraction (was Re: formatting intervals with to_char)</nowiki>]
}}

{{TodoItem
|Allow a comma to denote fractional seconds in ISO-8601-compliant times (and timestamps)
* https://www.postgresql.org/message-id/7D5AC9AB-238D-4FE7-8857-18D98190A4D9@justatheory.com
* https://www.postgresql.org/message-id/19944.1529810240%40sss.pgh.pa.us
}}

{{TodoEndSubsection}}

=== Arrays ===
{{TodoSubsection}}

{{TodoItem
|Allow single-byte header storage for array elements}}

{{TodoItem
|Add function to detect if an array is empty
* [http://archives.postgresql.org/pgsql-hackers/2008-11/msg00475.php <nowiki>Re: array_length()</nowiki>]
}}

{{TodoItem
|Improve handling of NULLs in arrays
* [http://archives.postgresql.org/pgsql-bugs/2008-11/msg00009.php <nowiki>BUG #4509: array_cat's null behaviour is inconsistent</nowiki>]
* http://archives.postgresql.org/pgsql-hackers/2010-11/msg01040.php
}}

{{TodoEndSubsection}}

=== MONEY Data Type ===
{{TodoSubsection}}

{{TodoItem
|Add locale-aware MONEY type, and support multiple currencies
* [http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php <nowiki>A real currency type</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php <nowiki>Money type todos?</nowiki>]
}}

{{TodoItem
|MONEY dumps in a locale-specific format making it difficult to restore to a system with a different locale}}

{{TodoEndSubsection}}

=== Text Search ===
{{TodoSubsection}}

{{TodoItem
|Allow dictionaries to change the token that is passed on to later dictionaries
* [http://archives.postgresql.org/pgsql-patches/2007-11/msg00081.php <nowiki>a tsearch2 (8.2.4) dictionary that only filters out stopwords</nowiki>]
}}

{{TodoItem
|Consider a function-based API for '@@' searches
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00511.php <nowiki>Some recent advances in
full-text search</nowiki>]
}}

{{TodoItem
|Improve text search error messages
* [http://archives.postgresql.org/pgsql-hackers/2007-10/msg00966.php <nowiki>Poorly designed tsearch NOTICEs</nowiki>]
}}

{{TodoItem
|Consider changing error to warning for strings larger than one megabyte
* [http://archives.postgresql.org/pgsql-bugs/2008-02/msg00190.php <nowiki>BUG #3975: tsearch2 index should not bomb out of 1Mb limit</nowiki>]
}}

{{TodoItem
|tsearch and tsdicts regression tests fail in Turkish locale on glibc
* [http://archives.postgresql.org/message-id/49749645.5070801@gmx.net tsearch with Turkish locale]
}}

{{TodoItem
|Improve handling of dash and plus signs in email address user names, and perhaps improve URL parsing
* http://archives.postgresql.org/pgsql-hackers/2010-10/msg00772.php
* [http://archives.postgresql.org/message-id/E1Ri8il-0008Ct-9p@wrigleys.postgresql.org tsearch does not recognize all valid emails]
}}

{{TodoItem
|Improve default parser, to more easily allow adding new tokens
* http://archives.postgresql.org/message-id/23485.1297727826@sss.pgh.pa.us
}}

{{TodoItem
|Add additional support functions
* http://archives.postgresql.org/pgsql-hackers/2011-06/msg00319.php
}}

{{TodoEndSubsection}}

=== XML ===
{{TodoSubsection}}

{{TodoItem
|Allow XML arrays to be cast to other data types
* [http://archives.postgresql.org/pgsql-hackers/2007-09/msg00981.php <nowiki>proposal casting from XML[] to int[], numeric[], text[]</nowiki>]
}}

{{TodoItem
|Add XML Schema validation and xmlvalidate functions (SQL:2008)}}

{{TodoItem
|Add xmlvalidatedtd variant to support validating against a DTD?}}

{{TodoItem
|Relax-NG validation; libxml2 supports this already}}

{{TodoItem
|Allow reliable XML operation non-UTF8 server encodings (xpath(), in particular, is known to not work)
* [http://archives.postgresql.org/pgsql-bugs/2009-01/msg00135.php <nowiki>BUG #4622: xpath only work in utf-8 server encoding</nowiki>]
* http://archives.postgresql.org/message-id/4110.1238973350@sss.pgh.pa.us}}

{{TodoItem
|Add functions from SQL:2006: XMLDOCUMENT, XMLCAST, XMLTEXT}}

{{TodoItem
|Add XMLNAMESPACES support in XMLELEMENT and elsewhere}}

{{TodoItem
|Move XSLT from contrib/xml2 to a more reasonable location
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg00539.php
}}

{{TodoItem
|Report errors returned by the XSLT library
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg00562.php
}}

{{TodoItem
|Improve the XSLT parameter passing API
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg00416.php
}}

{{TodoItem
|XML Canonical: Convert XML documents to canonical form to compare them. libxml2 has support for this.}}

{{TodoItem
|Add pretty-printed XML output option
|Parse a document and serialize it back in some indented form. libxml2 might support this.}}

{{TodoItem
|Add XMLQUERY (from the SQL/XML standard)}}

{{TodoItem
|Allow XML shredding
|In some cases shredding could be better option (if there is no need to keep XML docs entirely, e.g. if we have already developed tools that understand only relational data. This would be a separate module that implements annotated schema decomposition technique, similar to DB2 and SQL Server functionality.}}

{{TodoItem
|XPath: Adding the <x> at the root causes problems [http://archives.postgresql.org/pgsql-bugs/2008-05/msg00184.php] [http://archives.postgresql.org/pgsql-bugs/2008-07/msg00054.php] [http://archives.postgresql.org/pgsql-general/2008-07/msg00613.php]}}

{{TodoItem
|xpath_table needs to be implemented/implementable to get rid of contrib/xml2 [http://archives.postgresql.org/pgsql-general/2008-05/msg00823.php]}}

{{TodoItem
|xpath_table is pretty broken anyway [http://archives.postgresql.org/pgsql-hackers/2010-02/msg02424.php]}}

{{TodoItem
|better handling of XPath data types [http://archives.postgresql.org/pgsql-hackers/2008-06/msg00616.php] [http://archives.postgresql.org/message-id/004a01c90e90$4b986d90$e2c948b0$@anstett@iaas.uni-stuttgart.de]}}

{{TodoItem
|Improve handling of PIs and DTDs in xmlconcat() [http://archives.postgresql.org/message-id/200904211211.n3LCB09p008988@wwwmaster.postgresql.org]}}

{{TodoItem
|Restructure XML and /contrib/xml2 functionality
* http://archives.postgresql.org/pgsql-hackers/2011-02/msg02314.php
}}

{{TodoItem
|Verify Xpath escaping behavior
* [http://www.postgresql.org/message-id/E1VOXZv-0008Q9-0Z@wrigleys.postgresql.org Xpath behaviour unintuitive / arguably wrong]
* [http://www.postgresql.org/message-id/CAAY5AM1L83y79rtOZAUJioREO6n4%3DXAFKcGu6qO3hCZE1yJytg@mail.gmail.com xpath missing entity decoding - bug or feature]
}}

{{TodoEndSubsection}}

== Functions ==

{{TodoItem
|Enforce typmod for function inputs, function results and parameters for spi_prepare'd statements called from PLs
* [http://archives.postgresql.org/pgsql-hackers/2007-01/msg01403.php <nowiki>Re: BUG #2917: spi_prepare doesn't accept typename aliases</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2009-11/msg01160.php <nowiki>RFC for adding typmods to functions</nowiki>]
}}

{{TodoItem
|Fix IS OF so it matches the ISO specification, and add documentation
* [http://archives.postgresql.org/pgsql-patches/2003-08/msg00060.php <nowiki>Re: [HACKERS] IS OF</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg00060.php <nowiki>ToDo: add documentation for operator IS OF</nowiki>]
}}

{{TodoItem
|Implement Boyer-Moore searching in LIKE queries
* {{messageLink|27645.1220635769@sss.pgh.pa.us|TODO item: Implement Boyer-Moore searching (First time hacker)}}
* [https://www.postgresql.org/message-id/CALkFZpcbipVJO%3DxVvNQMZ7uLUgHzBn65GdjtBHdeb47QV4XzLw@mail.gmail.com Implement Boyer-Moore searching in LIKE queries]
}}

{{TodoItem
|Prevent malicious functions from being executed with the permissions of unsuspecting users
|Indexed functions are safe, so VACUUM and ANALYZE are safe too. Triggers, CHECK and DEFAULT expressions, and rules are still vulnerable.
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00268.php <nowiki>Some notes about the index-functions security vulnerability</nowiki>]
}}

{{TodoItem
|Reduce memory usage of aggregates in set returning functions
* [http://archives.postgresql.org/pgsql-performance/2008-01/msg00031.php <nowiki>Re: Performance of aggregates over set-returning functions</nowiki>]
}}

{{TodoItem
|Fix /contrib/ltree operator
* [http://archives.postgresql.org/pgsql-bugs/2007-11/msg00044.php <nowiki>BUG #3720: wrong results at using ltree</nowiki>]
}}

{{TodoItem
|Fix /contrib/btree_gist's implementation of inet indexing
* [http://archives.postgresql.org/pgsql-bugs/2010-10/msg00099.php <nowiki>BUG #5705: btree_gist: Index on inet changes query result</nowiki>]
}}

=== Character Formatting ===

{{TodoSubsection}}
{{TodoItem
|Allow to_date() and to_timestamp() to accept localized month names}}

{{TodoItem
|Add missing parameter handling in to_char()
* [http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php <nowiki>Re: to_char and i18n</nowiki>]
}}

{{TodoItem
|Throw an error from to_char() instead of printing a string of "#" when a number doesn't fit in the desired output format.
* discussed in [http://archives.postgresql.org/message-id/37ed240d0907290836w42187222n18664dfcbcb445b1@mail.gmail.com "to_char, support for EEEE format"]
}}

{{TodoItem
|Fix to_number() handling for values not matching the format string
* [http://archives.postgresql.org/pgsql-hackers/2009-09/msg01447.php <nowiki>Re: numeric_to_number() function skipping some digits</nowiki>]
}}

{{TodoEndSubsection}}

== Multi-Language Support ==

{{TodoItem
|Add NCHAR (as distinguished from ordinary varchar)
* [http://www.postgresql.org/message-id/A756FAD7EDC2E24F8CAB7E2F3B5375E918B12BC0@FALEX03.au.fjanz.com UTF8 national character data type support WIP patch and list of open issues.]
}}

{{TodoItem
|Add a cares-about-collation column to pg_proc, so that unresolved-collation errors can be thrown at parse time
* [http://archives.postgresql.org/pgsql-hackers/2011-03/msg01520.php <nowiki>Open issues for collations</nowiki>]
}}

{{TodoItem
|Integrate collations with text search configurations
* [http://archives.postgresql.org/message-id/28887.1303579034@sss.pgh.pa.us <nowiki>Some TODO items for collations</nowiki>]
}}

{{TodoItem
|Integrate collations with to_char() and related functions
* [http://archives.postgresql.org/message-id/28887.1303579034@sss.pgh.pa.us <nowiki>Some TODO items for collations</nowiki>]
}}

{{TodoItem
|Support collation-sensitive equality and hashing functions
* [http://archives.postgresql.org/pgsql-hackers/2011-06/msg00472.php <nowiki> contrib/citext versus collations</nowiki>]
}}

{{TodoItem
|Support multiple simultaneous character sets, per SQL:2008}}

{{TodoItem
|Improve UTF8 combined character handling?}}

{{TodoItem
|Add octet_length_server() and octet_length_client()}}

{{TodoItem
|Make octet_length_client() the same as octet_length()?}}

{{TodoItem
|Fix problems with wrong runtime encoding conversion for NLS message files}}

{{TodoItem
|Fix contrib/fuzzystrmatch to work with multibyte encodings
* [http://archives.postgresql.org/pgsql-bugs/2009-04/msg00047.php <nowiki> soundex function returns UTF-16 characters</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2010-04/msg00138.php <nowiki> dmetaphone woes</nowiki>]
}}

{{TodoItem
|Change memory allocation for multi-byte functions so memory is allocated inside conversion functions
|Currently we preallocate memory based on worst-case usage.}}

{{TodoItem
|Add ability to use case-insensitive regular expressions on multi-byte characters
|Currently it works for UTF-8, but not other multi-byte encodings
* [http://archives.postgresql.org/pgsql-hackers/2008-12/msg00433.php <nowiki>Regexps vs. locale</nowiki>]
* {{MessageLink|20091201210024.B1393753FB7@cvs.postgresql.org|A partial solution for UTF-8}}
}}

{{TodoItem
|Improve encoding of connection startup messages sent to the client
|Currently some authentication error messages are sent in the server encoding
* [http://archives.postgresql.org/pgsql-general/2008-12/msg00801.php <nowiki>encoding of PostgreSQL messages</nowiki>]
* [http://www.postgresql.org/message-id/20131220030725.GA1411150@tornado.leadboat.com multibyte messages are displayed incorrectly on the client]
}}

{{TodoItem
|Windows: Cache MessageEncoding conversion for use outside transactions
* http://www.postgresql.org/message-id/20150812055719.GA1945333@tornado.leadboat.com
}}

{{TodoItem
|More sensible support for Unicode combining characters, normal forms
* http://archives.postgresql.org/message-id/200904141532.44618.peter_e@gmx.net
}}

== Views and Rules ==

{{TodoItem
|Allow VIEW/RULE recompilation when the underlying tables change
|This is both difficult and controversial.
* [http://archives.postgresql.org/pgsql-hackers/2009-12/msg01723.php Re: About "Allow VIEW/RULE recompilation when the underlying tables change"]
* [http://archives.postgresql.org/pgsql-hackers/2009-12/msg01724.php Re: About "Allow VIEW/RULE recompilation when the underlying tables change2"]
* [http://archives.postgresql.org/message-id/CACk%3DU9NFSzWrEba8G5dZ%3DTZLy3_hx3QXGyCcKVWT%3D4iA1FjMuA@mail.gmail.com VIEW still referring to old name of field]
* [http://www.postgresql.org/message-id/87mwe4k46y.fsf@commandprompt.com Re-create dependent views on ALTER TABLE ALTER COLUMN ... TYPE?]
}}
{{TodoItem
|Make it possible to use RETURNING together with conditional DO INSTEAD rules, such as for partitioning setups
* [http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php <nowiki>RETURNING and DO INSTEAD ... Intentional or not?</nowiki>]
}}

{{TodoItem
|Improve ability to modify views via ALTER TABLE
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00691.php <nowiki>Re: idea: storing view source in system catalogs</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg01410.php <nowiki>modifying views</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-08/msg00300.php <nowiki>Re: patch: Add columns via CREATE OR REPLACE VIEW</nowiki>]
}}

{{TodoItem
|Allow ALTER INDEX ... RENAME concurrently
* [https://www.postgresql.org/message-id/1531767486.432607658@f357.i.mail.ru Alter index rename concurrently to]
}}

== SQL Commands ==

{{TodoItem
|Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT
* [http://web.archive.org/web/20161019182747/dissipatedheat.com/2011/11/10/how-not-to-write-a-patch-for-postgresql/ How not to write this patch.]
}}

{{TodoItem
|Improve type determination of unknown (NULL or quoted literal) result columns for UNION/INTERSECT/EXCEPT
* [http://archives.postgresql.org/message-id/9799.1302719551@sss.pgh.pa.us <nowiki>UNION construct type cast gives poor error message</nowiki>]
}}

{{TodoItem
|Allow prepared transactions with temporary tables created and dropped in the same transaction, and when an ON COMMIT DELETE ROWS temporary table is accessed
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00047.php <nowiki>Re: "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables</nowiki>]
* [http://archives.postgresql.org/message-id/492543D5.9050904@enterprisedb.com A suggestion on how to implement this]
}}

{{TodoItem
|Add a GUC variable to warn about non-standard SQL usage in queries}}

{{TodoItem
|Add NOVICE output level for helpful messages
|For example, have it warn about unjoined tables. This could also control automatic sequence/index creation messages.
}}

{{TodoItem
|Add SQL-standard MERGE command
|MERGE is typically used to merge two tables, for data warehousing type use cases.
* PostgreSQL has an "UPSERT" command as of version 9.5, with the addition of "ON CONFLICT DO UPDATE". SQL MERGE is independently useful, though.
* A patch for this that made it into Postgres 11 was reverted.
}}

{{TodoItem
|Allow NOTIFY in rules involving conditionals}}

{{TodoItem
|Allow LISTEN on patterns
* http://www.postgresql.org/message-id/52693FC5.7070507@gmail.com
}}

{{TodoItem
|Simplify dropping roles that have objects in several databases}}

{{TodoItem
|Add support for WITH RECURSIVE ... CYCLE
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg00291.php <nowiki>WITH RECURSIVE ... CYCLE in vanilla SQL: issues with arrays of rows</nowiki>]}}

{{TodoItem
|Add DEFAULT .. AS OWNER so permission checks are done as the table owner
|This would be useful for SERIAL nextval() calls and CHECK constraints.}}

{{TodoItem
|Allow DISTINCT to work in multiple-argument aggregate calls}}

{{TodoItem
|Add comments on system tables/columns using the information in catalogs.sgml
|Ideally the information would be pulled from the SGML file automatically.}}

{{TodoItem
|Prevent the specification of conflicting transaction read/write options
* [http://archives.postgresql.org/pgsql-hackers/2009-01/msg00684.php <nowiki>Re: SET TRANSACTION and SQL Standard</nowiki>]
}}

{{TodoItem
|Allow DELETE and UPDATE to be used with LIMIT and ORDER BY
* http://archives.postgresql.org/pgadmin-hackers/2010-04/msg00078.php
* http://archives.postgresql.org/pgsql-hackers/2010-11/msg01997.php
}}

{{TodoItem
|Allow PREPARE of cursors}}

{{TodoItem
|Have DISCARD PLANS discard plans cached by functions
|DISCARD ALL should do the same.
* http://archives.postgresql.org/pgsql-hackers/2011-01/msg00431.php
}}

{{TodoItem
|Avoid multiple-evaluation of BETWEEN and IN arguments containing volatile expressions
* http://archives.postgresql.org/message-id/4D95B605.2020709@enterprisedb.com
}}

=== CREATE ===
{{TodoSubsection}}

{{TodoItem
|Allow CREATE TABLE AS to determine column lengths for complex expressions like SELECT col1 || col2}}

{{TodoItem
|Have WITH CONSTRAINTS also create constraint indexes
* [http://archives.postgresql.org/pgsql-patches/2007-04/msg00149.php <nowiki>Re: CREATE TABLE LIKE INCLUDING INDEXES support</nowiki>]
}}

{{TodoItem
|Move NOT NULL constraint information to pg_constraint
|Currently NOT NULL constraints are stored in pg_attribute without any designation of their origins, e.g. primary keys. One manifest problem is that dropping a PRIMARY KEY constraint does not remove the NOT NULL constraint designation. Another issue is that we should probably force NOT NULL to be propagated from parent tables to children, just as CHECK constraints are. (But then does dropping PRIMARY KEY affect children?)
* http://archives.postgresql.org/message-id/19768.1238680878@sss.pgh.pa.us
* http://archives.postgresql.org/message-id/200909181005.n8IA5Ris061239@wwwmaster.postgresql.org
* http://archives.postgresql.org/pgsql-hackers/2011-07/msg01223.php
* http://archives.postgresql.org/pgsql-hackers/2011-07/msg00358.php
* [https://www.postgresql.org/message-id/CAB7nPqTPXgX9HiyhhtAgpW7jbA1iskMCSoqXPEEB_KYXYy1E1Q@mail.gmail.com Prevent ALTER TABLE DROP NOT NULL on child tables if parent column has it]
}}

{{TodoItem
|Prevent concurrent CREATE TABLE from sometimes returning a cryptic error message
* [http://archives.postgresql.org/pgsql-bugs/2007-10/msg00169.php <nowiki>BUG #3692: Conflicting create table statements throw unexpected error</nowiki>]
}}

{{TodoItem
|Add CREATE SCHEMA ... LIKE that copies a schema}}

{{TodoItem
|Fix CREATE OR REPLACE FUNCTION to not leave objects depending on the function in inconsistent state
* [http://archives.postgresql.org/pgsql-general/2008-08/msg00985.php indexes on functions and create or replace function]
}}

{{TodoItem
|Allow temporary tables to exist as empty by default in all sessions
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00006.php <nowiki>what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg01329.php <nowiki>idea: global temp tables</nowiki>]
* [http://archives.postgresql.org//pgsql-hackers/2009-05/msg00016.php <nowiki>Re: idea: global temp tables</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2010-04/msg01098.php <nowiki>global temporary tables</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2012-04/msg01148.php Temporary tables under hot standby]
* [http://www.postgresql.org/message-id/CAFj8pRC2h6qhHsFbcE7b_7SagiS6o%3D5J2UvCwCb05Ka1XFv_Ng@mail.gmail.com Implementation of global temporary tables?]
}}

{{TodoItem
|Allow the creation of "distinct" types
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01647.php <nowiki>Distinct types</nowiki>]
}}

{{TodoItem
|Consider analyzing temporary tables when they are first used in a query
|Autovacuum cannot analyze or vacuum temporary tables.
* [http://archives.postgresql.org/pgsql-hackers/2010-04/msg00416.php <nowiki>autovacuum and temp tables support</nowiki>]
}}

{{TodoEndSubsection}}

=== UPDATE ===
{{TodoSubsection}}

{{TodoItem
|Research self-referential UPDATEs that see inconsistent row versions in read-committed mode
* [http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php <nowiki>Concurrently updating an updatable view</nowiki>]
}}

{{TodoItem
|Improve performance of EvalPlanQual mechanism that rechecks already-updated rows
|This is related to the previous item, which questions whether it even has the right semantics
* [http://archives.postgresql.org/pgsql-bugs/2008-09/msg00045.php <nowiki>BUG #4401: concurrent updates to a table blocks one update indefinitely</nowiki>]
* [http://archives.postgresql.org/pgsql-bugs/2009-07/msg00302.php <nowiki>BUG #4945: Parallel update(s) gone wild</nowiki>]
}}

{{TodoEndSubsection}}

=== ALTER ===
{{TodoSubsection}}

{{TodoItem
|Have ALTER TABLE RENAME of a SERIAL column rename the sequence
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php <nowiki>Re: newbie: renaming sequences task</nowiki>]
* [http://archives.postgresql.org/message-id/CADLWmXUV4LbLhMZL8rYMhCy72aZZLB5BSARPQVgoX0BrxA0FFg@mail.gmail.com renaming implicit sequences]
}}

{{TodoItem
|Add ALTER DOMAIN to modify the underlying data type}}

{{TodoItem
|Allow ALTER TABLESPACE to move the tablespace to different directories}}

{{TodoItem
|Allow moving system tables to other tablespaces, where possible
|Currently non-global system tables must be in the default database tablespace. Global system tables can never be moved.}}

{{TodoItem
|Have ALTER INDEX update the name of a constraint using that index}}

{{TodoItem
|Allow column display reordering by recording a display, storage, and permanent id for every column?
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php <nowiki>Re: column ordering, was Re: [PATCHES] Enums patch v2</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-11/msg01029.php <nowiki>Column reordering in pg_dump</nowiki>]
* http://archives.postgresql.org/message-id/1324412114-sup-9608@alvh.no-ip.org
* [http://www.postgresql.org/message-id/CAApHDvqhnuznxd4xVMFDcGn+nHVYyUtJ-TvbRsOuR%3DPaVbbGqw@mail.gmail.com logical column order and physical column order]
* [http://www.postgresql.org/message-id/20141209174146.GP1768@alvh.no-ip.org logical column ordering]
}}

{{TodoItem
|Allow deactivating (and reactivating) indexes via ALTER TABLE
* http://archives.postgresql.org/pgsql-hackers/2010-12/msg01191.php
}}

{{TodoItem
|Add ALTER OPERATOR ... RENAME
|needs to consider effects of changing operator precedence
* [http://archives.postgresql.org/message-id/1322948781.26266.9.camel@vanquo.pezone.net Missing rename support]
}}

{{TodoEndSubsection}}

=== CLUSTER ===
{{TodoSubsection}}

{{TodoItem
|Automatically maintain clustering on a table
|This might require some background daemon to maintain clustering during periods of low usage. It might also require tables to be only partially filled for easier reorganization. Another idea would be to create a merged heap/index data file so an index lookup would automatically access the heap data too. A third idea would be to store heap rows in hashed groups, perhaps using a user-supplied hash function.
* [http://archives.postgresql.org/pgsql-performance/2004-08/msg00350.php <nowiki>Equivalent praxis to CLUSTERED INDEX?</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00155.php <nowiki>Re: Grouped Index Tuples</nowiki>]
* http://community.enterprisedb.com/git/
* [http://archives.postgresql.org/pgsql-performance/2009-10/msg00346.php <nowiki>Re: maintain_cluster_order_v5.patch</nowiki>]
}}

{{TodoItem
| Allow CLUSTER to be used on partial indexes
* http://www.postgresql.org/message-id/CAMkU%3D1zYwoHHsqJ8wfK3GdG_t_a6t4RK-GFDSKymQ0EGP%3DtypA@mail.gmail.com
}}

{{TodoEndSubsection}}

=== COPY ===
{{TodoSubsection}}

{{TodoItem
|Allow COPY to report error lines and continue
|This requires the use of a savepoint before each COPY line is processed, with ROLLBACK on COPY failure.
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00572.php <nowiki>Re: VLDB Features</nowiki>]
}}

{{TodoItem
|Allow COPY to report errors sooner
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg01169.php <nowiki>Timely reporting of COPY errors</nowiki>]
}}

{{TodoItem
|Allow COPY FROM to create index entries in bulk
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00811.php <nowiki>Batch update of indexes on data loading</nowiki>]
}}

{{TodoItem
|Improve COPY performance
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00954.php <nowiki>Re: 8.3 / 8.2.6 restore comparison</nowiki>]
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg01882.php
}}

{{TodoItem
|Allow a stalled COPY to exit if the backend is terminated
* [http://archives.postgresql.org/pgsql-bugs/2009-04/msg00067.php <nowiki>Re: possible bug not in open items</nowiki>]
}}

{{TodoItem
|Allow COPY "text" format to output a header
* [http://www.postgresql.org/message-id/CACfv+pJ31tesLvncJyP24quo8AE+M0GP6p6MEpwPv6yV8%3DsVHQ@mail.gmail.com Why doesn't COPY support the HEADER options for tab-separated output?]
}}

{{TodoItem
|Have COPY FREEZE set PD_ALL_VISIBLE
* [http://www.postgresql.org/message-id/CAMkU%3D1w3osJJ2FneELhhNRLxfZitDgp9FPHee08NT2FQFmz_pQ@mail.gmail.com items]
}}

{{TodoEndSubsection}}

=== GRANT/REVOKE ===
{{TodoSubsection}}

{{TodoItem
|Allow dropping of a role that has connection rights
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00736.php <nowiki>DROP ROLE dependency tracking ...</nowiki>]
}}
{{TodoEndSubsection}}

=== DECLARE CURSOR ===
{{TodoSubsection}}

{{TodoItem
|Prevent DROP TABLE from dropping a table referenced by its own open cursor?}}

{{TodoItem
|Provide some guarantees about the behavior of cursors that invoke volatile functions
* [http://archives.postgresql.org/message-id/20997.1244563664@sss.pgh.pa.us Re: Cursor with hold emits the same row more than once across commits in 8.3.7]
}}

{{TodoEndSubsection}}

=== SHOW/SET ===
{{TodoSubsection}}

{{TodoItem
|Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM ANALYZE, and CLUSTER}}

{{TodoItem
|Rationalize the discrepancy between settings that use values in bytes and SHOW that returns the object count
* [http://archives.postgresql.org/pgsql-docs/2008-07/msg00007.php <nowiki>Re: [ADMIN] shared_buffers and shmmax</nowiki>]
}}

{{TodoEndSubsection}}

=== ANALYZE ===
{{TodoSubsection}}

{{TodoItem
|Improve how ANALYZE computes in-doubt tuples
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00771.php <nowiki>VACUUM/ANALYZE counting of in-doubt tuples</nowiki>]
}}

{{TodoItem
|Remove quadratic time in statistics sender when analyzing many tables
* [http://www.postgresql.org/message-id/flat/CAMkU%3D1wLjAsmJNuB6ZObZmGHqi9jLbK6n1eSgnOc5J1-AUsvUA@mail.gmail.com Thousands of schemas and ANALYZE goes out of memory]
}}

{{TodoItem
|Reduce memory use when analyzing many tables in a single command by making catcache and syscache flushable or bounded.
* [http://www.postgresql.org/message-id/flat/CAMkU%3D1yZnAYvMHENt8%3D9pgwE8q5zmX+mG%3DSXbFHiLkq_qn0B7Q@mail.gmail.com Thousands of schemas and ANALYZE goes out of memory]
}}

{{TodoEndSubsection}}

=== EXPLAIN ===
{{TodoSubsection}}
{{TodoItem
|Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and actual row counts differ by a specified percentage}}

{{TodoItem
|Have EXPLAIN ANALYZE report rows as floating-point numbers
* [http://archives.postgresql.org/pgsql-hackers/2009-05/msg01363.php <nowiki>explain analyze rows=%.0f</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2009-06/msg00108.php <nowiki>Re: explain analyze rows=%.0f</nowiki>]
}}

{{TodoItem
|Have EXPLAIN ANALYZE report buckets and memory usage for HashAggregate
* [https://www.postgresql.org/message-id/flat/2527f5cb-5992-ae66-f3ec-4aa2396065ec%402ndquadrant.com <nowiki>to-do item for explain analyze of hash aggregates? </nowiki>]
}}

{{TodoEndSubsection}}

=== Window Functions ===
See {{messageLink|357.1230492361@sss.pgh.pa.us|TODO items for window functions}}.
{{TodoSubsection}}
{{TodoItem
|Support creation of user-defined window functions
|We have the ability to create new window functions written in C. Is it
worth the effort to create an API that would let them be written in PL/pgsql, etc?}}

{{TodoItem
|Implement full support for window framing clauses
|In addition to done clauses described in the [http://developer.postgresql.org/pgdocs/postgres/sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS latest doc], these clauses are not implemented yet.
* RANGE BETWEEN ... PRECEDING/FOLLOWING
* EXCLUDE
}}

{{TodoItem
|Investigate tuplestore performance issues
|The tuplestore_in_memory() thing is just a band-aid, we ought to try to solve it properly. tuplestore_advance seems like a weak spot as well.
* [http://archives.postgresql.org/pgsql-hackers/2008-12/msg00152.php <nowiki>tuplestore potential performance problem</nowiki>]
}}

{{TodoItem|Do we really need so much duplicated code between Agg and WindowAgg?}}

{{TodoItem
|Teach planner to evaluate multiple windows in the optimal order
|Currently windows are always evaluated in the query-specified order.
* http://archives.postgresql.org/message-id/3CDAD71E9D70417290FCF66F0178D1E1@amd64
}}

{{TodoItem
|Implement DISTINCT clause in window aggregates
|Some proprietary RDBMSs have implemented it already, so it helps with porting from those.}}

{{TodoEndSubsection}}

== Integrity Constraints ==
=== Keys ===

{{TodoSubsection}}

{{TodoItem
|Improve deferrable unique constraints for cases with many conflicts
|The current implementation fires a trigger for each potentially conflicting row. This might not scale well for an update that changes many key values at once.
}}

{{TodoEndSubsection}}

=== Referential Integrity ===
{{TodoSubsection}}

{{TodoItem
|Add MATCH PARTIAL referential integrity}}

{{TodoItem
|Change foreign key constraint for array -> element to mean element in array?
* [http://archives.postgresql.org/pgsql-hackers/2010-10/msg01814.php <nowiki>foreign keys for array/period contains relationships</nowiki>]
}}

{{TodoItem
|Fix problem when cascading referential triggers make changes on cascaded tables, seeing the tables in an intermediate state
* [http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php <nowiki>Re: [PATCHES] Work-in-progress referential action trigger timing</nowiki>]
}}

{{TodoItem
|Are ri_KeysEqual checks in the RI enforcement triggers still necessary?
* [http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php <nowiki>Re: Effects of cascading references in foreign keys</nowiki>]
}}

{{TodoEndSubsection}}

=== Check Constraints ===
{{TodoSubsection}}

{{TodoItem
|Run check constraints only when affected columns are changed
* http://archives.postgresql.org/message-id/1326055327.15293.13.camel@vanquo.pezone.net
}}

{{TodoItem
|Do not scan the table when a check constraint is added in the same command that adds the column
* [http://www.postgresql.org/message-id/CAMkU%3D1z5vXZ8Txd9_8hvNFovtbGuP4VTitFRN59XDncEHVGtJA@mail.gmail.com skip table scan for adding column with provable check constraints]
}}

{{TodoEndSubsection}}

== Server-Side Languages ==

{{TodoItem
|Add support for polymorphic arguments and return types to languages other than PL/PgSQL}}

{{TodoItem
|Add support for OUT and INOUT parameters to languages other than PL/PgSQL}}

{{TodoItem
|Add more fine-grained specification of functions taking arbitrary data types
* [http://archives.postgresql.org/pgsql-hackers/2009-09/msg00367.php <nowiki>RfD: more powerful "any" types</nowiki>]
}}

{{TodoItem
|Allow holdable cursors in SPI}}

{{TodoItem
|Rethink query plan caching and timing of parse analysis within SQL-language functions
|They should work more like plpgsql functions do ...
* [http://archives.postgresql.org/pgsql-bugs/2011-05/msg00078.php <nowiki>Re: BUG #6019: invalid cached plan on inherited table</nowiki>]
}}

{{TodoItem
|Allow regex operations in PL/Perl using UTF8 characters in non-UTF8 encoded databases}}

=== PL/pgSQL ===
{{TodoSubsection}}

{{TodoItem
|Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]}}

{{TodoItem
|<nowiki>Allow listing of record column names, and access to record columns via variables, e.g. columns := r.(*), tval2 := r.(colname)</nowiki>
* [http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php <nowiki>Re: PL/PGSQL: Dynamic Record Introspection</nowiki>]
* [http://pgxn.org/dist/colnames/ <nowiki>colnames: Extension to retrieve column names from a record</nowiki>]
}}

{{TodoItem
|Allow row and record variables to be set to NULL constants, and allow NULL tests on such variables
|Because a row is not scalar, do not allow assignment from NULL-valued scalars.
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg00070.php <nowiki>NULL and plpgsql rows</nowiki>]
}}

{{TodoItem
|Consider keeping separate cached copies when search_path changes
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg01009.php <nowiki>pl/pgsql Plan Invalidation and search_path</nowiki>]
}}

{{TodoItem
|Improve handling of NULL row values vs. NULL rows
* [http://archives.postgresql.org/pgsql-hackers/2008-09/msg01758.php <nowiki>Null row vs. row of nulls in plpgsql</nowiki>]
* http://archives.postgresql.org/pgsql-hackers/2010-10/msg01973.php
}}

{{TodoItem
|Improve PERFORM handling of WITH queries or document limitation
* http://archives.postgresql.org/pgsql-bugs/2011-03/msg00309.php
}}

{{TodoEndSubsection}}

=== PL/Python ===
{{TodoSubsection}}

{{TodoItem
|Create a new restricted execution class that will allow passing function arguments in as locals. Passing them as globals means functions cannot be called recursively.
* [http://archives.postgresql.org/pgsql-hackers/2011-02/msg01468.php <nowiki>Re: pl/python do not delete function arguments</nowiki>]
}}

{{TodoItem
|Add a DB-API compliant interface on top of the SPI interface
* http://petereisentraut.blogspot.com/2011/11/plpydbapi-db-api-for-plpython.html
}}

{{TodoItem
|For functions returning a setof record with a composite type, cache the I/O functions for the composite type
* http://archives.postgresql.org/pgsql-hackers/2010-12/msg02007.php
}}

{{TodoEndSubsection}}

== Clients ==

{{TodoItem
|Split out pg_resetxlog output into pre- and post-sections
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg02040.php
}}

{{TodoItem
|Improve pg_rewind
* [https://www.postgresql.org/message-id/CAN-RpxDhc_8JOq%3DcT9vd6MqWQaS0ZtvSf2LFV1V+bjOoEz02ow@mail.gmail.com Proposal: pg_rewind to skip config files]
}}

=== psql ===
{{TodoSubsection}}

{{TodoItem
|Move psql backslash database information into the backend, use mnemonic commands?
|This would allow non-psql clients to pull the same information out of the database as psql.
* [http://archives.postgresql.org/pgsql-hackers/2004-01/msg00191.php <nowiki>Re: psql \d option list overloaded</nowiki>]
}}

{{TodoItem
|Make psql's \d commands distinguish default privileges from no privileges
|ACL displays were visibly different for the two cases before we "improved" them by using array_to_string.
* [http://archives.postgresql.org/pgsql-bugs/2011-05/msg00082.php <nowiki>BUG #6021: There is no difference between default and empty access privileges with \dp</nowiki>]
}}

{{TodoItem
|Consistently display privilege information for all objects in psql}}

{{TodoItem
|Add a \set variable to control whether \s displays line numbers
|Another option is to add \# which lists line numbers, and allows command execution.
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php <nowiki>Re: psql possible TODO</nowiki>]
}}

{{TodoItem
|Include the symbolic SQLSTATE name in verbose error reports
* [http://archives.postgresql.org/pgsql-general/2007-09/msg00438.php <nowiki>Re: Checking is TSearch2 query is valid</nowiki>]
}}

{{TodoItem
|Add option to wrap column values at whitespace boundaries, rather than chopping them at a fixed width.
|Currently, "wrapped" format chops values into fixed widths. Perhaps the word wrapping could use the same algorithm documented in the W3C specification.
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php <nowiki>Re: psql wrapped format default for backslash-d commands</nowiki>]
* http://www.w3.org/TR/CSS21/tables.html#auto-table-layout}}

{{TodoItem
|Add option to print advice for people familiar with other databases
* [http://archives.postgresql.org/pgsql-hackers/2010-01/msg01845.php <nowiki>MySQL-ism help patch for psql</nowiki>]
}}

{{TodoItem
|Fix FETCH_COUNT to handle SELECT ... INTO and WITH queries
* http://archives.postgresql.org/pgsql-hackers/2010-05/msg01565.php
* http://archives.postgresql.org/pgsql-bugs/2010-05/msg00192.php
}}

{{TodoItem
|Prevent psql from sending remaining single-line multi-statement queries after reconnecting
* http://archives.postgresql.org/pgsql-bugs/2010-05/msg00159.php
* http://archives.postgresql.org/pgsql-hackers/2010-05/msg01283.php
}}

{{TodoItem
|Improve line drawing characters
* http://archives.postgresql.org/pgsql-hackers/2011-04/msg00386.php
}}

{{TodoItem
|Consider improving the continuation prompt
* http://archives.postgresql.org/pgsql-hackers/2011-04/msg01772.php
}}

{{TodoItem
|Improve speed of tab completion by using LIKE
* http://www.postgresql.org/message-id/20120821174847.GL1267@tamriel.snowman.net
}}

{{TodoEndSubsection}}

=== pg_dump / pg_restore ===
{{TodoSubsection}}

{{TodoItemEasy
|Dump security labels and comments on databases in a way that allows to load a dump into a differently named database
* [http://www.postgresql.org/message-id/20150710115735.GH26521@alap3.anarazel.de security labels on databases are bad for dump & restore]
|}}

{{TodoItemEasy
|<nowiki>Add full object name to the tag field. eg. for operators we need '=(integer, integer)', instead of just '='.</nowiki>}}

{{TodoItem
|Avoid using platform-dependent names for locales in pg_dumpall output
|Using native locale names puts roadblocks in the way of porting a dump to another platform. One possible solution is to get
CREATE DATABASE to accept some agreed-on set of locale names and fix them up to meet the platform's requirements.
* http://archives.postgresql.org/message-id/21396.1241716688@sss.pgh.pa.us
}}

{{TodoItem
|In a selective dump, allow dumping of an object and all its dependencies}}

{{TodoItem
|Stop dumping CASCADE on DROP TYPE commands in clean mode}}

{{TodoItem
|Allow pg_restore to load different parts of the COPY data for a single table simultaneously}}

{{TodoItem
|Preserve sparse storage of large objects over dump/restore
* [http://archives.postgresql.org/message-id/18789.1349750451@sss.pgh.pa.us <nowiki>TODO item: teach pg_dump about sparsely-stored large objects</nowiki>]
}}

{{TodoItem
|Prevent PL/pgSQL comment from throwing an error in a non-superuser restore
* [http://www.postgresql.org/message-id/E1VuYH7-0008Rz-SV@wrigleys.postgresql.org Reloading dump fails at COMMENT ON EXTENSION plpgsql]
}}

{{TodoItem
|Delay REFRESH MATERIALIZED VIEW until dependent indexes are created
* [http://www.postgresql.org/message-id/20140820021530.2534.43156@wrigleys.postgresql.org pg_restore unusable for expensive matviews]
}}

{{TodoEndSubsection}}

=== pg_upgrade ===
{{TodoSubsection}}

{{TodoItem
|Handle large object comments
|This is difficult to do because the large object doesn't exist when --schema-only is loaded.
}}

{{TodoItem
|Consider using pg_depend for checking object usage in version.c
}}

{{TodoItem
|Migrate pg_statistic by dumping it out as a flat file, so analyze is not necessary
* [http://archives.postgresql.org/message-id/CAAZKuFaWdLkK8eozSAooZBets9y_mfo2HS6urPAKXEPbd-JLCA@mail.gmail.com pg_upgrade and statistics]
* [https://www.postgresql.org/message-id/20171205140135.GA25023%40momjian.us Speeding up pg_upgrade]
}}

{{TodoItem
|Find cleaner way to start/stop dedicated servers for upgrades
* http://archives.postgresql.org/pgsql-hackers/2012-08/msg00275.php
}}

{{TodoItem
|Desired changes that would prevent upgrades with pg_upgrade
* 32-bit page checksums
* Add metapage to GiST indexes
* Clean up hstore's internal representation
* Remove tuple infomask bit HEAP_MOVED_OFF and HEAP_MOVED_IN
* [http://www.postgresql.org/message-id/CAK+WP1xdmyswEehMuetNztM4H199Z1w9KWRHVMKzyyFM+hV%3DzA@mail.gmail.com fix char() index trailing space handling]
* [http://www.postgresql.org/message-id/CAPpHfdtxXMjyZxwND09ZLBBACVbWb5J9bLUf67CndR4VKFDgwg@mail.gmail.com Use non-collation-aware comparisons for GIN opclasses]
}}

{{TodoEndSubsection}}

=== ecpg ===
{{TodoSubsection}}

{{TodoItem
|Docs
|Document differences between ecpg and the SQL standard and information about the Informix-compatibility module.}}

{{TodoItem
|Solve cardinality > 1 for input descriptors / variables?}}

{{TodoItem
|Add a semantic check level, e.g. check if a table exists}}

{{TodoItem
|fix handling of DB attributes that are arrays}}

{{TodoItem
|Fix nested C comments}}

{{TodoItemEasy
|sqlwarn[6] should be 'W' if the PRECISION or SCALE value specified}}

{{TodoItem
|Make SET CONNECTION thread-aware, non-standard?}}

{{TodoItem
|Allow multidimensional arrays}}

{{TodoItem
|Implement COPY FROM STDIN}}

{{TodoItem
|Provide a way to specify size of a bytea parameter
* [http://archives.postgresql.org/message-id/200906192131.n5JLVoMo044178@wwwmaster.postgresql.org <nowiki>BUG #4866: ECPG and BYTEA</nowiki>]
}}

{{TodoItemEasy
|Fix small memory leaks in ecpg
|Memory leaks in a short running application like ecpg are not really a problem, but make debugging more complicated}}

{{TodoItem
|Allow reuse of cursor name variables
* [http://archives.postgresql.org/message-id/20100329113435.GA3430@feivel.credativ.lan <nowiki>Problems with variable cursorname in ecpg</nowiki>]
}}

{{TodoEndSubsection}}

=== libpq ===
{{TodoSubsection}}

{{TodoItem
|Add PQexecf() that allows complex parameter substitution
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php <nowiki>Last minute mini-proposal (I know, know) for PQexecf()</nowiki>]
}}

{{TodoItem
|Add SQLSTATE and severity to errors generated within libpq itself
* [http://archives.postgresql.org/pgsql-interfaces/2007-11/msg00015.php <nowiki>v8.1: Error severity on libpq PGconn*</nowiki>]
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg01425.php
}}

{{TodoItem
|Add support for interface/ipaddress binding to libpq
* [http://archives.postgresql.org/pgsql-hackers/2010-02/msg01811.php <nowiki>SR/libpq - outbound interface/ipaddress binding</nowiki>]
}}

{{TodoItem
|When receiving a FATAL error remember it, so that it doesn't profess ingnorance about why the session was closed
* [http://www.postgresql.org/message-id/CA+TgmoZ4P1cQetjOxQoHiG072UcE7dpE7dTBV8hMOidhwhof+g@mail.gmail.com<nowiki>Idle In Transaction Session Timeout, revived</nowiki>]
}}

{{TodoItem
|Pipelining support for libpq async API and an array-valued PQexecPrepared that uses it
* [http://www.postgresql.org/message-id/CAMsr+YHE8Rt800yWcHEL8SrgruK0ng_nBmtKV6YMZ2BAzRBZzw@mail.gmail.com Foreign table batched inserts]
}}
{{TodoEndSubsection}}

== Triggers ==

{{TodoItem
|Improve storage of deferred trigger queue
|Right now all deferred trigger information is stored in backend memory. This could exhaust memory for very large trigger queues. This item involves dumping large queues into files, or doing some kind of join to process all the triggers, some bulk operation, or a bitmap.
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00876.php <nowiki>Re: BUG #4204: COPY to table with FK has memory leak</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2009-10/msg00464.php <nowiki>Scaling up deferred unique checks and the after trigger queue</nowiki>]
* http://archives.postgresql.org/pgsql-hackers/2011-08/msg00023.php
}}

{{TodoItem
|Allow triggers to be disabled in only the current session.
|This is currently possible by starting a multi-statement transaction, modifying the system tables, performing the desired SQL, restoring the system tables, and committing the transaction. ALTER TABLE ... TRIGGER requires a table lock so it is not ideal for this usage.}}

{{TodoItem
|With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY
|If the dump is known to be valid, allow foreign keys to be added without revalidating the data.}}

{{TodoItem
|When statement-level triggers are defined on a parent table, have them fire only on the parent table, and fire child table triggers only where appropriate
* [http://archives.postgresql.org/pgsql-hackers/2008-11/msg01883.php <nowiki>Statement-level triggers and inheritance</nowiki>]
}}

{{TodoItem
|Tighten trigger permission checks
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php <nowiki>Security leak with trigger functions?</nowiki>]
}}

{{TodoItem
|Allow BEFORE INSERT triggers on views
* [http://archives.postgresql.org/pgsql-general/2007-02/msg01466.php <nowiki>Re: Why can't I put a BEFORE EACH ROW trigger on a view?</nowiki>]
}}

{{TodoItem
|Add database and transaction-level triggers
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00451.php <nowiki>Proposal for db level triggers</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00620.php <nowiki>triggers on prepare, commit, rollback... ?</nowiki>]
}}

{{TodoItem
|Avoid requirement for AFTER trigger functions to return a value
* http://archives.postgresql.org/pgsql-hackers/2011-02/msg02384.php
}}

{{TodoItem
|Allow creation of inline triggers
* http://archives.postgresql.org/pgsql-hackers/2012-02/msg00708.php
}}

== Inheritance ==

{{TodoItem
|Allow unique indexes across inherited tables (requires multi-table indexes)
* Postgres 11 allows unique indexes across partitions if the partition key is part of the index.
}}

{{TodoItem
|Research whether ALTER TABLE / SET SCHEMA should work on inheritance hierarchies (and thus support ONLY)}}

{{TodoItem
|ALTER TABLE variants sometimes support recursion and sometimes not, but this is poorly/not documented, and the ONLY marker would then be silently ignored. Clarify the documentation, and reject ONLY if it is not supported.}}

== Indexes ==

{{TodoItem
|Prevent index uniqueness checks when UPDATE does not modify the column
|Uniqueness (index) checks are done when updating a column even if the column is not modified by the UPDATE.
However, HOT already short-circuits this in common cases, so more work might not be helpful.
* http://www.postgresql.org/message-id/CA+TgmoZOyaTanfEvNUdiHBCuu9Zh0JVP1e_UTVbx6Rvj9vFC9Q@mail.gmail.com
}}

{{TodoItem
|Consider having a larger statistics target for indexed columns and expression indexes.
}}

{{TodoItem
|Allow multiple indexes to be created concurrently, ideally via a single heap scan
|pg_restore allows parallel index builds, but it is done via subprocesses, and there is no SQL interface for this.
Cluster could definitely benefit from this.
* http://archives.postgresql.org/pgsql-performance/2011-04/msg00093.php
* http://www.postgresql.org/message-id/CADVWZZJ5AS%3DXVrDwfTQqQP_V1+_fTYcZhq%3Dd5CbCXoALCjObbg@mail.gmail.com
}}

{{TodoItem
|Consider sorting entries before inserting into btree index
* [http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php <nowiki>Re: ATTN: Clodaldo was Performance problem. Could it be related to 8.3-beta4?</nowiki>]
}}

{{TodoItem
|Consider using "effective_io_concurrency" for index scans
|Currently only bitmap scans use this, which might be fine because most multi-row index scans use bitmap scans.
* [http://www.postgresql.org/message-id/CAGTBQpZzf70n0PYJ%3DVQLd+jb3wJGo%3D2TXmY+SkJD6G_vjC5QNg@mail.gmail.com Prefetch index pages for B-Tree index scans]
}}

{{TodoItem
|Allow GIN indexes to be used for exclusion constraints
* http://archives.postgresql.org/pgsql-hackers/2012-05/msg00669.php
}}

{{TodoItem
| Allow "loose" or "skip" scans on btree indexes in which the first column has low cardinality
* http://archives.postgresql.org/pgsql-performance/2012-08/msg00159.php
}}

{{TodoItem
| Make the planner's "special index operator" mechanism extensible
* http://www.postgresql.org/message-id/27270.1364700924@sss.pgh.pa.us
}}

{{TodoItem
| Allow index-only COUNT(*) for indexes which don't support index-only scans
}}

{{TodoItem
|Improve GIN performance
* [http://www.postgresql.org/message-id/52F373CC.4050800@vmware.com Small GIN optimizations (after 9.4)]
}}

{{TodoItem
| Teach GIN cost estimation about "fast scans"
* http://www.postgresql.org/message-id/53208B4D.5000806@vmware.com
}}

{{TodoItem
| Allow unlogged indexes
* http://www.postgresql.org/message-id/11561.1414793261@sss.pgh.pa.us
}}

=== GIST ===
{{TodoSubsection}}

{{TodoItem
|Add more GIST index support for geometric data types}}

{{TodoItem
|Allow GIST indexes to create more complex index types, like digital trees (see Aoki)}}

{{TodoItem
|Fix performance issues in contrib/seg and contrib/cube GiST support
* [http://archives.postgresql.org/message-id/alpine.DEB.2.00.0904161633160.4053@aragorn.flymine.org GiST index performance]
* [http://archives.postgresql.org/message-id/alpine.DEB.2.00.0904221704470.22330@aragorn.flymine.org draft patch]
* [http://archives.postgresql.org/pgsql-performance/2009-05/msg00069.php <nowiki>Re: GiST index performance</nowiki>]
* [http://archives.postgresql.org/pgsql-performance/2009-06/msg00068.php <nowiki>GiST index performance</nowiki>]
}}

{{TodoItem
|[http://archives.postgresql.org/message-id/4DC8D284-05CF-4E3D-9670-AC9A32C37A36@justatheory.com GiST index support for arrays]
}}

{{TodoEndSubsection}}

=== Hash ===
{{TodoSubsection}}

{{TodoItem
|Add UNIQUE capability to hash indexes
* [https://www.postgresql.org/message-id/592254A5.9000809@anastigmatix.net Re: PG10 Crash-safe and replicable Hash Indexes and UNIQUE]
}}

{{TodoItem
|Allow multi-column hash indexes
* This requires all columns to be specified for a query to use the index.
* [https://www.postgresql.org/message-id/CA+Tgmoax6DhnKsuE_gzY5qkvmPEok77JAP1h8wOTbf+dg2Ycrw@mail.gmail.com Write Ahead Logging for Hash Indexes]
}}

{{TodoEndSubsection}}

== Sorting ==

{{TodoItem
|Consider whether duplicate keys should be sorted by block/offset
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00558.php <nowiki>Remove hacks for old bad qsort() implementations?</nowiki>]
}}

{{TodoItem
|Consider being smarter about memory and external files used during sorts
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg01101.php <nowiki>Sorting Improvements for 8.4</nowiki>]
}}

{{TodoItem
|Consider detoasting keys before sorting}}

{{TodoItem
|Allow sorts of skinny tuples to use even more available memory.
|Now that it is not limited by MaxAllocSize, don't limit by INT_MAX either.
* [http://www.postgresql.org/message-id/CA+U5nMKkRMin1pV8VMpS6_n7hcOWSG0kZS3oFL9JOa8DV6vJyQ@mail.gmail.com Re: MemoryContextAllocHuge(): selectively bypassing MaxAllocSize]
}}

== Cache Usage ==

{{TodoItem
|Consider automatic caching of statements at various levels:
* Parsed query tree
* Query execute plan
* Query results
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg00823.php <nowiki>Cached Query Plans (was: global prepared statements)</nowiki>]
* [https://www.postgresql.org/message-id/CAFj8pRAGLaiEm8ur5DWEBo7qHRWTk9HxkuUAz00CZZtJj-LkCA%40mail.gmail.com PoC plpgsql - possibility to force custom or generic plan]
* [https://www.postgresql.org/message-id/CADT4RqAd_74m6MUbXAPsYzqXG3F6wWVhS_dFJijrfXs7N+QGHQ@mail.gmail.com Cached/global query plans, autopreparation]
}}

{{TodoItem
|Consider allowing higher priority queries to have referenced shared buffer pages stay in memory longer
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00562.php <nowiki>Re: How to keep a table in memory?</nowiki>]
}}

{{TodoItem
|Fix memory leak caused by negative catcache entries
* [http://www.postgresql.org/message-id/51C0A1FF.2050404@vmware.com <nowiki>Re: Memory leak in PL/pgSQL function which CREATE/SELECT/DROP a temporary table</nowiki>]
}}

== Vacuum ==

{{TodoItem
|Auto-fill the free space map by scanning the buffer cache or by checking pages written by the background writer
* [http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php <nowiki>Dead Space Map</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2006-03/msg00011.php <nowiki>Re: Automatic free space map filling</nowiki>]
}}

{{TodoItem
|Allow concurrent inserts to use recently created pages rather than creating new ones
* http://archives.postgresql.org/pgsql-hackers/2010-05/msg00853.php
}}

{{TodoItem
|Consider having single-page pruning update the visibility map
* <nowiki>https://commitfest.postgresql.org/action/patch_view?id=75</nowiki>
* [http://archives.postgresql.org/pgsql-hackers/2010-02/msg02344.php <nowiki>Re: visibility maps and heap_prune</nowiki>]
}}

{{TodoItem
|Allow VACUUM FULL and CLUSTER to update the visibility map
* [http://www.postgresql.org/message-id/20130112191404.255800@gmx.com index-only scans : abnormal heap fetches after VACUUM FULL]
}}

{{TodoItem
|Improve tracking of total relation tuple counts now that vacuum doesn't always scan the whole heap
* [http://archives.postgresql.org/pgsql-hackers/2009-06/msg00531.php Partial vacuum versus pg_class.reltuples]
}}

{{TodoItem
|Bias FSM towards returning free space near the beginning of the heap file, in hopes that empty pages at the end can be truncated by VACUUM
* [http://archives.postgresql.org/pgsql-hackers/2009-09/msg01124.php <nowiki>FSM search modes</nowiki>]
* [http://www.postgresql.org/message-id/20150424190403.GP4369@alvh.no-ip.org Re: Feedback on getting rid of VACUUM FULL]
}}

{{TodoItem
|Consider a more compact data representation for dead tuple locations within VACUUM
* [http://archives.postgresql.org/pgsql-patches/2007-05/msg00143.php <nowiki>Re: Have vacuum emit a warning when it runs out of maintenance_work_mem</nowiki>]
}}

{{TodoItem
|Provide more information in order to improve user-side estimates of dead space bloat in relations
* [http://archives.postgresql.org/pgsql-general/2009-05/msg01039.php <nowiki>Re: Bloated Table</nowiki>]
}}

{{TodoItem
|Reduce the number of table scans performed by vacuum
* http://archives.postgresql.org/pgsql-hackers/2011-05/msg01119.php
* http://archives.postgresql.org/pgsql-hackers/2011-07/msg00624.php
}}

{{TodoItem
|Vacuum Gin indexes in physically order rather than logical order
* http://archives.postgresql.org/pgsql-hackers/2012-04/msg00443.php
}}

{{TodoItem
|Avoid creation of the free space map for small tables
* http://archives.postgresql.org/pgsql-hackers/2011-11/msg01751.php
}}

=== Auto-vacuum ===
{{TodoSubsection}}

{{TodoItem
|Issue log message to suggest VACUUM FULL if a table is nearly empty?
*[http://www.postgresql.org/message-id/F40B0968DB0A904DA78A924E633BE78645FAAF@SYDEXCHTMP2.au.fjanz.com discussion]
}}

{{TodoItem
|Prevent long-lived temporary tables from causing frozen-xid advancement starvation
|The problem is that autovacuum cannot vacuum them to set frozen xids; only the session that created them can.
* [http://archives.postgresql.org/pgsql-general/2007-06/msg01645.php <nowiki>Re: AutoVacuum Behaviour Question</nowiki>]
}}

{{TodoItem
|Prevent autovacuum from running if an old transaction is still running from the last vacuum
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00899.php <nowiki>Re: Autovacuum and OldestXmin</nowiki>]
}}

{{TodoItem
|Have autoanalyze of parent tables occur when child tables are modified
* http://archives.postgresql.org/pgsql-performance/2010-06/msg00137.php
}}

{{TodoItem
|Allow visibility map all-visible bits to be set even when an auto-ANALYZE is running
* http://archives.postgresql.org/pgsql-hackers/2012-01/msg00356.php
}}

{{TodoItem
|Improve autovacuum tuning
* http://www.postgresql.org/message-id/5078AD6B.8060802@agliodbs.com
* http://www.postgresql.org/message-id/20130124215715.GE4528@alvh.no-ip.org
}}

{{TodoItem
|Improve setting of visibility map bits for read-only and insert-only workloads
* http://www.postgresql.org/message-id/20130906001437.GA29264@momjian.us
}}

{{TodoEndSubsection}}

== Locking ==

{{TodoItem
|Fix problem when multiple subtransactions of the same outer transaction hold different types of locks, and one subtransaction aborts
* [http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php <nowiki>FOR SHARE vs FOR UPDATE locks</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php <nowiki>Re: FOR SHARE vs FOR UPDATE locks</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php <nowiki>Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2007-05/msg00773.php <nowiki>Re: savepoints and upgrading locks</nowiki>]
}}

{{TodoItem
|Improve deadlock detection when a page cleaning lock conflicts with a shared buffer that is pinned
* [http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php <nowiki>BUG #3883: Autovacuum deadlock with truncate?</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php <nowiki>Thoughts about bug #3883</nowiki>]
* [http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php <nowiki>Re: pgsql: Add checks to TRUNCATE, CLUSTER, and REINDEX to prevent</nowiki>]
}}

{{TodoItem
|Detect deadlocks involving LockBufferForCleanup()
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php <nowiki>Thoughts about bug #3883</nowiki>]
}}

{{TodoItem
|Allow finer control over who is cancelled in a deadlock
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg01727.php
}}

== Startup Time Improvements ==

{{TodoItem
|Allow backends to change their database without restart
|This allows for faster server startup.
* http://archives.postgresql.org/pgsql-hackers/2010-11/msg00843.php
* http://archives.postgresql.org/pgsql-hackers/2010-12/msg00336.php
}}

== Write-Ahead Log ==

{{TodoItem
|Eliminate need to write full pages to WAL before page modification
|Currently, to protect against partial disk page writes, we write full page images to WAL before they are modified so we can correct any partial page writes during recovery. These pages can also be eliminated from point-in-time archive files.
* [http://archives.postgresql.org/pgsql-hackers/2002-06/msg00655.php <nowiki>Re: Index Scans become Seq Scans after VACUUM ANALYSE</nowiki>]
* http://archives.postgresql.org/pgsql-hackers/2011-05/msg01191.php
* [http://archives.postgresql.org/message-id/20120105061916.GB21048@fetter.org WIP double writes]
* [http://archives.postgresql.org/message-id/4EFC449F02000025000441CD@gw.wicourts.gov double writes]
* [http://archives.postgresql.org/message-id/20120110214344.GB21106@fetter.org Double-write with Fast Checksums]
* [http://archives.postgresql.org/message-id/1962493974.656458.1327703514780.JavaMail.root@zimbra-prod-mbox-4.vmware.com double writes using "double-write buffer" approach]
* http://archives.postgresql.org/pgsql-hackers/2012-10/msg01463.php
}}

{{TodoItem
|When full page writes are off, write CRC to WAL and check file system blocks on recovery
|If CRC check fails during recovery, remember the page in case a later CRC for that page properly matches. The difficulty is that hint bits are not WAL logged, meaning a valid page might not match the earlier CRC.}}

{{TodoItem
|Write full pages during file system write and not when the page is modified in the buffer cache
|This allows most full page writes to happen in the background writer. It might cause problems for applying WAL on recovery into a partially-written page, but later the full page will be replaced from WAL.
* [http://archives.postgresql.org/message-id/CAGvK12UST-tPhyLrSLuSpwFxZbAO79yYrhV2xaLmS2MkUxNUVQ@mail.gmail.com Page Checksums + Double Writes]
}}

{{TodoItem
|Allow WAL information to recover corrupted pg_controldata
* [http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php <nowiki>Re: [HACKERS] pg_resetxlog -r flag</nowiki>]
}}

{{TodoItem
|Speed WAL recovery by allowing more than one page to be prefetched
|This should be done utilizing the same infrastructure used for prefetching in general to avoid introducing complex error-prone code in WAL replay.
* [http://archives.postgresql.org/pgsql-general/2007-12/msg00683.php <nowiki>Slow PITR restore</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00497.php <nowiki>Re: [GENERAL] Slow PITR restore</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php <nowiki>Read-ahead and parallelism in redo recovery</nowiki>]
}}

{{TodoItem
|Improve WAL concurrency by increasing lock granularity
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00556.php <nowiki>Reworking WAL locking</nowiki>]
}}

{{TodoItem
|Have resource managers report the duration of their status changes
* [http://archives.postgresql.org/pgsql-hackers/2007-10/msg01468.php <nowiki>Recovery of Multi-stage WAL actions</nowiki>]
}}

{{TodoItem
|Close deleted WAL files held open in *nix by long-lived read-only backends
* [http://archives.postgresql.org/pgsql-hackers/2009-11/msg01754.php <nowiki>Deleted WAL files held open by backends in Linux</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2009-12/msg00060.php <nowiki>Re: Deleted WAL files held open by backends in Linux</nowiki>]
}}

== Optimizer / Executor ==

{{TodoItem
|Improve selectivity functions for geometric operators}}

{{TodoItem
|Consider increasing the default values of from_collapse_limit, join_collapse_limit, and/or geqo_threshold
* [http://archives.postgresql.org/message-id/4136ffa0905210551u22eeb31bn5655dbe7c9a3aed5@mail.gmail.com from_collapse_limit vs. geqo_threshold]
}}

{{TodoItem
|Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
* http://archives.postgresql.org/pgsql-hackers/2012-08/msg00597.php
}}

{{TodoItem
|Log statements where the optimizer row estimates were dramatically different from the number of rows actually found?}}

{{TodoItem
|Consider compressed annealing to search for query plans
|This might replace GEQO.
* http://archives.postgresql.org/message-id/15658.1241278636%40sss.pgh.pa.us
}}

{{TodoItem
|Improve use of expression indexes for ORDER BY
* [http://archives.postgresql.org/pgsql-hackers/2009-08/msg01553.php <nowiki>Resjunk sort columns, Heikki's index-only quals patch, and bug #5000</nowiki>]
}}

{{TodoItem
|Modify the planner to better estimate caching effects
* http://archives.postgresql.org/pgsql-performance/2010-11/msg00117.php
}}

{{TodoItem
|Allow shared buffer cache contents to affect index cost computations
* http://archives.postgresql.org/pgsql-hackers/2011-06/msg01140.php
}}

=== Hashing ===
{{TodoSubsection}}

{{TodoItem
|Consider using a hash for joining to a large IN (VALUES ...) list
* [http://archives.postgresql.org/pgsql-hackers/2007-05/msg00450.php <nowiki>Planning large IN lists</nowiki>]
}}

{{TodoItem
|Allow single batch hash joins to preserve outer pathkeys
* [http://archives.postgresql.org/pgsql-hackers/2008-09/msg00806.php Re: Potential Join Performance Issue]
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]
}}

{{TodoItem
|Use "lazy" hash tables to look up only the tuples that are actually requested
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]
}}

{{TodoItem
|Avoid building the same hash table more than once during the same query
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]
}}

{{TodoItem
|Avoid hashing for distinct and then re-hashing for hash join
* [http://archives.postgresql.org/message-id/4136ffa0902191346g62081081v8607f0b92c206f0a@mail.gmail.com Re: Fixing Grittner's planner issues]
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]
}}

{{TodoEndSubsection}}

== Background Writer ==

{{TodoItem
|Consider having the background writer update the transaction status hint bits before writing out the page
|Implementing this requires the background writer to have access to system catalogs and the transaction status log.
* [http://www.postgresql.org/message-id/CAMkU%3D1zf1Yo0dYJzJ-pk9o4mwLuMD4Uzw6Jck7u1nC_Xb2gYWA@mail.gmail.com Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables]
}}

{{TodoItem
|Consider adding buffers the background writer finds reusable to the free list
* [http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php <nowiki>Background LRU Writer/free list</nowiki>]
* [http://archives.postgresql.org/message-id/CA+U5nMKtvyDcV4zTr7bq7t6cA2nBfLxCJ8tQgVBnc5ddRPO+Bg@mail.gmail.com our buffer replacement strategy is kind of lame]
* [http://www.postgresql.org/message-id/CAOeZVic4HikhmzVD%3DZP4JY9g8PgpyiQQOXOELWP%3DkR+%3DH1Frgg@mail.gmail.com Page replacement algorithm in buffer cache]
* [http://www.postgresql.org/message-id/002f01ce50a8$e057c7a0$a10756e0$@kapila@huawei.com Move unused buffers to freelist]
}}

{{TodoItem
|Automatically tune bgwriter_delay based on activity rather then using a fixed interval
* [http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php <nowiki>Background LRU Writer/free list</nowiki>]
* [http://archives.postgresql.org/message-id/CA+U5nMKtvyDcV4zTr7bq7t6cA2nBfLxCJ8tQgVBnc5ddRPO+Bg@mail.gmail.com our buffer replacement strategy is kind of lame]
}}

{{TodoItem
|Consider whether increasing BM_MAX_USAGE_COUNT improves performance
* [http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php <nowiki>Bgwriter LRU cleaning: we've been going at this all wrong</nowiki>]
}}

{{TodoItem
|Test to see if calling PreallocXlogFiles() from the background writer will help with WAL segment creation latency
* [http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php <nowiki>Re: Load Distributed Checkpoints, final patch</nowiki>]
}}

== Concurrent Use of Resources ==

{{TodoItem
|Do async I/O for faster random read-ahead of data
|Async I/O allows multiple I/O requests to be sent to the disk with results coming back asynchronously.
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php <nowiki>Asynchronous I/O Support</nowiki>]
* [http://archives.postgresql.org/pgsql-performance/2007-09/msg00255.php <nowiki>Re: random_page_costs - are defaults of 4.0 realistic for SCSI RAID 1</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00027.php <nowiki>There's random access and then there's random access</nowiki>]
* [http://archives.postgresql.org/pgsql-patches/2008-01/msg00170.php <nowiki>Bitmap index scan preread using posix_fadvise (Was: There's random access and then there's random access)</nowiki>]
The above patch is already applied as of 8.4, but it still remains to figure out how to handle plain indexscans effectively.
* [http://archives.postgresql.org//pgsql-hackers/2009-01/msg00806.php Problems with the patch submitted for posix_fadvise in index scans]
}}

{{TodoItem
|SMP scalability improvements
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00439.php <nowiki>Straightforward changes for increased SMP scalability</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2007-09/msg00206.php <nowiki>Re: Reducing Transaction Start/End Contention</nowiki>]
}}

== TOAST ==

{{TodoItem
|Allow user configuration of TOAST thresholds
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php <nowiki>Re: Proposed adjustments in MaxTupleSize and toastthresholds</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg00082.php <nowiki>pg_lzcompress strategy parameters</nowiki>]
}}

{{TodoItem
|Reduce unnecessary cases of deTOASTing
* [http://archives.postgresql.org/pgsql-hackers/2007-09/msg00895.php <nowiki>Re: [PATCHES] Eliminate more detoast copies for packed varlenas</nowiki>]
}}

{{TodoItem
|Reduce costs of repeat de-TOASTing of values
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg01096.php <nowiki>WIP patch: reducing overhead for repeat de-TOASTing</nowiki>]
}}

== Monitoring ==

{{TodoItem
|Have pg_stat_activity display query strings in the correct client encoding
* [http://archives.postgresql.org/pgsql-hackers/2009-01/msg00131.php <nowiki>pg_stats queries versus per-database encodings</nowiki>]
}}

{{TodoItem
| Allow reporting of stalls due to wal_buffer wrap-around
* http://archives.postgresql.org/pgsql-hackers/2012-02/msg00826.php
}}

{{TodoItem
| Restructure pg_stat_database columns tup_returned and tup_fetched to return meaningful values
* http://www.postgresql.org/message-id/20121012060345.GA29214@toroid.org
}}

{{TodoItem
| Improve handling of pg_stat_statements handling of bind "IN" variables
* [http://www.postgresql.org/message-id/CAM3SWZSpdPB3uErnXWMt3q74y0r+84ZsOt2U3HKKes_V7O+0Qg@mail.gmail.com Revisiting pg_stat_statements and IN()]
}}

== Miscellaneous Performance ==

{{TodoItem
|Rather than consider mmap()-ing in 8k pages, consider mmap()'ing entire files into a backend?
|Doing I/O to large tables would consume a lot of address space or require frequent mapping/unmapping. Extending the file also causes mapping problems that might require mapping only individual pages, leading to thousands of mappings. Another problem is that there is no way to _prevent_ I/O to disk from the dirty shared buffers so changes could hit disk before WAL is written.
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg01239.php
}}

{{TodoItem
|Allow configuration of backend priorities via the operating system
|Though backend priorities make priority inversion during lock waits possible, research shows that this is not a huge problem.
* [http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php <nowiki>Priorities for users or queries?</nowiki>]
}}

{{TodoItem
|Consider if CommandCounterIncrement() can avoid its AcceptInvalidationMessages() call
* [http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php <nowiki>pgsql: Avoid incrementing the CommandCounter when</nowiki>]
}}

{{TodoItem
|Consider Cartesian joins when both relations are needed to form an indexscan qualification for a third relation
* [http://archives.postgresql.org/pgsql-performance/2007-12/msg00090.php <nowiki>Re: TB-sized databases</nowiki>]
}}

{{TodoItem
|Consider not storing a NULL bitmap on disk if all the NULLs are trailing
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00624.php <nowiki>Proposal for Null Bitmap Optimization(for Trailing NULLs)</nowiki>]
* [http://archives.postgresql.org/pgsql-patches/2007-12/msg00109.php <nowiki>Re: [HACKERS] Proposal for Null Bitmap Optimization(for TrailingNULLs)</nowiki>]
}}

{{TodoItem
|Sort large UPDATE/DELETEs so it is done in heap order
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg01119.php <nowiki>Possible future performance improvement: sort updates/deletes by ctid</nowiki>]
}}

{{TodoItem
|Add auto-tuning of work_mem
* [http://www.postgresql.org/message-id/20131009143046.GT22450@momjian.us Auto-tuning work_mem and maintenance_work_mem]
}}

{{TodoItem
|Consider decreasing the I/O caused by updating tuple hint bits
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00847.php <nowiki>Hint Bits and Write I/O</nowiki>]
* [http://archives.postgresql.org/pgsql-patches/2008-07/msg00199.php <nowiki>Re: [HACKERS] Hint Bits and Write I/O</nowiki>]
* http://archives.postgresql.org/pgsql-hackers/2010-10/msg00695.php
* http://archives.postgresql.org/pgsql-hackers/2010-11/msg00792.php
* http://archives.postgresql.org/pgsql-hackers/2011-01/msg01063.php
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg01408.php
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg01453.php
}}

{{TodoItem
|Avoid reading in b-tree pages when replaying vacuum records in hot standby mode
* [http://archives.postgresql.org/message-id/1272571938.4161.14739.camel@ebony <nowiki>Hot Standby tuning for btree_xlog_vacuum()</nowiki>]
}}

{{TodoItem
|Restructure truncation logic to be more resistant to failure
|This also involves not writing dirty buffers for a truncated or dropped relation
* http://archives.postgresql.org/pgsql-hackers/2010-08/msg01032.php
}}

{{TodoItem
|Enhance foreign data wrappers, parallelism, partitioning, and perhaps add a global snapshot/transaction manager to allow creation of a proof-of-concept built-in sharding solution
|Ideally these enhancements and new facilities will be available to external sharding solutions as well.
* [https://wiki.postgresql.org/wiki/Built-in_Sharding Built-in sharding wiki]
}}

== Miscellaneous Other ==

{{TodoItem
|Deal with encoding issues for filenames in the server filesystem
* {{MessageLink|20090413184335.39BE.52131E4D@oss.ntt.co.jp|a proposed patch here}}
* {{MessageLink|8484.1244655656@sss.pgh.pa.us|some issues about it here}}
* {{MessageLink|20100107103740.97A5.52131E4D@oss.ntt.co.jp|Windows-specific patch here}}
}}

{{TodoItem
|Deal with encoding issues in the output of localeconv()
* [http://archives.postgresql.org/message-id/40c6d9160904210658y590377cfw6dbbecb53d2b8be0@mail.gmail.com bug report]
* [http://archives.postgresql.org/message-id/49EF8DA0.90008@tpf.co.jp draft patch]
* [http://archives.postgresql.org/message-id/21710.1243620986@sss.pgh.pa.us review of patch]
}}

{{TodoItem
|Have GB18030 handle more than 2-byte Unicode code points
* [http://www.postgresql.org/message-id/20150309205145.4031.32069@wrigleys.postgresql.org GB18030 encoding doesn't support Unicode characters over 0xFFFF]
}}

{{TodoItem
|Provide schema name and other fields available from SQL GET DIAGNOSTICS in error reports
* [http://archives.postgresql.org/message-id/dcc563d10810211907n3c59a920ia9eb7cd2a6d5ea58@mail.gmail.com <nowiki>How to get schema name which violates fk constraint</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2009-11/msg00846.php <nowiki>patch - Report the schema along table name in a referential failure error message</nowiki>]
* {{MessageLink|3191.1263306359@sss.pgh.pa.us|Re: NOT NULL violation and error-message}}
* [http://archives.postgresql.org/pgsql-hackers/2009-08/msg00213.php <nowiki>the case for machine-readable error fields</nowiki>]
}}

{{TodoItem
|Use sa_mask to close race conditions between signal handlers
* http://www.postgresql.org/message-id/20130911013107.GA225735@tornado.leadboat.com
}}

{{TodoItem
|Allow pg_export_snapshot() to run on hot standby servers
|This will allow parallel pg_dump on such servers.
* [http://www.postgresql.org/message-id/CA+U5nML2VMJ3R2YBAZ+CsAsTWF3LuYSo16Wu9+yXFrfy4%3Df2fA@mail.gmail.com pg_export_snapshot on standby side]
}}

{{TodoItem
|Provide a way to enumerate and unregister background workers
|Right now the only way to unregister bgworkers is from within the worker with <tt>proc_exit(0)</tt> or registering with <tt>BGW_NEVER_RESTART</tt>
* https://www.postgresql.org/message-id/CAMsr%2BYG-fD%2BmP-BNZDheVYucC7%3DoUn8ByTQSFz7RKkVX2MRS2Q%40mail.gmail.com
}}

== Source Code ==

{{TodoItem
|Allow cross-compiling by generating the zic database on the target system}}

{{TodoItem
|Improve NLS maintenance of libpgport messages linked onto applications}}

{{TodoItem
|Use UTF8 encoding for NLS messages so all server encodings can read them properly}}

{{TodoItem
|Allow creation of universal binaries for Darwin
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg00884.php <nowiki>Getting to universal binaries for Darwin</nowiki>]
}}

{{TodoItem
|Consider GnuTLS if OpenSSL license becomes a problem
* http://archives.postgresql.org/pgsql-hackers/2011-02/msg00892.php
* [http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php <nowiki>[PATCH] Add support for GnuTLS</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php <nowiki>TODO: GNU TLS</nowiki>]
}}

{{TodoItem
|Consider making NAMEDATALEN more configurable}}

{{TodoItem
|Research use of signals and sleep wake ups
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00003.php <nowiki>Restartable signals 'n all that</nowiki>]
}}

{{TodoItem
|Consider simplifying how memory context resets handle child contexts
* [http://archives.postgresql.org/pgsql-patches/2007-08/msg00067.php <nowiki>Re: Memory leak in nodeAgg</nowiki>]
}}

{{TodoItem
|Implement the non-threaded Avahi service discovery protocol
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00939.php <nowiki>Re: [PATCHES] Avahi support for Postgresql</nowiki>]
* [http://archives.postgresql.org/pgsql-patches/2008-02/msg00097.php <nowiki>Re: Avahi support for Postgresql</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg01211.php <nowiki>Re: [PATCHES] Avahi support for Postgresql</nowiki>]
* [http://archives.postgresql.org/pgsql-patches/2008-04/msg00001.php <nowiki>Re: [HACKERS] Avahi support for Postgresql</nowiki>]
}}

{{TodoItem
|Reduce data row alignment requirements on some 64-bit systems
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg00369.php <nowiki>[WIP] Reduce alignment requirements on 64-bit systems.</nowiki>]
}}

{{TodoItem
|Restructure TOAST internal storage format for greater flexibility
* [http://archives.postgresql.org/pgsql-hackers/2008-11/msg00049.php <nowiki>Re: PG_PAGE_LAYOUT_VERSION 5 - time for change</nowiki>]
}}

{{TodoItem
| Consider removing the attribute options cache
* http://archives.postgresql.org/pgsql-hackers/2011-03/msg00039.php
}}

{{TodoItem
| Restructure /contrib section
* http://archives.postgresql.org/pgsql-hackers/2011-06/msg00705.php
}}

=== Windows ===
{{TodoSubsection}}

{{TodoItem
|Remove configure.in check for link failure when the cause is found}}

{{TodoItem
|Allow psql to use readline once non-US code pages work with backslashes}}

{{TodoItem
|Improve signal handling
* [http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php <nowiki>Simplify Win32 Signaling code</nowiki>]
}}

{{TodoItem
|Support PGXS when using MSVC}}

{{TodoItem
|Fix MSVC NLS support, like for to_char()
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00485.php <nowiki>NLS on MSVC strikes back!</nowiki>]
* [http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php <nowiki>Fix for 8.3 MSVC locale (Was [HACKERS] NLS on MSVC strikes back!)</nowiki>]
}}

{{TodoItem
|Fix global namespace issues when using multiple terminal server sessions
* [http://archives.postgresql.org/message-id/48F3BFCC.8030107@dunslane.net problems with Windows global namespace]}}

{{TodoItem
|Change from the current autoconf/gmake build system to cmake
* [http://archives.postgresql.org/pgsql-hackers/2008-12/msg01869.php <nowiki>About CMake (was Re: [COMMITTERS] pgsql: Append major version number and for libraries soname major)</nowiki>]
}}

{{TodoItem
|Improve consistency of path separator usage
* http://archives.postgresql.org/message-id/49C0BDC5.4010002@hagander.net
}}

{{TodoItem
|Fix cross-compiling on Windows
* http://archives.postgresql.org/pgsql-bugs/2010-10/msg00110.php
}}

{{TodoItem
|Reduce file statistics overhead on directory reads
* http://www.postgresql.org/message-id/1338325561.82125.YahooMailNeo@web39304.mail.mud.yahoo.com
}}

{{TodoItem
|Fix hang with long file paths
* [http://www.postgresql.org/message-id/CAA4eK1JxaBofxpcgLqCx9EB%3Dm3PaXr9iFU9%3DV3ddDswsPZooxw@mail.gmail.com Long paths for tablespace leads to uninterruptible hang in Windows]
}}

{{TodoEndSubsection}}

=== Wire Protocol Changes / v4 Protocol ===
{{TodoSubsection}}

{{TodoItem
|Allow dynamic character set handling}}

{{TodoItem
|Ensure the client can determine the encoding of messages sent early in the handshake
* http://www.postgresql.org/message-id/541A5659.5050006@2ndquadrant.com}}

{{TodoItem
|Let the client indicate character encoding of database names, user names, passwords, and of pre-auth error messages returned by the server
* http://www.postgresql.org/message-id/16160.1360540050@sss.pgh.pa.us
* http://www.postgresql.org/message-id/20131220030725.GA1411150@tornado.leadboat.com
}}

{{TodoItem
|Send numeric version to clients in fixed header
* [https://commitfest.postgresql.org/10/752/ <nowiki>patch to send server_version_num in v3 protocol as GUC_REPORT</nowiki>]
}}

{{TodoItem
|Add decoded type length/precision (i.e. typmod information)}}

{{TodoItem
|Mark result columns as known-not-null when possible
* [http://archives.postgresql.org/pgsql-hackers/2010-11/msg01029.php <nowiki>Adding nullable indicator to Describe</nowiki>]
}}

{{TodoItem
|Use compression
|Specify and implement wire protocol compression. If SSL transparent compression is used, hopefully avoid the overhead of key negotiation and encryption when SSL is configured only for compression. Note that [https://www.ietf.org/mail-archive/web/tls/current/msg11619.html compression is being removed from TLS 1.3] so we really need to do it ourselves.
* http://archives.postgresql.org/pgsql-hackers/2012-06/msg00793.php
}}

{{TodoItem
|Update clients to use data types, typmod, schema.table.column names of result sets using new statement protocol}}

{{TodoItem
|Set protocol for wire format negotiation
* [http://archives.postgresql.org/message-id/CACMqXCKkGrGXxQhjHCKCe0B8hn6sTt-1sdgHZOSGQMxrusOsQA@mail.gmail.com GUC_REPORT for protocol tunables]
}}

{{TodoItem
|Make sure upgrading to a 4.1 protocol version will actually work smoothly
* [http://archives.postgresql.org/message-id/28307.1318255008@sss.pgh.pa.us Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable]
}}

{{TodoItem
|Allow multi-state authentication (e.g. try client peer, fall back to md5)
* http://www.postgresql.org/message-id/51A44185.5060306@2ndquadrant.com
* http://www.postgresql.org/message-id/55192AFE.6080106@iki.fi
* http://www.postgresql.org/message-id/54DB1D4E.8090700@vmware.com
* https://commitfest.postgresql.org/6/320/
}}

{{TodoItem
|Allow re-authentication
|Let the client request re-authentication as a different user mid session, for connection pools that pass through the handshake.
}}

{{TodoItem
|Identify the affected object in CommandComplete message?
* http://www.postgresql.org/message-id/CAAfz9KNGVoyM+z_2tnPKTDXG_RdR9a33Y5s+zQ9LdwTTsqqZng@mail.gmail.com
}}

{{TodoItem
|Allow negotiation of encryption, <tt>STARTTLS</tt> style, rather than forcing client to decide on SSL or !SSL before connecting
* http://www.postgresql.org/message-id/5406EAD3.7070002@2ndquadrant.com}}

{{TodoItem
|Permit lazy fetches of large values, at least out-of-line TOASTED values
* http://www.postgresql.org/message-id/53FF0EF8.100@2ndquadrant.com
}}

{{TodoItem
|Add session-level whitelisting of types for binary-mode transfer
* http://www.postgresql.org/message-id/30470.1412055068@sss.pgh.pa.us
}}

{{TodoItem
|Send client the xid when it is allocated
|Lets the client later ask the server "did this commit or not?" after interterminate result due to crash or connection loss
}}

{{TodoItem
|Report xlog position in commit message
|Help enable client-side failover by providing a token clients can use to see if a commit has replayed to replicas yet
* http://www.postgresql.org/message-id/53E2D346.9030806@2ndquadrant.com
}}

{{TodoItem
|Changes to make cancellations more reliable and more secure
* http://www.postgresql.org/message-id/CADT4RqAUd7wYYsM9D7GHJnZj3J79D4W%3Dved2kqM5mVt5cuGHgg@mail.gmail.com
}}

{{TodoItem
|Clarify semantics of statement_timeout in extended query protocol
|Batched and pipelined queries have unexpected behaviour with statement_timeout. Client needs to be able to specify statement boundary with protocol message.
* https://www.postgresql.org/message-id/20160528.220442.1489791680347556026.t-ishii@sraoss.co.jp
}}

{{TodoItem
|Create a more efficient way to handle out-of-line parameters
* [https://www.postgresql.org/message-id/12500.1470002232%40sss.pgh.pa.us Re: Slowness of extended protocol]
}}

{{TodoItem
|Separate transaction delineation from protocol error recovery (in v3 both are managed via the same Sync message)
* https://www.postgresql.org/message-id/CADT4RqDdo9EcFbxwB_YO2H3BVZ0t-1qqZ%3D%2B%2BdVMnYaN6BpyUGQ%40mail.gmail.com
* https://www.postgresql.org/message-id/CAMsr%2BYEgnJ8ZAWPLx5%3DBCbYYq9SNTdwbwvUcb7V-vYm5d5uhbQ%40mail.gmail.com
}}

{{TodoEndSubsection}}

== Documentation ==

{{TodoItem
|Provide a manpage for postgresql.conf
* {{messageLink|20080819194311.GH4428@alvh.no-ip.org|A smaller default postgresql.conf}}
* {{messageLink|200808211910.37524.peter_e@gmx.net|A smaller default postgresql.conf}}
}}

{{TodoItem
|Document support for N<nowiki>' '</nowiki> national character string literals, if it matches the SQL standard
* http://archives.postgresql.org/message-id/1275895438.1849.1.camel@fsopti579.F-Secure.com
}}

== Exotic Features ==

{{TodoItem
|Add pre-parsing phase that converts non-ISO syntax to supported syntax
|This could allow SQL written for other databases to run without modification.}}

{{TodoItem
|Allow plug-in modules to emulate features from other databases}}

{{TodoItem
|Add features of Oracle-style packages
|A package would be a schema with session-local variables, public/private functions, and initialization functions. It is also possible to implement these capabilities in any schema and not use a separate "packages" syntax at all.
* [http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php <nowiki>proposal for PL packages for 8.3.</nowiki>]
* [http://www.postgresql.org/message-id/CAFj8pRD4OAXp2zp7dBRg5eo6X3rtT5MHTMVRN1e1kdK8xE6E4g@mail.gmail.com proposal: schema PL session variables]
* [https://www.postgresql.org/message-id/CAFj8pRCfdTLeJbTSbAFOwhuS-aWaJ61w59XwKLcVYQFAVwfVCw%40mail.gmail.com proposal: session server side variables]
* [https://www.postgresql.org/message-id/81060c9d-73df-2266-8857-d584164bb699%40commandprompt.com Packages: Again]
}}

{{TodoItem
|Consider allowing control of upper/lower case folding of unquoted identifiers
* [http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php <nowiki>Bringing PostgreSQL torwards the standard regarding case folding</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php <nowiki>Re: [SQL] Case Preservation disregarding case sensitivity?</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00849.php <nowiki>TODO Item: Consider allowing control of upper/lower case folding of unquoted, identifiers</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg00415.php <nowiki>Identifier case folding notes</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg00415.php <nowiki>Identifier case folding notes</nowiki>]
* [https://www.postgresql.org/message-id/ACF85C502E55A143AB9F4ECFE960660A17282D@mailserver2.local.mstarlabs.com Cluster wide option to control symbol case folding]
}}

{{TodoItem
|Add autonomous transactions
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php <nowiki>autonomous transactions</nowiki>]
}}

{{TodoItem
|Give query progress indication
* [[Query progress indication]]
}}

{{TodoItem
|Rethink our type system
* [[Rethinking datatypes]]
}}

== Features We Do ''Not'' Want ==

The following features have been discussed ad nauseum on the PostgreSQL mailing lists and the consensus has been that the project is not interested in them. As such, if you are going to bring them up as potential features, you will want to be familiar with all of the arguments against these features which have been previously made over the years. If you decide to work on such features anyway, you should be aware that you face a higher-than-normal barrier to get the Project to accept them.

{{TodoItem
|All backends running as threads in a single process (not wanted)
|This eliminates the process protection we get from the current setup. Thread creation is usually the same overhead as process creation on modern systems, so it seems unwise to use a pure threaded model, and MySQL and DB2 have demonstrated that threads introduce as many issues as they solve. Threading specific operations such as I/O, seq scans, and connection management has been discussed and will probably be implemented to enable specific performance features. Moving to a threaded engine would also require halting all other work on PostgreSQL for one to two years.
* [https://www.postgresql.org/message-id/942824238.20160712165757@bitec.ru One process per session lack of sharing]
}}

{{TodoItem
|"Oracle-style" optimizer hints (not wanted)
|Optimizer hints, as implemented in Oracle and other RDBMSes, are used to work around problems in the optimizer and introduce upgrade and maintenance issues. We would rather have such problems reported and fixed. We have discussed a more sophisticated system of per-class cost adjustment instead, but a specification remains to be developed. See [[OptimizerHintsDiscussion|Optimizer Hints Discussion]] for further information.}}

{{TodoItem
|Embedded server (not wanted)
|While PostgreSQL clients runs fine in limited-resource environments, the server requires multiple processes and a stable pool of resources to run reliably and efficiently. Stripping down the PostgreSQL server to run in the same process address space as the client application would add too much complexity and failure cases. Besides, there are several very mature embedded SQL databases already available.}}

{{TodoItem
|Obfuscated function source code (not wanted)
|Obfuscating function source code has minimal protective benefits because anyone with super-user access can find a way to view the code. At the same time, it would greatly complicate backups and other administrative tasks. To prevent non-super-users from viewing function source code, remove SELECT permission on pg_proc.
* [http://archives.postgresql.org/pgsql-general/2008-09/msg00668.php <nowiki>Obfuscated stored procedures (was Re: Oracle and Postgresql)</nowiki>]
}}

{{TodoItem
|Indeterminate behavior for the GROUP BY clause (not wanted)
|At least one other database product allows specification of a subset of the result columns which GROUP BY would need to be able to provide predictable results; the server is free to return any value from the group. This is not viewed as a desirable feature. PostgreSQL 9.1 allows result columns that are not referenced by GROUP BY if a primary key for the same table is referenced in GROUP BY.
* [http://archives.postgresql.org/pgsql-hackers/2010-03/msg00297.php <nowiki>Re: SQL compatibility reminder: MySQL vs PostgreSQL</nowiki>]
}}

{{TodoItem
|On-disk bitmap indexes (not wanted)
|The rigidity of on-disk bitmap indexes, and the existence of GIN and in-memory bitmaps make this undesirable.
* [http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php <nowiki>Re: Bitmap index AM</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php <nowiki>Bitmap index thoughts</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg00265.php <nowiki>Stream bitmaps</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01214.php <nowiki>Re: Bitmapscan changes - Requesting further feedback</nowiki>]
* [http://archives.postgresql.org/pgsql-patches/2007-05/msg00013.php <nowiki>Updated bitmap index patch</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00741.php <nowiki>Reviewing new index types (was Re: [PATCHES] Updated bitmap indexpatch)</nowiki>]
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01023.php <nowiki>Bitmap Indexes: request for feedback</nowiki>]
* [http://archives.postgresql.org/message-id/800923.27831.qm@web29010.mail.ird.yahoo.com <nowiki>bitmap indexes - performance</nowiki>]
* [http://www.postgresql.org/message-id/20130914181424.GA24448@toroid.org <nowiki>[PATCH] bitmap indexes</nowiki>]
}}

[[Category:Todo]]

Corruption

2019-12-15T17:57:29Z

Dfetter: /* Detecting corruption */

== VITALLY IMPORTANT FIRST RESPONSE ==

Do you think you have one of those rare but nasty index or table corruption problems?

Before doing ''anything'' else:

'''Stop the postmaster and take a file system level copy of your database NOW!'''. Don't use pg_dump, instead make a copy of all the files in the data directory (the one that contains the "base", "pg_xlog", "pg_clog" etc folders).

If possible, put a copy of it on an external hard drive, DVD, or other storage you can disconnect from your computer so you don't accidentally modify your snapshot after making it.

People often destroy potentially recoverable data by trying to repair it. Make a file-system-level copy of your database before attempting any repair. It might save your data.

The experimental hex editor toolkit [https://github.com/petergeoghegan/pg_hexedit pg_hexedit] can be used for low-level analysis of PostgreSQL relation files. It should only be run against a copy of the database.

Your backup copy is also important evidence that may help figure out what caused the problem, allowing you to prevent it from happening again. Repair efforts usually destroy that evidence. Having the damaged data may be the only way to figure out why it was damaged and how to prevent the same thing happening again.

== Detecting corruption ==

As of PostgreSQL 10, there is am [https://www.postgresql.org/docs/10/static/amcheck.html extension called amcheck]. Although it only verifies the integrity of B-Tree indexes, it is reasonably well suited for use as a general purpose corruption smoke test, especially because the indexes can be verified against the heap with the "heapallindexed" verification option (later versions only). Note that there is also a [https://github.com/petergeoghegan/amcheck version on Github that targets earlier PostgreSQL versions].

PostgreSQL 9.6 introduced a [https://www.postgresql.org/docs/9.6/static/pgvisibility.html more specialized tool for verifying the integrity of the visibility map, called pg_visibility]. This may be of interest in cases where visibility map corruption is suspected specifically.

== Causes ==

Remember that most corruption is caused by hardware issues:

* RAID controllers with faulty / worn out battery backup, and an unexpected power loss
* Hard disk drives with write-back cache enabled, and an unexpected power loss
* Cheap SSDs with insufficient power-loss protection, and an unexpected power-loss
* Defective RAM
* Defective or overheating CPU(s)

Other causes can be:

* Database systems configured with <tt>fsync=off</tt> and an OS crash or power loss
* Filesystems configured to use write barriers plus a storage layer that ignores write barriers. [http://serverfault.com/questions/279571/lvm-dangers-and-caveats LVM was a particular culprit] but [https://bugzilla.kernel.org/show_bug.cgi?id=9554 full barrier support was added by Liunx 2.6.33-rc1].
* PostgreSQL bugs
* Operating system bugs
* Admin error
** directly modifying Postgres data-directory contents
** faulty fail-over procedures like <tt>rsync</tt>'ing without <tt>pg_start_backup</tt>
** [http://blog.ringerc.id.au/2012/10/avoiding-postgresql-database-corruption.html and lots more]

== What next? ==

Consider contacting a [https://www.postgresql.org/support/professional_support/ professional support service provider]. Corruption issues can be time consuming and difficult to diagnose and fix, and are often hardware- or configuration-specific.

Read the [[guide to reporting problems|Guide_to_reporting_problems]] and post to the pgsql-general mailing list with information about the problem. Remember that your hardware settings and postgresql configuration are vital information, as are any error messages, your Pg version, etc.

[http://thebuild.com/presentations/worst-day-fosdem-2014.pdf Christophe Pettus's FOSDEM presentation on database corruption] is also well worth a read, but you don't get the spoken warnings that come with it. In particular, the recovery techniques described there are for recovering what you can from a DB, with the understanding that you'll have missing chunks of data, inconsistent FK relationships, reappearing deleted rows / visible uncommitted rows, and all sorts of problems depending on the repair technique used. It assumes you've already done the sensible initial investigation and fixed any less serious problems that might be causing your issue.

[[Category:Administration]]

Python

2019-12-02T22:06:13Z

Dfetter:

There are several Python drivers for PostgreSQL. This is the incomplete feature matrix for them; please help complete it as you see fit.

In general, Python users want to use psycopg2 unless they have a strong reason to try another driver, most of which are no longer maintained. Since DBAPI allows drivers to have different semantics, porting applications from one driver to another is non-trivial.

{| class="wikitable" border="1"
!Software
!License
!Platforms
!Python versions
!DB API 2.0
!Native (uses libpq)
!Last Release
!Notes
|-
|[[Psycopg2]]
|LGPL
|Unix, Win32
|2.6-3.6
|yes
|yes
|2019
|Most popular python driver, required for most Python+Postgres frameworks
|-
|[https://pypi.python.org/pypi/pg8000 pg8000]
|BSD
|any (pure Python)
|3.3+
|yes
|no
|2019
|Used by Web2Py. [https://github.com/tlocke/pg8000 current updated official site]
|-
|[https://github.com/python-postgres/fe py-postgresql]
|BSD
|any (pure Python)
|3.0+
|yes
|no
|2018
|Pure Python with optional C accelerator modules,<br\>extensive custom API. Python 3 only.
|-
|[http://www.pygresql.org/ PyGreSQL]
|BSD
|Unix, Win32
|2.6 thru 3.6
|yes
|yes
|2017
|The first PostgreSQL adapter for Python. Still actively maintained.
|-
|[http://code.google.com/p/ocpgdb/ ocpgdb]
|BSD
|Unix
|2.3-2.6
|yes
|yes
|2010
|PG8.1+
|-
|[http://barryp.org/software/bpgsql/ bpgsql ]
|LGPL
|any (pure Python)
|2.3-2.6
|yes
|no
|2009
|labeled alpha
|-
|[https://aiopg.readthedocs.io/en/stable/ aiopg]
|BSD
|any
|3.52+
|(ish)
|Native
|2019
|}

More abandoned driver projects:

* [http://jamwt.com/pgasync/ pgasync], Twisted-native driver, no updates since 2005
* [http://sourceforge.net/projects/popy/ PoPy], no updates since 2003 - [https://github.com/Cito/PyGreSQL/commit/678cadfd2627b8821933ac8809ebafb15274882c development was merged with pygresql]
* [http://pypgsql.sourceforge.net/ pyPgSQL], no updates since 2006

There is [http://wiki.python.org/moin/PostgreSQL similar page on the Python wiki]

[[Python PostgreSQL Driver TODO]]

[[Category:Python]]

Python

2019-12-02T21:58:59Z

Dfetter:

There are several Python drivers for PostgreSQL. This is the incomplete feature matrix for them; please help complete it as you see fit.

In general, Python users want to use psycopg2 unless they have a strong reason to try another driver, most of which are no longer maintained. Since DBAPI allows drivers to have different semantics, porting applications from one driver to another is non-trivial.

{| class="wikitable" border="1"
!Software
!License
!Platforms
!Python versions
!DB API 2.0
!Native (uses libpq)
!Last Release
!Notes
|-
|[[Psycopg2]]
|LGPL
|Unix, Win32
|2.6-3.6
|yes
|yes
|2019
|Most popular python driver, required for most Python+Postgres frameworks
|-
|[https://pypi.python.org/pypi/pg8000 pg8000]
|BSD
|any (pure Python)
|3.3+
|yes
|no
|2019
|Used by Web2Py. [https://github.com/tlocke/pg8000 current updated official site]
|-
|[https://github.com/python-postgres/fe py-postgresql]
|BSD
|any (pure Python)
|3.0+
|yes
|no
|2018
|Pure Python with optional C accelerator modules,<br\>extensive custom API. Python 3 only.
|-
|[http://www.pygresql.org/ PyGreSQL]
|BSD
|Unix, Win32
|2.6 thru 3.6
|yes
|yes
|2017
|The first PostgreSQL adapter for Python. Still actively maintained.
|-
|[http://code.google.com/p/ocpgdb/ ocpgdb]
|BSD
|Unix
|2.3-2.6
|yes
|yes
|2010
|PG8.1+
|-
|[http://barryp.org/software/bpgsql/ bpgsql ]
|LGPL
|any (pure Python)
|2.3-2.6
|yes
|no
|2009
|labeled alpha
|-
|[https://aiopg.readthedocs.io/en/stable/ aiopg]
|BSD
|any
|(ish)
|Native
|2019
|}

More abandoned driver projects:

* [http://jamwt.com/pgasync/ pgasync], Twisted-native driver, no updates since 2005
* [http://sourceforge.net/projects/popy/ PoPy], no updates since 2003 - [https://github.com/Cito/PyGreSQL/commit/678cadfd2627b8821933ac8809ebafb15274882c development was merged with pygresql]
* [http://pypgsql.sourceforge.net/ pyPgSQL], no updates since 2006

There is [http://wiki.python.org/moin/PostgreSQL similar page on the Python wiki]

[[Python PostgreSQL Driver TODO]]

[[Category:Python]]

Python

2019-12-02T21:58:17Z

Dfetter:

There are several Python drivers for PostgreSQL. This is the incomplete feature matrix for them; please help complete it as you see fit.

In general, Python users want to use psycopg2 unless they have a strong reason to try another driver, most of which are no longer maintained. Since DBAPI allows drivers to have different semantics, porting applications from one driver to another is non-trivial.

{| class="wikitable" border="1"
!Software
!License
!Platforms
!Python versions
!DB API 2.0
!Native (uses libpq)
!Last Release
!Notes
|-
|[[Psycopg2]]
|LGPL
|Unix, Win32
|2.6-3.6
|yes
|yes
|2019
|Most popular python driver, required for most Python+Postgres frameworks
|-
|[https://pypi.python.org/pypi/pg8000 pg8000]
|BSD
|any (pure Python)
|3.3+
|yes
|no
|2019
|Used by Web2Py. [https://github.com/tlocke/pg8000 current updated official site]
|-
|[https://github.com/python-postgres/fe py-postgresql]
|BSD
|any (pure Python)
|3.0+
|yes
|no
|2018
|Pure Python with optional C accelerator modules,<br\>extensive custom API. Python 3 only.
|-
|[http://www.pygresql.org/ PyGreSQL]
|BSD
|Unix, Win32
|2.6 thru 3.6
|yes
|yes
|2017
|The first PostgreSQL adapter for Python. Still actively maintained.
|-
|[http://code.google.com/p/ocpgdb/ ocpgdb]
|BSD
|Unix
|2.3-2.6
|yes
|yes
|2010
|PG8.1+
|-
|[http://barryp.org/software/bpgsql/ bpgsql ]
|LGPL
|any (pure Python)
|2.3-2.6
|yes
|no
|2009
|labeled alpha
|-
|[https://aiopg.readthedocs.io/en/stable/ aiopg]
|BSD
|any
|-ish
|Native
|2019
|}

More abandoned driver projects:

* [http://jamwt.com/pgasync/ pgasync], Twisted-native driver, no updates since 2005
* [http://sourceforge.net/projects/popy/ PoPy], no updates since 2003 - [https://github.com/Cito/PyGreSQL/commit/678cadfd2627b8821933ac8809ebafb15274882c development was merged with pygresql]
* [http://pypgsql.sourceforge.net/ pyPgSQL], no updates since 2006

There is [http://wiki.python.org/moin/PostgreSQL similar page on the Python wiki]

[[Python PostgreSQL Driver TODO]]

[[Category:Python]]

Python

2019-12-02T21:47:07Z

Dfetter:

There are several Python drivers for PostgreSQL. This is the incomplete feature matrix for them; please help complete it as you see fit.

In general, Python users want to use psycopg2 unless they have a strong reason to try another driver, most of which are no longer maintained. Since DBAPI allows drivers to have different semantics, porting applications from one driver to another is non-trivial.

{| class="wikitable" border="1"
!Software
!License
!Platforms
!Python versions
!DB API 2.0
!Native (uses libpq)
!Last Release
!Notes
|-
|[[Psycopg2]]
|LGPL
|Unix, Win32
|2.6-3.6
|yes
|yes
|2019
|Most popular python driver, required for most Python+Postgres frameworks
|-
|[https://pypi.python.org/pypi/pg8000 pg8000]
|BSD
|any (pure Python)
|3.3+
|yes
|no
|2019
|Used by Web2Py. [https://github.com/tlocke/pg8000 current updated official site]
|-
|[https://github.com/python-postgres/fe py-postgresql]
|BSD
|any (pure Python)
|3.0+
|yes
|no
|2018
|Pure Python with optional C accelerator modules,<br\>extensive custom API. Python 3 only.
|-
|[http://www.pygresql.org/ PyGreSQL]
|BSD
|Unix, Win32
|2.6 thru 3.6
|yes
|yes
|2017
|The first PostgreSQL adapter for Python. Still actively maintained.
|-
|[http://code.google.com/p/ocpgdb/ ocpgdb]
|BSD
|Unix
|2.3-2.6
|yes
|yes
|2010
|PG8.1+
|-
|[http://barryp.org/software/bpgsql/ bpgsql ]
|LGPL
|any (pure Python)
|2.3-2.6
|yes
|no
|2009
|labeled alpha
|}

More abandoned driver projects:

* [http://jamwt.com/pgasync/ pgasync], Twisted-native driver, no updates since 2005
* [http://sourceforge.net/projects/popy/ PoPy], no updates since 2003 - [https://github.com/Cito/PyGreSQL/commit/678cadfd2627b8821933ac8809ebafb15274882c development was merged with pygresql]
* [http://pypgsql.sourceforge.net/ pyPgSQL], no updates since 2006

There is [http://wiki.python.org/moin/PostgreSQL similar page on the Python wiki]

[[Python PostgreSQL Driver TODO]]

[[Category:Python]]

Python

2019-12-02T21:46:24Z

Dfetter:

There are several Python drivers for PostgreSQL. This is the incomplete feature matrix for them; please help complete it as you see fit.

In general, Python users want to use psycopg2 unless they have a strong reason to try another driver, most of which are no longer maintained. Since DBAPI allows drivers to have different semantics, porting applications from one driver to another is non-trivial.

{| class="wikitable" border="1"
!Software
!License
!Platforms
!Python versions
!DB API 2.0
!Native (uses libpq)
!Last Release
!Notes
|-
|[[Psycopg2]]
|LGPL
|Unix, Win32
|2.6-3.6
|yes
|yes
|2019
|Most popular python driver, required for most Python+Postgres frameworks
|-
|[https://pypi.python.org/pypi/pg8000 pg8000]
|BSD
|any (pure Python)
|3.3+
|yes
|no
|2019
|Used by Web2Py. [https://github.com/tlocke/pg8000 current updated official site]
|-
|[https://github.com/python-postgres/fe py-postgresql]
|BSD
|any (pure Python)
|3.0+
|yes
|no
|2016
|Pure Python with optional C accelerator modules,<br\>extensive custom API. Python 3 only.
|-
|[http://www.pygresql.org/ PyGreSQL]
|BSD
|Unix, Win32
|2.6 thru 3.6
|yes
|yes
|2017
|The first PostgreSQL adapter for Python. Still actively maintained.
|-
|[http://code.google.com/p/ocpgdb/ ocpgdb]
|BSD
|Unix
|2.3-2.6
|yes
|yes
|2010
|PG8.1+
|-
|[http://barryp.org/software/bpgsql/ bpgsql ]
|LGPL
|any (pure Python)
|2.3-2.6
|yes
|no
|2009
|labeled alpha
|}

More abandoned driver projects:

* [http://jamwt.com/pgasync/ pgasync], Twisted-native driver, no updates since 2005
* [http://sourceforge.net/projects/popy/ PoPy], no updates since 2003 - [https://github.com/Cito/PyGreSQL/commit/678cadfd2627b8821933ac8809ebafb15274882c development was merged with pygresql]
* [http://pypgsql.sourceforge.net/ pyPgSQL], no updates since 2006

There is [http://wiki.python.org/moin/PostgreSQL similar page on the Python wiki]

[[Python PostgreSQL Driver TODO]]

[[Category:Python]]

Hash Join

2019-11-01T04:14:54Z

Dfetter:

Here is a page to track ideas and ongoing work for hash joins. See also the [[Parallel_Hash]] page for parallelism-specific ideas.

Some active discussions with patches:

* Hash joins can, in extreme cases, use more memory that they are allowed to, if hash-based partitioning fails to divide the inner relation up enough to fit in the memory budget. [https://www.postgresql.org/message-id/flat/20190520143152.77nrjewyd3mbsbyj%40development#980efe458aa3feecbdbbdcc75688e7d6 Thread discussing strategies for respecting work_mem more strictly].

* Hash joins can decide to use a huge number of partitions in order to fit into work_mem, but the partition book-keeping is unmetered so can be way more than work_mem. [https://www.postgresql.org/message-id/flat/20190504003414.bulcbnge3rhwhcsh@development Thread discussing that, somewhat intertwined with the above discussion].

* Hash Join and Hash nodes seem to be very tightly coupled. [https://www.postgresql.org/message-id/flat/20191028231526.wcnwag7lllkra4qt%40alap3.anarazel.de Perhaps we should just merge them into one?]

* We could use Bloom filters. (Add short explanation here). [https://www.postgresql.org/message-id/flat/5670946E.8070705%402ndquadrant.com Thread] [https://www.postgresql.org/message-id/flat/c902844d-837f-5f63-ced3-9f7fd222f175%402ndquadrant.com Thread]

Observations without patches:

* nodeHashjoin.c's switch case HJ_SCAN_BUCKET calls ExecScanHashBucket() which contains ExecQualAndReset(hash clauses), and then after that returns it immediately does ExecQual(joinqual). So we pay the cost of evaluator setup twice, instead of doing both together. The reason we have to do this that EXPLAIN needs to count the two kinds of filtering separately, and we don't have a mechanism to build a single expression which ANDs together two filters and but maintains two separate counters. This might apply to other join types too. (Observation made by Andres Freund in private discussion with Thomas Munro, who added this note here.)

* Tuples are copied to intermediate palloc'd memory while loading them into the hash table during conversion to minimal tuple; we really just want to copy them directly into place in the hash table having allocated the memory!

* Memory is allocated in chunks that waste a ton of "invisible" memory on some OSes. [https://www.postgresql.org/message-id/flat/CAEepm%3D1bRyd%2B_W9eW-QmP1RGP03ti48zgd%3DK11Q6o4edQLgkcg%40mail.gmail.com Thread].

* Andres: There's too many indirections for hashtable lookups. For a successful hashtable lookup we need the following pointer dereferences: 1) HashJoinState->hj_HashTable (and a bunch of related state), 2) HashJoinTable->unshared 3) HashJoinTable->unshared[bucket] (likely uncached), 4) HashJoinTuple->hashvalue (likely uncached)
** We should work on at least removing the indirection for ->hashvalue, by moving the hashvalue into HashJoinTable->unshared[bucket], rather than that being just a pointer. It might be worthwhile to also store the ->next pointer inline.
** It could also be worthwhile to just embed the HashJoinTableData into the HashJoinState. As far as I can tell there's really no need for that to be a separate pointer indirection.

* Andres: The whole notion of HashJoinTuple is suspect - needing to perform the offsetting math in various places costs cycles itself, but also makes it harder to avoid unnecessary allocations in other places.

* Andres: The bucket scanning API (ExecScanHashBucket()) leads to unnecessary unpredictable branches, in a path that already suffers heavily from stalls.
** In a query where every lookup is a match (very commmon), the branch that decides whether to continue lookups in a previous bucket, or perform a fresh lookup, reaches both paths at roughly 50% - the worst case for a branch predictor. Instead there should be separate function for continuing a bucket search, which should be called by either branching earlier in the caller (will be very predictable), or even better by having a separate hj_JoinState value for continuing a bucket search.
** Currently the same "if" determines whether there is a match in a fresh lookup (common), and whether there's further tuples in a bucket (uncommon). That leads to inefficient branch prediction. Should be split.
** It might be worthwhile to move the check whether to search the skew hashtable into either a) the ExecHashJoinImpl() state-machine, by having a separate state for searching buckets in the skew hashtable b) just moving the check into ExecHashJoinImpl(), which'd at least allow to reuse the result of previous checks.

* Perhaps different hash join nodes could share a hash table, for the benefit of partition-wise joins. [https://www.postgresql.org/message-id/flat/CAOP8fzaVL_2SCJayLL9kj5pCA46PJOXXjuei6-3aFUV45j4LJQ%40mail.gmail.com Thread].

* There are arbitrary limits on the number of buckets you can have that come from using int in the logic and from respecting a 1GB memory allocation limit. If you run very large hash joins, you finish up hitting the cap of 64 (or is it 128?) million buckets and then the load factor goes beyond 1 due to this. It would be nice to fix that, as memories and data sets increase in size.

* Our load factor accounting should ideally be based on the number of unique keys, not the number of tuples. If there are a duplicate keys in the inner relation, we finish up with a too-sparse hash table.

Some work on the horizon:

* Andres Freund is working on transforming execution plans into a "linear programs" of opcodes (and eventually probably also machine code via LLVM), like SQLite and System R. This means we'll need to figure out how to break our hash join algorithm into steps that can be expressed that way.

* Even before we get that far, there may be micro-optimisation opportunities where we JIT some of the hashing work? Andres: Indeed, the evaluation of the hash keys is fairly expensive, especially with multiple columns. We should add an expression step for mixing hash values, and use that to build an expression that does not just evaluate the key, but immediately hashes it.

Some highly speculative work:

* It's possible to make hash joins go faster by peeking ahead at the next tuple to be probed, and prefetching the right memory cache line. [https://www.postgresql.org/message-id/flat/CAEepm%3D2y9HM9QP%2BHhRZdQ3pU6FShSMyu%3DV1uHXhQ5gG-dketHg%40mail.gmail.com Experimental hack thread with links to academic papers]. To do this well might require executor changes to that we can get a batch of tuples at the same time, and process them without escaping the current node.

PostgreSQL vs SQL Standard

2019-07-25T06:55:26Z

Dfetter: /* Major features simply not implemented yet */

This page attempts to document those instances where PostgreSQL deviates from standard SQL. It is not necessarily complete, and doesn't attempt to include all cases where an optional feature is not implemented or only partially implemented.

== Issues not yet classified ==

=== NOT NULL constraints on composite-type columns ===

The spec defines a <code>NOT NULL</code> column constraint as being equivalent to <code>CHECK(column IS NOT NULL)</code>, thus importing the semantics of composite-type null tests.

PostgreSQL treats <code>NOT NULL</code> as a simple "is not the null value" test, and therefore allows a row value with some null fields to be stored contrary to the spec.

=== COALESCE on row types ===

The spec defines <code>COALESCE(X,Y)</code> as a syntactic transformation to <code>CASE WHEN X IS NOT NULL THEN X ELSE Y END</code> (it leaves open the question of whether X is really evaluated twice by disallowing non-deterministic expressions or expressions with side effects in this context). A consequence of this is that the rather odd rules for null tests of row types are applied.

PostgreSQL applies only the "is not the null value" test to X. Accordingly, if X is a row value containing null columns, PostgreSQL will return X, while the spec would require returning Y.

 

== Fixable issues ==

These are cases where PG's behavior differs from the spec, but there appears to be no major obstacle to changing it to conform.

=== Wrong return type for extract() ===

The spec requires that <code>extract()</code> return an exact numeric type.

PostgreSQL returns an approximate numeric type (<code>double precision</code>).

There are obviously some backward compatibility concerns that would have to be considered before changing this one, but they don't look serious.

 

== Issues with some block to implementation ==

These are cases where PG's behavior differs from the spec, or where an otherwise desirable feature is missing, but there is some technical issue that would make it harder to implement.

=== LISTAGG() ===

<code>LISTAGG()</code> is the standard SQL equivalent of our <code>string_agg()</code>, but it uses the ordered-set aggregate syntax.

Implementing this in the most straightforward way would require erasing many of the existing distinctions between ordered-set aggregate syntax and conventional aggregate syntax. Currently we require that ordered-set aggs be called using <code>WITHIN GROUP</code>, while ordinary aggs must not use <code>WITHIN GROUP</code> but may have an embedded <code>ORDER BY</code> clause in their arguments (as per the standard <code>ARRAY_AGG()</code>).

<code>LISTAGG()</code> does not have the semantics of an ordered-set aggregate, so implementing it other than as a special case would mean allowing ordinary aggs to be called using <code>WITHIN GROUP</code> as an alternative to their normal syntax.

=== Data change delta tables ===

These are the standard's closest equivalent to our <code>RETURNING</code> and writable CTEs, but the visibility and trigger firing rules appear to be different to those of wCTEs, so one can't be implemented in terms of the other.

=== Identifier lengths ===

The spec requires that identifiers be allowed up to 18 characters even if the "long identifiers" feature is not declared; if it is, then the limit is 128 characters. Note that this limit is in characters and not bytes.

PostgreSQL limits the significant length of an identifier to 63 '''bytes''' unless specified otherwise at compile time; this isn't enough for 18 unicode characters.

Currently we use the fixed-length <code>name</code> type for names; making it larger would significantly inflate the sizes of many system catalogs, while making it variable length would be a compatibility issue (e.g. changing the order of columns in many system catalogs to put the name field after the fixed-length fields).

=== DISTINCT aggregates as window functions ===

PostgreSQL does not allow <code>DISTINCT</code> in aggregates when they are invoked as window functions.

The existing implementation of <code>DISTINCT</code> would be quite hard to adapt to window functions.

=== Deferrable CHECK and NOT NULL ===

The spec defines <code>NOT NULL</code> in terms of <code>CHECK</code>, and allows <code>CHECK</code> constraints to be deferrable.

PostgreSQL currently does all these checks before actually inserting the new or modified row.

=== FULL OUTER JOIN conditions ===

The spec allows any join condition for a <code>FULL OUTER JOIN</code>.

PostgreSQL currently limits such conditions to ones that are implementable without constructing explicit <code>UNION</code> operations; that is, the condition must be hashable, mergeable, or constant.

Adding support for arbitrary full joins (which would likely require constructing a <code>UNION</code> of the inner join and the two anti-joins) seems like a lot of work for minimal gain.

 
== Issues with some block at design level ==

These are cases where PG's behavior differs from the spec, or where an otherwise desirable feature is missing, but there is some technical issue that makes it hard to even decide how to implement it.

=== ANY() and SOME() aggregates ===

PostgreSQL supports <code>every()</code> from the standard, and provides <code>bool_or</code> as a nonstandard spelling of the <code>ANY</code>/<code>SOME</code> aggregate function, but two syntax conflicts make it impossible to parse the standard's <code>ANY</code> syntax:

# PostgreSQL allows <code>= ANY (array_expression)</code> as a form of quantified comparison predicate (this is an extension to the spec)
# PostgreSQL allows subselects in all contexts to have additional parentheses, which the spec does not allow

The spec's syntax for <code>ANY(expression)</code> as an aggregate function can be parsed unambiguously only because the spec's version of <code>ANY</code> as a quantified comparison predicate must have the keyword <code>SELECT</code> immediately following the <code>ANY(</code>.

=== Unreserved keywords as select-list aliases without AS ===

The spec requires that <code>SELECT 1 ZONE</code> be equivalent to <code>SELECT 1 AS ZONE</code>. PostgreSQL accepts only the latter form or alternatively requires the identifier to be quoted.

The main syntax ambiguity here is caused by the presence of postfix operators in PostgreSQL syntax; <code>SELECT 1 ! ZONE</code> would be ambiguous between treating the operator as postfix or infix (we take it as being infix in this case by using precedence rules). Additional ambiguities exist with compound type names using <code>NATIONAL</code>, <code>VARYING</code>, or <code>WITHOUT</code> (which would likely have to be made reserved words, as they are in the spec). <code>WITHIN</code>, <code>FILTER</code>, and <code>OVER</code>, and the datetime component names, which are not currently reserved in PostgreSQL, would also need to become reserved words. Since adding so many more reserved words is likely to break existing queries, this isn't considered a particularly viable solution.

=== DROP DOMAIN … CASCADE ===

The spec says that <code>DROP DOMAIN … CASCADE</code> does not drop any columns, but simply changes any columns of the domain type to instead use the base type with the addition of the domain's defaults and constraints.

PostgreSQL drops columns of the domain type.

The issue here is that we can reach a <code>DROP DOMAIN</code> by cascading from a drop of another object, such as a schema containing the domain or a function referenced in the domain's default or constraints. Supporting the standard behavior would therefore mean altering objects in ways that add new dependencies from within the code that traverses the existing dependencies, which seems problematic.

=== Temporary tables ===

In the spec, temporary tables are persistent schema objects whose ''data'' (and only the data) is temporary and per-session. Implementing these in PostgreSQL would actually have substantial advantages (catalog bloat when using temp tables heavily is a common problem); but PostgreSQL's existing behavior is very well-entrenched and changing it would cause compatibility issues.

(One approach sometimes suggested would be to use the spec's method if <code>GLOBAL</code> was specified when creating the table.)

=== Mandatory parens in VALUES ===

The spec allows <code>VALUES 1,2,3</code> (as an explicit table with 1 column, 3 rows).

PostgreSQL requires parens on each row: <code>VALUES (1),(2),(3)</code>.

It looks like the only obstacle here is that <code>VALUES</code> would need to become a reserved word.

 
== Issues where we explicitly choose to disregard the spec (WONTFIX) ==

=== Identifier case ===

PostgreSQL folds unquoted identifiers to lowercase, not the uppercase that the spec requires.

=== Constraint name scope ===

PostgreSQL treats the scope of a table or column constraint name as being the table it belongs to. The spec requires that such names be unique over the whole schema.

PostgreSQL's behavior here severely limits the usefulness of several <code>information_schema</code> views, which are defined on the assumption of schema-wide constraint name uniqueness.

=== TIMESTAMP WITH TIME ZONE ===

PostgreSQL's timestamp with time zone type is very different from the standard one.

# <code>timestamp '2018-06-01 00:00:00+1200'</code> is a timestamp without timezone, spec says it should be with timezone. PostgreSQL does not allow the type of a literal to depend on its string value.
# <code>timestamp with time zone</code> does not store a timezone offset, but is interpreted with the session timezone. The spec's timezone handling is less than useless, PostgreSQL's is actually useful.

=== AT TIME ZONE ===

Our <code>AT TIME ZONE</code> operator is somewhat different to the spec's.

The spec says:

# <code>t AT TIME ZONE z</code> where <code>t</code> is of type <code>time[stamp] without time zone</code> returns a result of the corresponding <code>with time zone</code> type.
# <code>t AT TIME ZONE z</code> where <code>t</code> is of type <code>time[stamp] with time zone</code>, the result is of the same type.

What PostgreSQL does is:

# <code>t AT TIME ZONE z</code> where <code>t</code> is of type <code>timestamp without time zone</code> returns a result of type <code>timestamp with time zone</code>.
# <code>t AT TIME ZONE z</code> where <code>t</code> is of type <code>timestamp with time zone</code> returns a result of type <code>timestamp without time zone</code>.
# <code>t AT TIME ZONE z</code> where <code>t</code> is of type <code>time with time zone</code> returns a result of type <code>time with time zone</code>.
# <code>t AT TIME ZONE z</code> where <code>t</code> is of type <code>time without time zone</code> casts the value of <code>t</code> to type <code>time with time zone</code> and then proceeds as the previous option.

This permits various transforms which are simply not possible in the spec's crippled timezone support, such as converting a wallclock time from one location to another via two applications of <code>AT TIME ZONE</code>.

=== INTERVAL ===

The standard interval type assumes that all days are the same length, and therefore intervals can be divided into "year-month" and "day-second" values; only one of which can be present in any single interval value or column.

PostgreSQL's interval type has three fields: months,days,[micro]seconds and allows all three to be present simultaneously.

Rationale: the spec's lack of usable timezone support makes its interval type useless too.

=== Transaction management ===

The spec's model of the relationship between the database and its clients differs from PostgreSQL's (and most other databases for that matter). This leaves the spec's requirements concerning how transactions begin and end as somewhat inconsistent, with some statements being defined as implicitly starting transactions and others not (and some may or may not implicitly start transactions depending on variable content).

PostgreSQL treats all client requests (which may contain multiple statements) as being wrapped in a transaction (auto-committing at the end of the request) except where <code>BEGIN</code> or <code>START TRANSACTION</code> is used explicitly.

=== Default transaction isolation level ===

The spec declares <code>SERIALIZABLE</code> to be the default isolation level, but PostgreSQL defaults to <code>READ COMMITTED</code>.

=== Object ownership scope ===

The standard controls ownership of objects only at the schema level; objects inside a schema belong to the schema's owner.

PostgreSQL tracks ownership at individual object level.

Rationale: this PG behavior dates back to before it had schemas, and is much more flexible than the standard's approach.

=== Trigger firing order ===

The standard says that trigger firing order on a table depends on creation order of the triggers.

PostgreSQL fires triggers in order of name.

Rationale: documentation says "this was judged to be more convenient".

=== Trigger firing relative to referential constraint actions ===

The spec requires that when a referential action (e.g. <code>CASCADE</code> or <code>SET NULL</code>) causes a <code>BEFORE</code> trigger to be fired, the referential action is actually performed before firing the trigger.

One possible motivation for this is to ensure that the trigger function doesn't see the inconsistent intermediate state of the database in which the FK is violated.

Nevertheless, PostgreSQL always runs the <code>BEFORE</code> trigger before doing the operation.

In addition, the spec requires that referential constraints are enforced before <code>AFTER</code> triggers. PostgreSQL instead enforces them via triggers with names of the form <code>"RI_ConstraintTrigger_…"</code> which are executed in name order with respect to other triggers (see [[#Trigger_firing_order|this item]]).

=== LIKE with no escape clause ===

The standard says that <code>LIKE</code> has no escape character if the <code>ESCAPE</code> clause was not specified.

PostgreSQL treats a missing <code>ESCAPE</code> clause as if it were <code>ESCAPE '\'</code>.

Rationale: historical.

=== Declared type of string literals ===

The standard says that the type of a string literal is fixed-length character string, i.e. <code>character(n)</code> where <code>n</code> is the length of the literal.

PostgreSQL treats untyped literals as being of unknown type and deduces the type from context (even in contexts where the spec does not provide for contextual typing). If no type is deduced, the value is treated either as <code>text</code> or <code>unknown</code> type depending on context and PostgreSQL version.

=== Trailing spaces in character(n) ===

Trailing spaces in char(n) values are removed in contexts where the spec requires they be kept.

An example is that <code>LIKE</code> will remove trailing spaces from a <code>character(n)</code> pattern parameter (but not from the first parameter).

Rationale: PG actually converts char(n) to text in most contexts and all the relevant functions and operators take text args, rather than having separate versions for char(n).

=== FETCH FIRST 0 ROWS ===

The spec requires an error to be generated for specifying a limit of 0. We generate errors only for values strictly less than 0.

=== Early enforcement of non-deferrable UNIQUE ===

The spec says that <code>UNIQUE</code> (and <code>PRIMARY KEY</code>) constraints are enforced at statement end and not row-by-row when in immediate mode, with no distinction between non-deferrable constraints and deferrable constraints currently set to immediate mode.

PostgreSQL enforces non-deferrable constraints row-by-row, and deferrable constraints in immediate mode at statement end. This is a compromise between wanting to preserve the hard semantic guarantees of uniqueness in row-by-row mode (relied on by the planner in order to prove result uniqueness), while allowing conflicting updates (e.g. <code>UPDATE … SET uniq = uniq + 1</code> where really necessary.

=== Lexing of string literals and comments ===

PostgreSQL rejects all of these:


<code><pre>
select 'foo'
/**/ 'bar' from ...

select 'foo' /**/ 'bar' from ...

select U&'foo' UESCAPE /**/ 'x' from ...

select 'foo' as U&"foo" UESCAPE /**/ 'x' from ...

select U&'foo' /**/ UESCAPE 'x' from ...

select 'foo' as U&"foo" /**/ UESCAPE 'x' from ...
</pre></code>

The first of those is certainly legal in the spec; the remainder are more debatable since the spec is rather unclear.

Regarding the second case:

<blockquote>
<code>5.3 <literal></code> 
Syntax Rules 
7) In a <code><character string literal></code>, <code><national character string literal></code>, <code><Unicode character string literal></code>, or <code><binary string literal></code>, a <code><separator></code> shall contain a <code><newline></code>.
</blockquote>

But SQL2016 also says:

<blockquote>
<code>5.2 <token> and <separator></code> 
Syntax Rules 
11) SQL text containing one or more instances of <code><comment></code> is equivalent to the same SQL text with the <code><comment></code> replaced with <code><newline></code>.
</blockquote>

which implies that the input should have been accepted.

Regarding the remaining cases:

<blockquote>
<code>5.2 <token> and <separator></code> 
<code><separator> ::= { <comment> | <white space> }...</code> 
Syntax Rules 
7) Any <code><token></code> may be followed by a <code><separator></code>.
</blockquote>

<blockquote>
<code>5.3 <literal></code> 
Syntax Rules 
11) In a <code><Unicode character string literal></code>, there shall be no
<code><separator></code> between the "U" and the <code><ampersand></code> nor between the
<code><ampersand></code> and the <code><quote></code>.
</blockquote>

which seems to imply that <code><separator></code> around the <code>UESCAPE</code> would be permitted; indeed, no other rule permits any kind of whitespace there.

There's no present desire to fix this because of the added complexity in the lexer. It is possible that this could be revisited if the lexer is redesigned in future.

 

== Issues where PostgreSQL actually conforms to the spec ==

These issues have been claimed or discussed as violations, but where PostgreSQL currently conforms to the spec as written. These are for reference in case they come up again; also, cases where PostgreSQL formerly violated the spec can be noted here as fixed.

=== null return from every(x) ===

In the query <code>SELECT every(x) FROM t;</code> the result will be <code>NULL</code> if <code>t</code> has no rows or all values of <code>t.x</code> are <code>NULL</code>. This is correct as per the spec, even though it's inconsistent with conventional mathematical usage (in which an AND of no terms should return true).

 
== Major features simply not implemented yet ==

* CREATE TABLE … (LIKE … INCLUDING GENERATED)
* MATCH PARTIAL
* references in typed tables
* fetch first … with ties
* fetch first … percent
* more functional dependencies
* row pattern recognition
* partition join
* distinct types
* temporal tables
* generated columns (partially implemented)
* respect/ignore nulls for window functions
* "from last" for nth_value
* many more
* CAST(val AS type FORMAT 'template')

PostgreSQL Clients

2019-05-22T17:08:52Z

Dfetter: /* DBeaver */

This page is a partial list of interactive SQL clients - that doesn't include reporting engines, ETL data loaders, visual design tools, just interactive clients that you can type SQL in to and get results from them.

== CLI Clients ==

=== Open Source / Free Software ===

==== psql ====

https://www.postgresql.org/docs/current/static/app-psql.html

The standard command line client, maintained by the postgresql development group and typically distributed as part of the server installation.

==== pgcli ====

https://www.pgcli.com

A command line client with syntax highlighting and pop-up command completion.

==== jaqy ====

https://teradata.github.io/jaqy/

A universal JDBC command line client with lots of features. It is not specific to PostgreSQL, but it is pre-configured to handle PostgreSQL servers. Requires PostgreSQL JDBC driver.

== macOS GUI Clients ==

=== Open Source / Free Software ===

==== Postbird ====

https://github.com/paxa/postbird

Open source, desktop application to manage your local or remote PostgreSQL databases.

=== Proprietary ===

==== SQLPro for Postgres ====

http://www.macpostgresclient.com/SQLProPostgres

macOS 10.8 and above

100% native OS X app with a clean and simple to use interface. Query editor with syntax highlighting and autocomplete.

==== TablePlus ====

https://tableplus.io/

A modern, native client for relational databases with nice UI and very convenient query editor. It's compatible with all versions of Postgres.

==== Postico ====

https://eggerapps.at/postico/

A nice native client by the developers of [http://postgresapp.com Postgres.app]. A free "demo" version of an inexpensive proprietary app, but it has very reasonable limits and no time limit.

==== pgEdit ====

http://pgedit.com

Not a standalone client, rather a plugin for [https://macromates.com Textmate] for using psql.

==== PSequel ====

http://www.psequel.com/

OS X Yosemite only, free, "Sequel Pro" inspired.

==== SEQUEL for PostgreSQL ====

http://www.sequel.tech

SEQUEL for PostgreSQL is a professional DB administration and management tool, with extremely intuitive and feature rich GUI that makes it the best assistant tool for developers and admins. SEQUEL is lightweight, fast and powerful that it can significantly simplify the DB management process. For those who cannot live without a CLI, SEQUEL offers a powerful Query Editor with syntax highlight, autocomplete and a Console log view that is always visible, so you can monitor the communication with your databases.

== Windows GUI Clients ==

=== Open Source / Free Software ===

=== Proprietary ===

==== DBTools Manager ====

http://www.dbtools.com.br

Freeware, available for PostgreSQL and MySQL, allows managing all aspects of the database: db, table, triggers, functions, etc. Includes import/export wizards to migrate data and structure to/from other database engines.

==== EMS SQL Manager for PostgreSQL Freeware ====

http://www.sqlmanager.net/en/tools/free

EMS SQL Manager for PostgreSQL Freeware (EMS SQL Manager Lite for PostgreSQL) is an excellent and easy-to-use freeware graphical tool for PostgreSQL database administration. It has the minimal required set of tools for those users who are new to PostgreSQL server and need only its basic functionality.

There is a proprietary version available with significantly more functionality.

==== Marshal SQL Utility ====

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1756

The Marshal SQL Utility is a generic cross database utility with batch execution capabilities. It allows you to test ODBC connections, browse database schemas, discover tables, views and columns.

==== dbForge Studio for PostgreSQL ====

https://www.devart.com/dbforge/postgresql/studio/

dbForge Studio for PostgreSQL is a GUI tool for managing and developing databases and objects. The PostgreSQL IDE allows users to create, develop, and execute queries, edit and adjust the code to your requirements in a convenient and UI. The tool provides a data editing tool to customize your queries and property window so that users can view all the required information of PostgreSQL database objects they are interested in.

==== AnySQL Maestro ====

http://www.sqlmaestro.com/products/anysql/maestro/

AnySQL Maestro is a freeware tool for administering any database engine (PostgreSQL, SQL Server, Oracle, MySQL, MS Access, etc.), which is accessible via ODBC driver or OLE DB provider. Includes Database Designer, Visual Query Builder, BLOB Viewer/Editor, SQL Editor, Data export/import and other features.

==== PostgreSQL Maestro ====

https://www.sqlmaestro.com/products/postgresql/maestro/

Allows you to create, edit, copy, drop and dump database objects easy and fast. You can also design your database as ER diagram, build queries visually, execute SQL queries and scripts, debug PL/pgSQL functions, view and edit data including BLOBs, represent data as diagrams, export and import data to/from most popular file formats, analyze your data summarized into multidimensional views and hierarchies (OLAP cubes), manage PostgreSQL roles, users, groups and privileges, and use a lot of other admin tools designed for making your work with PostgreSQL database server comfortable and efficient.

==== Access ====

https://products.office.com/en-us/access

Yes, you can use MS Access as a PostgreSQL database interface. Supports data access to PostgreSQL tables and views; many ODBC-based limitations and errors.

==== VSQL++ for PostgreSQL ====

http://www.sqlpp.com/products/postgresql-management/

A powerful Postgresql database management tool to help DBA sto manage the database objects easy and quickly.

==== Nucleon Database Master ====

http://nucleonsoftware.com/products/database-master

Supports PostgreSQL MongoDB, Oracle, DB2, Informix, Ingres, SQL Server, SQL Azure, MySQL, FireBird, SQLite

==== SQLPro ====

http://www.vive.net/products/sqlpro.htm

SqlPro is an easy to use database GUI tool for six popular databases (Oracle, MySQL, PostgreSQL, SQL Server, SQLite and Access). One IDE makes database administration and development faster and error free.
SQLPro Key Features: color-coding of the SQL, drag-and-drop of objects into the editor pane to save you from typing their names, retrieval of SQL code for things like stored procedures and triggers from the underlying database, and one-click creation of SELECT and INSERT statements. You can open, save and print SQL scripts.

=== Obsolete or End-of-Life ===

==== PGExplorer ====

http://www.PGExplorer.com

Hasn't been significantly updated in many years, but latest downloads suggest it may support Postgresql 9.* to some extent.

== Linux / Unix GUI Clients ==

=== Open Source / Free Software ===

==== Gnome DB ====

http://www.gnome-db.org

Database administration/user tool for GNOME, based on libgda/libgnomedb, which are a complete database-independent access layer for UNIX systems, with support for PostgreSQL, MySQL, Sybase, MS SQL Server, Oracle, Interbase/Firebird, MS Access files, xBase.

Has an experimental Windows build available too.

==== Kexi ====

http://www.kexi-project.org/

A visual database application creator, c.f. Access or FileMaker

== Cross-platform GUI Clients ==

=== Open Source / Free Software ===

==== pgAdmin 3 ====

http://www.pgadmin.org/

Windows, Linux, FreeBSD, macOS, OpenBSD, Solaris

For many years the "standard" freely available GUI client for Postgresql, and so is bundled in many packaged installers. It provides a SQL query tool, an editor for procedural languages and a CRUD interface. It's also one of the few clients to provide a GUI front end to the plpgsql debugger.

Development has been discontinued by pgadmin.org, but it is still being maintained by BigSQL who are doing basic maintenance to support current versions of PostgreSQL and packaging it for current OS releases [[https://www.openscg.com/bigsql/pgadmin3/index.jsp/ here]]

==== pgAdmin 4 ====

http://www.pgadmin.org/

Windows, macOS, [https://yum.postgresql.org rpm], Python

pgAdmin 4 is a ground-up rewrite of pgAdmin 3. Rather than being a native application it's primarily a web application that's also packaged as desktop web shell. At the time of writing it's considered inferior to pgAdmin 3 both in terms of functionality and stability.

==== LibreOffice Base ====

http://www.libreoffice.org/discover/base/

Supports MySQL/MariaDB, Adabas D, MS Access and PostgreSQL, as well as other JDBC/ODBC databases.

==== Tora ====

http://tora.sf.net/

Linux, Windows, macOS

Oracle, MySQL, and PostgreSQL, as well as limited support for ODBC targets. Inspired by the proprietary Toad client.

==== SQL Workbench/J ====

http://www.sql-workbench.net

Java

An OpenSource (though it prohibits usage by government agencies from USA, UK, Canada, China, Russia, North Korea, Syria, Saudi Arabia, Turkey and the Chechen Republic) SQL GUI tool similar to Squirrel. Data can be edited directly in the result set. It has strong support for exporting and importing data between databases using its own SQL command extension. It can be used in GUI mode or as a console application. All SQL Workbench specific commands can also be run in batch mode to automate export and import task. It supports schema comparison ("diff") and copying data between databases.

It has some [http://sql-workbench.net/manual/license.html#license-restrictions restrictions] on use by government employees.

==== Druid III ====

http://druid.sourceforge.net/

Java

The druid is a tools that allows users to create databases in a graphical way. The user can add tables, fields, folders to group tables and can modify most of the database options that follow the SQL-92 standard. In addition to sql options, the user can document each table and each field with HTML information.

==== Power*Architect ====

http://www.sqlpower.ca/page/architect

Java

Power*Architect is an ERD modelling tool that is based on Java and JDBC. Support for forward and reverse engineering PostgreSQL databases is supported. It's OpenSource with a GPL license.

==== DBeaver ====

https://dbeaver.io

Java

Supports many SQL databases from different vendors, as well as few NoSQL ones (Cassandra, etc).
Good query editor with syntax highlighting, completion and autosave.
Editing of query results. SSH tunneling support. Tons of other cool features.
Quite good, but not 100% perfect PostgreSQL support (yet?). Regularly updated, as of 2019.

==== pgManage ====

https://github.com/pgManage/pgManage

An alternative to pgAdmin, which runs in both application and server modes.

==== OmniDB ====

https://github.com/OmniDB/OmniDB

Linux, Windows and macOS

Open source full-featured tool for database management. Currently supports PostgreSQL (9.3 - 11), Oracle (11g - 18c), MySQL (5.6 - 8.0) and MariaDB (10.1 - 10.3). More RDBMS support coming soon, including the ability of converting databases from any supported RDBMS to PostgreSQL and back.

=== Proprietary ===

==== Valentina Studio (Free) ====

http://www.valentina-db.com/valentina-studio-overview

Windows/OS X/Linux

Valentina Studio is a powerful PostgreSQL Database Server administration and development tool.

There is a proprietary version available with additional functionality.

==== RazorSQL ====

http://www.razorsql.com/

Macintosh/Windows/Linux/Solaris

RazorSQL is an SQL query tool, database browser, SQL editor, and database administration tool that supports PostgreSQL and any other JDBC or ODBC compliant database. Some of the major features are tools for creating, dropping, and altering objects such as tables, views, indexes, triggers, functions, users, and databases; a programming editor that supports 20 different programming languages; import and export tools; auto column and table lookup; and a query builder, query scheduler, and SQL formatter.

==== JetBrains DataGrip ====

https://www.jetbrains.com/datagrip/

Windows, macOS, Linux

JetBrains has a dedicated SQL IDE — DataGrip which can connect to PostgreSQL as well. It provides code completion, multicursors, local query history, navigation, refactorings and language injection support.

Other JetBrains IDEs have plugins available to provide similar functionality.

==== Aqua Data Studio ====

http://www.aquafold.com/index-postgresql.html

Java: Windows/Linux/macOS/Solaris

Aqua Data Studio is a management tool for the PostgreSQL relational database w/ administration capabilities and a database query tool. The visual administration features provide users the ability to browse and modify database structures, including schema objects, database storage and maintain database security. An integrated query tool allows users to quickly create, edit and execute SQL queries and scripts. Aqua Data Studio also provides an import and export tool to allow users to easily move data in and out of the PostgreSQL database in and from different data formats.

==== Navicat ====

https://www.navicat.com/en/products/navicat-for-postgresql

Windows, macOS, iOS

Navicat is a powerful PostgreSQL Database Server administration and development tool. It works with PostgreSQL 8.0 version or above and supports most of the PostgreSQL features including Trigger, Function, View, Manage User, and so on. It is also not only sophisticated enough for professional developers, but also easy to learn for new users. With its well-designed GUI, Navicat lets you quickly and easily create, organize, access and share information in a secure and easy way.

==== DbVisualizer ====

http://www.dbvis.com/

Windows/macOS/Linux/UNIX

DbVisualizer is a feature rich, intuitive multi-database tool for developers, database administrators, and increasingly for advanced analysts providing a single powerful interface across a wide variety of operating systems. With its easy-to-use and clean interface, DbVisualizer has proven to be one of the most cost effective database tools available, yet to mention that it runs on all major operating systems and supports all major RDBMS that are available. Users only need to learn and master one application. DbVisualizer integrates transparently with the operating system being used.

==== Datazenit ====

https://datazenit.com/

Windows, Mac OS X, Linux

Datazenit is a cross-platform PostgreSQL and MySQL GUI with data grid, schema builder and interactive charts.
It also has query builder, raw query editor with auto-complete, team collaboration features like connection, query and chart sharing among team members.

Web-based, but available packaged as a desktop app.

== Android ==

=== Proprietary ===

==== SQLTool Pro Database Editor ====

http://www.sqltoolpro.com

SQLTool Pro is a professional Android SQL editor for MySQL, SQL Server, PostgreSQL, Sybase, and Oracle Databases. JDBC.

== Web Clients ==

=== Open Source / Free Software ===

==== franchise ====

https://franchise.cloud/

Web client, either hosted (free) or running locally, connects to a local postgresql instance via a small bridge application.

Can share the interface with others, rather like sqlfiddle.com, but accessing your database.

==== pgAdmin 4 ====

http://www.pgadmin.org/

Python

pgAdmin 4 is a ground-up rewrite of pgAdmin 3. Rather than being a native application it's primarily a web application that's also packaged as desktop web shell. At the time of writing it's considered inferior to pgAdmin 3 both in terms of functionality and stability.

==== TeamPostgreSQL ====

http://www.teampostgresql.com

browser-based, webserver included

AJAX/JavaScript-powered web interface for PostgreSQL administration. Browse, maintain and create data and database objects from anywhere, in the web browser. Supports SSH for both the web interface and the database connections. Rich interface with tabbed SQL editor with auto-completion, inline row-editing widgets, click-through foreign key navigation between rows and tables, 'favorites' management for commonly used scripts, and more.

Installers available for Windows, Mac and Linux, alternatively download a simple cross-platform archive that runs anywhere with simple script.

==== Adminer ====

http://www.adminer.org

PHP

Adminer (formerly phpMinAdmin) is a full-featured database management tool written in PHP. A single PHP file ready to deploy to the target server. Adminer is available for MySQL, PostgreSQL, SQLite, MS SQL and Oracle.

==== OmniDB ====

https://github.com/OmniDB/OmniDB

Django/Python

Open source full-featured tool for database management. Currently supports PostgreSQL (9.3 - 11), Oracle (11g - 18c), MySQL (5.6 - 8.0) and MariaDB (10.1 - 10.3). More RDBMS support coming soon, including the ability of converting databases from any supported RDBMS to PostgreSQL and back.

==== Tadpole DB Hub ====

https://github.com/hangum/TadpoleForDBTools/wiki

Tadpole DB Hub is Unified infrastructure tool, various environment based interface for managing Apache Hive, Amazon RDS, CUBRID, MariaDB, MySQL, Oracle, SQLite, MSSQL, PostgreSQL and MongoDB databases. It enables you to handle typical DB over the World Wide Web.

==== SIDU ====

http://topnew.net/sidu/

PHP

Schema and data browser and editor.

==== Hisha ====

https://github.com/xshogi/hisha

Node.js

Hisha is cross-platform and web-based Postgre SQL Database client inspired by Adminium. You can edit and save result by clicking the cell you want and press enter when you finish.

=== Proprietary ===

==== JackDB ====

http://www.jackdb.com/

Html5 Web Browser (Linux/Mac OS X/Windows)

JackDB is a database client that runs entirely in your web browser. There's no software to install locally so you can use it on Mac OS X, Linux, and Windows and it works on all major modern browsers (eg. Chrome, Firefox, IE, Safari, and Opera). It supports connecting to PostgreSQL, as well as MySQL, Oracle, and SQL Server databases.

A hosted service, so it requires external access to your database.

==== DBHawk ====

https://www.datasparc.com/dbhawk/

DBHawk is a web based SQL tool and reporting software designed for PostgreSQL, Oracle, SQL Server and other databases. Its easy to deploy and use.

Query editor, report builder, schema and data browser.

==== Datazenit ====

https://datazenit.com/

Java

Datazenit is a cross-platform PostgreSQL and MySQL GUI with data grid, schema builder and interactive charts.
It also has query builder, raw query editor with auto-complete, team collaboration features like connection, query and chart sharing among team members.

Web-based, but available packaged as a desktop app.

=== Obsolete or End-of-Life ===

==== phpPgAdmin ====

http://phppgadmin.sourceforge.net/doku.php

PHP

Similar to phpMyAdmin, enhanced for PostgreSQL, supports browsing and modification of most types of PostgreSQL database objects, plus execution of ad-hoc queries.

(last updated 2013, 9.2.x)

== Other Resources ==

[[Community Guide to PostgreSQL GUI Tools]] - the source for a lot of this page. Includes many non-client tools, such as bulk loaders, schema diff, schema design, etc.

[http://www.postgresonline.com/journal/index.php?/archives/133-Database-Administration,-Reporting,-and-Light-application-development.html Database Administration, Reporting, and Light application development] - from 2009

[[GUI Database Design Tools]] - tools for designing database schemas

Community Guide to PostgreSQL GUI Tools

2019-05-04T17:34:55Z

Dfetter: Alphabetized FLOSS options.

{{Languages}}

== Alternate Guides ==

Another detailed summary from 2009 is available at
[http://www.postgresonline.com/journal/index.php?/archives/133-Database-Administration,-Reporting,-and-Light-application-development.html Database Administration, Reporting, and Light application development]

== Open Source / Free Software ==

=== Adminer ===

http://www.adminer.org

browser-based, requires webserver

Adminer (formerly phpMinAdmin) is a full-featured database management tool written in PHP. Conversely to phpMyAdmin, it consist of a single file ready to deploy to the target server. Adminer is available for MySQL, PostgreSQL, SQLite, MS SQL and Oracle.

=== DBeaver ===

https://dbeaver.io

Eclipse/Java (multi-platform)

Eclipse-based environment, supporting many SQL databases from different vendors, as well as few NoSQL ones (Cassandra, etc).
Good query editor with syntax highlighting, completion and autosave.
Editing of query results. SSH tunneling support. Tons of other cool features.
Quite good, but not 100% perfect PostgreSQL support (yet?). Regularly updated, as of 2018.

=== Druid III ===

http://druid.sourceforge.net/

Java (multi-platform)

The druid is a tools that allows users to create databases in a graphical way. The user can add tables, fields, folders to group tables and can modify most of the database options that follow the SQL-92 standard. In addition to sql options, the user can document each table and each field with HTML information. Once the database is created, the druid can generate:

* HTML documentation: for all tables, with browsing facilities
* PDF documentation: for all tables
* Java classes: (one class for each table) that contain tables' constants (such as fields size) plus java code added by the user
* A data dictionarythat contains all tables and fields present in the database
* SQL script which contains all table definitions that can be piped to the DBMS
* And much more info...

=== GNOME-DB ===

http://www.gnome-db.org

Linux, Unix

Admin

Database administration/user tool for GNOME, based on libgda/libgnomedb, which are a complete database-independent access layer for UNIX systems, with support for PostgreSQL, MySQL, Sybase, MS SQL Server, Oracle, Interbase/Firebird, MS Access files, xBase.

=== Kexi ===

http://www.kexi-project.org/

Kexi is part of the Calligra Suite and is released under the GNU General Public License (GPL) and LGPL.

available for
FreeBSD & Linux, Apple, Windows, (Android)

=== Libre Office ===

http://www.libreoffice.org/download/3-5-new-features-and-fixes/

New native driver for PostgreSQL databases (for versions > 8.4 - support for version 8.4 will be included in LibreOffice 3.5.1).

=== OmniDB ===

https://github.com/OmniDB/OmniDB

Linux, Windows and macOS

Open source full-featured tool for database management. Currently supports PostgreSQL (9.3 - 11), Oracle (11g - 18c), MySQL (5.6 - 8.0) and MariaDB (10.1 - 10.3). More RDBMS support coming soon, including the ability of converting databases from any supported RDBMS to PostgreSQL and back.

=== Open Source CMS ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=2017

Windows

The CMS is a free Visual Studio 2010 solution template with a set of projects providing a complete Content Management System (CMS) based on RISE Visual Modeling with model, full source, sample site and DB-scripts for PostgreSQL, MySQL and SQL Server.

It’s a complete ready-to-run Visual Studio solution with model, source code and web clients. It illustrates how to use RISE, how to implement a SOA backend and how to build RIA frontends.

=== PASH-Viewer: PostgreSQL Active Session History Viewer ===

https://github.com/dbacvetkov/PASH-Viewer

Java (multi-platform).

Open-source software which provides graphical view of active session history and help you to answer questions like "What wait events were taking most time?", "Which sessions were taking most time?", "Which queries were taking most time and what were they doing?". It also supports Active Session History extension by pgsentinel.

=== pgAdmin 4 ===

http://www.pgadmin.org/

MS Windows, GNU/Linux, FreeBSD, Mac OS X, OpenBSD, Solaris

Admin

pgAdmin III is an Open Source management tool for PostgreSQL databases. Features full Unicode support, fast, multithreaded query and data editing tools and support for all PostgreSQL object types.

pgAdmin III is bundled with the Windows installer, and you can use that such a client to administer a remote server on another OS. Note that binary packages for platforms like RPM don't show up in every point release, you currently have to go back to v1.8.0 to get the last full set of packages.

Free Administration Centre for the PostgreSQL database. Includes a graphical administration interface, an SQL query tool, a procedural code editor and much more. pgAdmin III is designed to answer the needs of most users, from writing simple SQL queries to developing complex databases. The graphical interface supports all PostgreSQL features and makes administration easy. Available in more than 30 languages and for several operating systems.

=== pgrights: GUI for PostgreSQL roles, privileges and policies ===

https://github.com/apsavin/pgrights

MacOS (based on Electron, so versions for other OS can be build from source code).

Open-source software which allows you to easely understand what can do (and what can't) a PostgreSQL user with a table's data. In other words, it's a viewer of results of GRANT commands and row-level security rules applied for a particular table and for a particular role.

=== phpPgAdmin ===

http://sourceforge.net/projects/phppgadmin

browser-based, requires webserver

Admin

Similar to the ever-popular phpMyAdmin, enhanced for PostgreSQL, supports browsing and modification of most types of PostgreSQL database objects, plus execution of ad-hoc queries. Maintained by (who else?) the phpPgAdmin team. (JMB 11.2002).

phpPgAdmin (and the required Apache and PHP packages) may be easily installed using Stack Builder if you are running a one-click-installer PostgreSQL distribution.

=== Postbird ===

https://github.com/paxa/postbird

MacOs

Open source, desktop application to manage your local or remote PostgreSQL databases.

=== Power*Architect ===

http://www.sqlpower.ca/page/architect

Java (multi-platform)

Power*Architect is an ERD modelling tool that is based on Java and JDBC. Support for forward and reverse engineering PostgreSQL databases is supported. It's OpenSource with a GPL license.

=== RISE PostgreSQL code generator ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1889

Windows

The RISE PostgreSQL code generator generates native PL/pgSQL scripts. Model your information in the free RISE Editor and generate your database script. The script incrementally updates the tables, columns, indexes and constraints in the database to match the RISE model. Once the database model is updated, the views defined in the RISE model are created in the database and possible default data, entered in the model, is inserted.

=== SQL Workbench/J ===

http://www.sql-workbench.net

Java (multi-platform)

An OpenSource SQL GUI tool similar to Squirrel. Data can be edited directly in the result set. It has strong support for exporting and importing data between databases using its own SQL command extension. It can be used in GUI mode or as a console application. All SQL Workbench specific commands can also be run in batch mode to automate export and import task. It supports schema comparison ("diff") and copying data between databases.

=== SQuirrel ===

http://www.squirrelsql.org/

Platforms that support Java

Admin

SQuirreL SQL Client is a graphical Java program that will allow you to view the structure of a JDBC compliant database, browse the data in tables, issue SQL commands etc. The minimum version of Java supported is 1.8.x as of SQuirreL version 3.8.1.

=== Sohag Developer ===

[http://sohag-developer.com/ Sohag Developer]

Gnu/Linux Windows (Other OS can compile from source code).

Build a powerful database applications following few steps using Sohag Developer .
Sohag Developer currently supports PostgreSQL database and has a set of generators that generates (Qt/C++ code and ui forms - PHP web applications uses web forms and bootstrap framework ) to manipulate the data in the database tables or views.

=== TOra, an Oracle tool with some PostgreSQL support ===

http://tora.sf.net/

Linux & Windows

Admin

An Oracle database administration interface, with limited ability to browse PostgreSQL databases (tables, views, and functions only). I'm told that if you have the Oracle libraries, Tora's sophisticated function editor will work for PostgreSQL as well. Developed by Henrik Johnson as a Quest Toad clone. (JMB 11.2002)

== Proprietary ==

=== SQLGate ===

https://www.sqlgate.com/product/download

Windows

SQLGate is a simple but powerful IDE for multiple Database including PostgreSQL.

* Powerful Data Grid and ERD

* Multiple SQL Execution

* Auto-Complete

* Intuitive UI/UX

* Multiple Themes

* Fast processing speed

Use SQLGate to maximize your productivity!

=== dbForge Studio for PostgreSQL ===

https://www.devart.com/dbforge/postgresql/studio/

PostgreSQL GUI tool for managing and developing databases and objects. The IDE for PostgreSQL allows users to create, develop, and execute queries, edit and adjust the code to your requirements in a convenient and user-friendly interface. It comes in two editions - Standard and Express (free).

Key features:
* SQL Development
* Database Explorer
* Data Editor
* Data Export and Import
* Pivot Table
* Master-Detail Browser
* Data Reports

=== PSequel ===

http://www.psequel.com/

OS X Yosemite only, free, "Sequel Pro" inspired.

=== EMS SQL Manager for PostgreSQL Freeware ===

http://www.sqlmanager.net/en/tools/free

Windows

EMS SQL Manager for PostgreSQL Freeware (EMS SQL Manager Lite for PostgreSQL) is an excellent and easy-to-use freeware graphical tool for PostgreSQL database administration. It has the minimal required set of tools for those users who are new to PostgreSQL server and need only its basic functionality.
EMS SQL Manager for PostgreSQL Freeware allows you to work with servers, databases and schemas, view, edit, search, group, sort and filter any data stored in a database, create and execute SQL queries with powerful SQL editor, handle multiple selected objects at a time and much more.

=== Marshal SQL Utility ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1756

Windows

The Marshal SQL Utility is a generic cross database utility with batch execution capabilities. It allows you to test ODBC connections, browse database schemas, discover tables, views and columns.

Key features of Marshal SQL Utility:

* Execute any query supported by your database server
* Execute batches of queries
* Discover tables and views in your database
* Discover columns for a selected table or view
* Supports BLOBS and CLOBS
* Save your results to file
* Use any ODBC compliant database such as PostgreSQL.

=== RISE PHP for PostgreSQL code generator ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1888

Windows

The RISE PHP for PostgreSQL code generator renders PHP source code for database access. Model your information and programming interfaces in the free RISE Editor and generate your code. The generated code implements the classes and methods corresponding to the information interfaces specified in the RISE model. This includes classes for database access and, optionally, classes implementing SOAP/JSON web services and proxy classes assisting the implementation of a PHP SOAP client.

=== RISE - Model Driven Development using ERD / UML ===

http://www.risetobloome.com

Windows

RISE is a free software suite for model driven information system development. Use a single source RISE model to generate your entire information solution including database, web services and documentation. Boost development throughput and improve quality and maintainability!

The RISE user experience is based on a project concept, similar to that of most integrated development environments. The user works with resources and drawings that are part of a single development project.

RISE supports a fully graphical approach to information modeling and system engineering, using ERD (Entity Relationship Diagram) as well as UML (Unified Modeling Language). This includes drag-and-drop of entities, their attributes and relations, as well as of views and entire web services.

RISE supports graphic editing of complex objects such as views and orchestrated methods. RISE automatically safeguards the combination process, thus, assuring a technically correct result.

RISE provides several ways to generate code from the model; directly to file, via the RISE Server or as an Internet service. RISE provides code generators for the database layer (SQL/DDL) as well as for the server side application layer (web services and persistent classes). All database scripts are incremental allowing you to install and maintain any number of databases from a single model.

Feature list
http://www.risetobloome.com/Page_1_S.aspx?ITEM=1355

=== WaveMaker Ajax GUI Design Tool ===

http://www.wavemaker.com/

Windows, Macintosh, Linux

WaveMaker is an Ajax-based GUI design tool for Postgres. WaveMaker is built using itself! WaveMaker generates a standard Java WAR file based on Spring, Hibernate and Dojo. WaveMaker supports Postgres schema creation and import and includes a visual query editor.

=== AnySQL Maestro ===

http://www.sqlmaestro.com/products/anysql/maestro/

Windows

AnySQL Maestro is a freeware tool for administering any database engine (PostgreSQL, SQL Server, Oracle, MySQL, MS Access, etc.), which is accessible via ODBC driver or OLE DB provider. Includes Database Designer, Visual Query Builder, BLOB Viewer/Editor, SQL Editor, Data export/import and other features.

=== TeamPostgreSQL ===

http://www.teampostgresql.com

browser-based, webserver included

AJAX/JavaScript-powered web interface for PostgreSQL administration. Browse, maintain and create data and database objects from anywhere, in the web browser. Supports SSH for both the web interface and the database connections. Rich interface with tabbed SQL editor with auto-completion, inline row-editing widgets, click-through foreign key navigation between rows and tables, 'favorites' management for commonly used scripts, and more.

Installers available for Windows, Mac and Linux, alternatively download a simple cross-platform archive that runs anywhere with simple script.

=== Postgres Compare ===

[[File:Postgres_compare.png|thumb|left|frameless]]

https://www.postgrescompare.com/

Windows, Mac & Linux

A comprehensive tool for identifying the differences between databases and generating an update script to synchronize them. Postgres Compare reads the system catalogs to determine the structure of the database and compares it to another to find the changes. Generate SQL and deploy the alterations, save snapshots for later. Automate the process via the command line.

Alpha build available now https://www.postgrescompare.com/downloads

<div style="clear:both;"></div>

=== JetBrains IDEs - DataGrip, IntelliJ IDEA, PHPStorm, PyCharm, RubyMine, etc ... ===

http://www.jetbrains.com/

Windows, Mac OS X, Linux

JetBrains has a dedicated SQL IDE — DataGrip which can connect to PostgreSQL as well. It provides code completion, multi cursors, local query history, navigation, refactorings and language injection support.
https://www.jetbrains.com/datagrip/

Other JetBrains Products, for example, PHPStorm, have built-in database plugin, and it has the same functionality as DataGrip.

After you configured the data sources of your project, you can easily create tables, foreign keys, indexes much easier than usual, because the IDE is very smart; for example by foreign keys it automatically sets the name of the key and the related columns. For me, it is so far the best experience by creating a basic database schema. Even with editable EER models was it slower...
By the settings of [http://goo.gl/TuqiPRpantun romantis terbaru] your data source you can configure the SQL dialect of your database. After that, if you want to add stored procedures or triggers, you will have code completion which is favorable too. So I think JetBrains products speed up your work if you exactly know what you want, and how can you make it.

For any JetBrains IDE, there is a free license for open source projects. For enterprise usage there is a 30 days trial, after that, you can buy a personal or proprietary license which is very cheap compared to other products.

For PyCharm (even the Community Edition) you can install the free third-party plugin [http://confluence.jetbrains.com/display/CONTEST/Database+Navigator Database Navigator] (Settings -> IDE Settings -> Plugins). It appears to deliver the same functionality described above for PHPStorm. You will get a new menu DB Navigator, left to the Help menu.

=== TablePlus ===

https://tableplus.io/

macOS

A modern, native tool with an elegant UI that allows you to simultaneously manage multiple databases, including PostgreSQL.

* True native built.

* Workspace supports multiple tabs, multiple windows

* Powerful SQL editor with full features: auto syntax highlight, auto-suggestion, split pane, favorite and history.

* Data Filter & Sorting, import & export

* Full-dark theme & modern shortcut

With plugin system, you can be able to write your own new features to work with database per your needs (export charts, pretty json…).

=== SQLPro for Postgres ===

http://www.hankinsoft.com/SQLProPostgres

Mac OS X 10.8 and above

Features:
* 100% native OS X app with a clean and simple to use interface.
* Query editor with syntax highlighting and autocomplete.
* Support for multiple result set execution.
* History feature, displaying your last ten executed queries.
* Primary key detection for inline result set modifications.
* Custom theme support allowing developers to work with style.

=== Postico ===

https://eggerapps.at/postico/

Mac OS X

Postico is a fully native Mac app for connecting to your PostgreSQL server. It supports encrypted connections via SSL and SSH to PostgreSQL 8.0 and later, including Amazon Redshift.

Postico has a powerful table content editor with in-cell editing and form-based row editing in a sidebar. You can quickly filter tables by keywords or even complex SQL expressions.

There's also a table structure editor for editing columns, types, default values, foreign keys, check constraints etc.

Finally, there's a convenient SQL Query Editor with support for query history and syntax highlighting. It also has convenience features like auto-indent and shortcuts for comment line etc.

=== SEQUEL for PostgreSQL ===

http://www.sequel.tech

macOS

SEQUEL for PostgreSQL is a professional DB administration and management tool, with extremely intuitive and feature-rich GUI that makes it the best assistant tool for developers and admins. SEQUEL is lightweight, fast and powerful that it can significantly simplify the DB management process. For those who cannot live without a CLI, SEQUEL offers a powerful Query Editor with syntax highlight, autocomplete and a Console log view that is always visible, so you can monitor the communication with your databases. It includes:

* Database management forms for Schema, Table, Index, Foreign key, Trigger, Rule, Sequence, Collation, Domain, Enum type, Tablespace and Language objects with full parameters support
* Assistant info views for Object information, Actions, Help, and Documentation
* Jump bar for quick objects selection and navigation
* Taskbar with multi-task monitoring support
* Console log view
* Syntax highlight, autocomplete, current and selection query execution and explain, line numbering and working statement detection
* Direct editing in the results view, query results explanation
* Powerful Field editor
* Transaction based database updates
* Code preview and Content editing

=== dbForge Data Compare for PostgreSQL ===

http://www.devart.com/dbforge/postgresql/datacompare/

Microsoft Windows 2000/XP/2003/Vista and Windows 7, 8, 10

'''dbForge Data Compare for PostgreSQL''' by '''Devart''' is a tool for table data comparison and synchronization. When using PostgreSQL data compare tool developer can detect data differences in compared PostgreSQL tables; generate data synchronization script and execute it to eliminate all these differences.

'''Key features:'''

* Identify the differences between two databases
* Compare separate tables or table groups by table name mask
* Compare tables with different structure
* Generate a report embodying data diff and save it for further analysis
* Sync data in tables and views in full or in part
* Generate SQL script for database synchronization
* Organize database synchronization according to the schedule

=== Full Convert ===

https://www.spectralcore.com/fullconvert

Database conversion and synchronization between PostgreSQL and Microsoft Access, dBase, FoxPro, Microsoft Excel, Firebird, Interbase, MySQL, Oracle, Paradox, Microsoft SQL Server, SQL Server, SQL Server Azure, SQL Server Compact(SQLCE), SQLite, Delimited text files (CSV), XML and many more via ODBC.

=== Replicator Pro ===

https://www.spectralcore.com/replicator

Replicator allows table data comparison and sync - even with heterogeneous databases. It is unique in the fact it can replicate changes only even if source is non-relational (CSV, DBF, Excel documents, Paradox...). Replicator has a built-in scheduler for easy periodic change replication.

=== Nucleon Database Master for PostgreSQL and Others ===

Nucleon Database Master is a modern, powerful, intuitive, easy to use and all in one PostgreSQL MongoDB, Oracle, DB2, Informix, Ingres, SQL Server, SQL Azure, MySQL, FireBird, SQLite client application with a consistent interface that simplifies managing, querying, editing, visualizing, designing and [http://mitraharga.blogspot.co.uk/2014/09/harga-tablet-pc-axioo.htmlharga tablet axioo] reporting relational and schema-free (NoSQL) database systems. You can connect any database system via ODBC and OleDB connections.Using Database Master, you can execute SQL, LINQ, JSON queries or you can create, edit and delete all database objects such as tables, views, procedures, columns, indexes, collections, and triggers. You can execute SQL queries and scripts, view and edit table data including BLOBs (Image, Text or any file), represent tables and its relations as an ER(Entity Relationship) diagram.

Info:
http://www.nucleonsoftware.com/
Windows, other platforms via WINE
Admin

=== DBTools Manager ===

http://www.dbtools.com.br

Windows

Admin

Freeware, available for PostgreSQL and MySQL, allows managing all aspects of the database: db, table, triggers, functions, etc. Includes import/export wizards to migrate data and structure to/from other database engines. Developed by DBTools Software.

=== PgManager ===

http://www.ems-hitech.com/pgmanager

Windows, Linux version just released

Admin

Basically a proprietary, more powerful version of PGAdmin II or PGAccess. Adds support for trigger and constraint editing, metadata logging, and query monitoring. Also includes multiple-format data import/export tools, which are also available on their own for Linux. Developed by EMS Hitech. (JMB 4.2003).

=== DeZign for Databases ===

http://www.datanamic.com

Windows

ERD

DeZign is a database development tool using an entity relationship diagram. It visually supports the layout of the entities and relations and automatically generates SQL schemas for most leading databases including PostgreSQL.

=== Case Studio 2 / Toad Data Modeler ===

http://www.casestudio.com/enu/index.aspx

Windows

ERD

Commenter 1: I just downloaded the trial version, so far it looks really promising and claims to support PostgreSQL. Handles reverse engineering of existing databases, and has a really nice interface for setting up tables, relationships etc. You can get a lite or full version. The description from the website... Professional database modeling tool for various databases. CASE Studio 2 includes following key features:

LITE version features + Reverse Engineering from various database systems Version Manager Data Flow Diagrams Definition of user-defined variables Large COM interface Users, User groups and User permission support and many more.

Case Studio was acquired, and renamed 'Toad Data Modeler'.

Commenter 2: I've used the licensed version before and after the name change. PostgreSQL support is excellent.

=== PostgreSQL PHP Generator ===

http://www.sqlmaestro.com/products/postgresql/phpgenerator/

Windows

PostgreSQL PHP Generator is a freeware but powerful PostgreSQL GUI frontend that allows you to generate high-quality PHP scripts for the selected tables, views and queries for the further working with these objects through the web.

=== pgEdit ===

http://pgedit.com

Macintosh
pgEdit is a high-performance SQL editor and development environment designed specifically for PostgreSQL relational databases. pgEdit features include SQL syntax coloring, direct source code execution, PHP support, integrated documentation, and extensive customizable editing facilities.

pgEdit uses psql, the interactive terminal application included with every PostgreSQL installation. This makes it easy to develop with pgEdit and then transfer your work to any PostgreSQL installation for maintenance and production tasks.

pgEdit is a native application for both Macintosh and Windows. It does not use Java or require installation of external libraries. You have the option of using the version of psql included with pgEdit or a different version installed anywhere on your hard drive.

=== RazorSQL ===

http://www.razorsql.com/

Macintosh/Windows/Linux/Solaris

RazorSQL is an SQL query tool, database browser, SQL editor, and database administration tool that supports PostgreSQL and any other JDBC or ODBC compliant database. Some of the major features are tools for creating, dropping, and altering objects such as tables, views, indexes, triggers, functions, users, and databases; a programming editor that supports 20 different programming languages; import and export tools; auto column and table lookup; and a query builder, query scheduler, and SQL formatter.

=== MicroOLAP Database Designer ===

http://www.microolap.com/products/database/postgresql-designer/

Windows ODBC

Database Designer for PostgreSQL is an easy CASE tool with an intuitive graphical interface allowing you to build a clear and effective database structure visually, see the complete picture (diagram) representing all the tables, references between them, views, stored procedures and other objects. Then you can easily generate a physical database on a server, modify it according to any changes you made to the diagram using fast ALTER statements.

=== Import / Export and synchronization tools for PostgreSQL ===

http://convertdb.com/postgresql

Microsoft Windows 8 / 7 / Vista / XP / 2000 / NT.
The software is able to connect to remote PostgreSQL 9.x/7.4 located on Linux, Solaris, Mac OS X, and Windows.

ConvertDB cross-database migration tools assist in data conversion and synchronization among PostgreSQL, MySQL, MS SQL Server, MS Windows SQL Azure, and MS Access databases

* 1 Million of records can be transferred in 5-10 minutes.
* Bi-directional synchronization between PostgreSQL, MS SQL, MySQL and Oracle
* Scheduling migration and synchronization jobs.

=== dbForge Studio for PostgreSQL ===

https://www.devart.com/dbforge/postgresql/studio/

Microsoft Windows 7, 8, 10

'''dbForge Studio for PostgreSQL''' is a brand new tool for PostgreSQL databases development, management, and editing process enjoyable and easy by Devart. The PostgreSQL IDE allows users to create, develop, and execute queries, edit and adjust the code to the requirements in a convenient and UI. The tool provides the PostgreSQL data editor functionality for queries customization and property window for the viewing all the required information of PostgreSQL database objects.

'''Key features:'''

* Code Completion helps to improve code quality when creating and editing queries with List Members, Parameter Info, Quick Info, Complete Word.
* Object Explorer for easy navigation through the object tree. You can retrieve data from the database on a single SQL document, truncate a table, select Properties to view some information on the object.
* Data Editor for management settings of tables, such as adjust column width, set either paginal or auto-search mode by default. Color and format rows and cells using a rich set of fonts and size. The tool has predefined data type formats to meet your own needs.

=== dotConnect for PostgreSQL ===

https://www.devart.com/dotconnect/postgresql/

Windows

'''dotConnect for PostgreSQL''', formerly known as PostgreSQLDirect .NET, is an enhanced ORM enabled data provider for PostgreSQL that builds on ADO.NET technology to present a complete solution for developing PostgreSQL-based database applications. It introduces new approaches for designing application architecture, boosts productivity, and leverages database applications.

'''Key features:'''

* Direct Mode
* Database Application Development Extension
* PostgreSQL Advanced Features Support
* Optimized Code
* ORM Support
* BIS Support

=== PostgreSQL Data Access Components ===

Windows

https://www.devart.com/pgdac/

PostgreSQL Data Access Components (PgDAC) is a library of components that provides native connectivity to PostgreSQL from Delphi, C++Builder, Lazarus (and Free Pascal) on Windows, Mac OS X, iOS, Android, Linux, and FreeBSD for both 32-bit and 64-bit platforms. PgDAC is designed to help programmers develop really lightweight, faster and cleaner PostgreSQL database applications without deploying any additional libraries.

Native Connectivity to PostgreSQL
PgDAC is a complete replacement for standard PostgreSQL connectivity solutions and presents an efficient alternative to the Borland Database Engine (BDE) and standard dbExpress driver for access to PostgreSQL. It provides direct access to PostgreSQL without PostgreSQL Client.

=== ODBC Driver for PostgreSQL ===

https://www.devart.com/odbc/postgresql/

Windows

Devart ODBC Driver for PostgreSQL provides high-performance and feature-rich connectivity solution for ODBC-based applications to access PostgreSQL databases from Windows, both 32-bit and 64-bit. Full support for standard ODBC API functions and data types implemented in our driver makes the interaction of your database applications with PostgreSQL fast, easy and extremely handy.

=== Excel Add-in for PostgreSQL ===

https://www.devart.com/excel-addins/postgresql.html

Windows

Devart Excel Add-in for PostgreSQL allows you to quickly and easily connect Microsoft Excel to PostgreSQL, load data from PostgreSQL to Excel, instantly refresh data in an Excel workbook from the database, edit these data, and save them back to PostgreSQL. It enables you to work with PostgreSQL data like with usual Excel worksheets, easily perform data cleansing and de-duplication, and apply all the Excel's powerful data processing and analysis capabilities to these data.

=== EMS Database Management Tools for PostgreSQL ===

http://www.sqlmanager.net/en/products/postgresql

Windows

PostgreSQL Tools Products Family:

* [http://www.sqlmanager.net/en/products/studio/postgresql SQL Management Studio for PostgreSQL] - a single workbench for administering PostgreSQL databases, managing database schema and objects as well as for database design, migration, extraction, query building, data import, export, and database comparison.

* [http://www.sqlmanager.net/en/products/postgresql/manager SQL Manager for PostgreSQL] - high performance graphical tool for PostgreSQL database administration and development. It makes creating and editing PostgreSQL database objects easy and fast, and allows you to run SQL scripts, visually design databases, build SQL queries, extract, print and search metadata, import and export PostgreSQL database data and much more.

* [http://www.sqlmanager.net/en/products/postgresql/dataexport Data Export for PostgreSQL] - tool to export PostgreSQL database data quickly to any of 19 available formats, including MS Access, MS Excel, MS Word, RTF, HTML, TXT, ODF and more. Data Export for PostgreSQL has a [http://aurora-ndut.blogspot.fr/2013/10/kata-kata-lucu.htmlkata kata lucu] friendly wizard, which allows you to set various options of PostgreSQL export process visually and a command-line utility to automate your PostgreSQL export jobs using the configuration file.

* [http://www.sqlmanager.net/en/products/postgresql/dataimport Data Import for PostgreSQL] - tool to import data to PostgreSQL tables from MS Excel 97-2007, MS Access, DBF, TXT, CSV, MS Word 2007, RTF, ODF and HTML files. This utility allows you to quickly import data to one or several PostgreSQL tables or views at once, save all PostgreSQL import parameters set on current wizard session, use special batch insert mode to import PostgreSQL data at the maximum possible speed and much more.

* [http://www.sqlmanager.net/en/products/postgresql/datapump Data Pump for PostgreSQL] - migration tool for converting databases and importing table data from an ADO-compatible source (e.g. MS Access, MS SQL database or any other database with ADO support) to PostgreSQL databases.

* [http://www.sqlmanager.net/en/products/postgresql/datagenerator Data Generator for PostgreSQL] - tool for generating test data to PostgreSQL database tables. The utility can help you to simulate the database production environment and allows you to populate several PostgreSQL database tables with test data simultaneously, define tables for generating data, set value ranges, control a wide variety of generation parameters for each field type and much more.

* [http://www.sqlmanager.net/en/products/postgresql/dbcomparer DB Comparer for PostgreSQL] - a tool for comparing PostgreSQL database schemas and discovering differences in their structures. You can view all the differences in compared database objects and execute an automatically generated script to synchronize structure of PostgreSQL databases and eliminate these differences.

* [http://www.sqlmanager.net/en/products/postgresql/extract DB Extract for PostgreSQL] - easy-to-use tool for creating PostgreSQL database backups in a form of SQL scripts. This database script utility allows you to save metadata of all PostgreSQL database objects as well as PostgreSQL table data as database snapshots.

* [http://www.sqlmanager.net/en/products/postgresql/query SQL Query for PostgreSQL] - a useful tool that lets you quickly and simply build SQL queries to PostgreSQL databases. Visual PostgreSQL query building, as well as direct editing of a query text, is available.

* [http://www.sqlmanager.net/en/products/postgresql/datacomparer Data Comparer for PostgreSQL] - tool for PostgreSQL data comparison and synchronization. Using this utility you can view all the differences in compared PostgreSQL tables and execute an automatically generated script to eliminate these differences.

=== SQL Maestro Group products for PostgreSQL ===

http://www.sqlmaestro.com/products/postgresql/

Windows

[http://www.sqlmaestro.com SQL Maestro Group] offers a number of tools for PostgreSQL.

* [http://www.sqlmaestro.com/products/postgresql/maestro/ PostgreSQL Maestro] allows you to create, edit, copy, drop and dump database objects easy and fast. You can also design your database as ER diagram, build queries visually, execute SQL queries and scripts, debug PL/pgSQL functions, view and edit data including BLOBs, represent data as diagrams, export and import data to/from most popular file formats, analyze your data summarized into multidimensional views and hierarchies (OLAP cubes), manage PostgreSQL roles, users, groups and privileges, and use a lot of other admin tools designed for making your work with PostgreSQL database server comfortable and efficient.

* [http://www.sqlmaestro.com/products/postgresql/datawizard/ PostgreSQL Data Wizard] provides you with a number of easy-to-use wizards to transfer any database to PostgreSQL, export data from PostgreSQL tables, views and queries to most popular formats, and import data from various sources into PostgreSQL tables.

* [http://www.sqlmaestro.com/products/postgresql/codefactory/ PostgreSQL Code Factory] is a GUI tool aimed at the SQL queries and scripts development.

* [http://www.sqlmaestro.com/products/postgresql/datasync/ PostgreSQL Data Sync] is a powerful and easy-to-use tool for database contents comparison and synchronization.

* [http://www.sqlmaestro.com/products/postgresql/phpgenerator/ PostgreSQL PHP Generator Professional] is a frontend that allows you to generate high-quality PHP applications for your database in a few mouse clicks.

SQL Maestro Group also produces similar tools for MySQL, Oracle, MS SQL Server, SQLite, Firebird, DB2, SQL Anywhere, and MaxDB.

=== Datanamic DataDiff for PostgreSQL ===

http://www.datanamic.com/datadiff-for-postgresql/

Windows

Datanamic DataDiff for PostgreSQL is a utility for data comparison and synchronization. Compare data for selected tables in two databases, view differences and publish changes quickly and safely. Flexible comparison and synchronization settings will enable you to set up a customized comparison key and to select tables and fields for comparison and for synchronization.
DB Data Difftective can be used for data migrations, verification of (corrupt) data, data auditing etc.

=== Datanamic SchemaDiff for PostgreSQL ===

http://www.datanamic.com/schemadiff-for-postgresql/index.html

Windows

Datanamic SchemaDiff for PostgreSQL is a tool for comparison and synchronization of database schemas. It allows you to compare and synchronize tables, views, functions, sequences (generators), stored procedures, triggers and constraints between two databases.

=== DB MultiRun PostgreSQL Edition ===

http://www.datanamic.com/multirun/index.html

Windows

DB MultiRun is a simple tool to execute multiple SQL scripts on multiple databases quickly.
Define a list of databases, add SQL scripts to execute on these databases and click "execute" to run those scripts on the databases in the list. The multi-threaded execution of the SQL scripts makes it complete the task fast. After execution of the scripts, you can examine the results of the executed scripts on each database.

=== SQLPro ===

http://www.vive.net/products/sqlpro.htm

Windows

SqlPro is an easy to use database GUI tool for six popular databases (Oracle, MySQL, PostgreSQL, SQL Server, SQLite, and Access). One IDE makes database administration and development faster and error free.
SQLPro Key Features: color-coding of the SQL, drag-and-drop of objects into the editor pane to save you from typing their names, retrieval of SQL code for things like stored procedures and triggers from the underlying database, and one-click creation of SELECT and INSERT statements. You can open, save and print SQL scripts.
SQLPro uses native drivers to connect to the databases (no ODBS or third party engines to install).

=== DB Doc ===

http://www.yohz.com/dbdoc_details.htm

Windows/Linux(Wine)

DB Doc helps you document your database structure and objects. Documents can be generated as PDF reports, HTML pages, Microsoft Word (docx) file, or a single compiled HTML file. The layout is fully customizable, and you can quickly view inter-object dependencies using hyperlinks.

DB Doc supports PostgreSQL 8.3 to 9.4.

=== SQL Blob Export ===

http://www.yohz.com/sbe_details.htm

Windows

SQL Blob Export exports unlimited images and files from your tables or queries in 5 simple steps.

=== SQL File Import ===

http://www.yohz.com/sfi_overview.htm

Windows

SQL File Import allows you to upload files, images, and other data into your database, without having to write any SQL statements. SQL File Import supports PostgreSQL, Firebird, MySQL, Oracle, SQLite, SQL Server, and various ODBC-supported databases (e.g. DB2 and PostgreSQL).

A scripting engine allows you to transform data before importing them into your database. A command line version is also included to allow you to perform unattended upload/import tasks.

=== SQL Image Viewer ===

http://www.yohz.com/siv_details.htm

Windows

SQL Image Viewer allows you to retrieve, view, convert and export images stored in Firebird, MySQL, Oracle, SQLite, SQL Server, and various ODBC-supported databases (e.g. DB2 and PostgreSQL). It supports the following image formats: BMP, GIF, JPG, PNG, PSD, and TIFF.

It also allows you to export binary data and recognises the following binary file types: PDF, MP3, WAV, 7Z, BZ2, GZ, RAR, ZIP, and has experimental support for DOC, PPT and XLS file types.

A command line version is also included to allow you to perform unattended scheduled exports of binary data.

=== SQL Multi Select ===

http://www.yohz.com/sms_details.htm

Windows

SQL Multi Select is a query tool that allows you to run multiple scripts on multiple servers with a single click. Result sets from different servers are consolidated into a single view, allowing for easy comparison and analysis.

=== SQLTool Pro Database Editor ===

http://www.sqltoolpro.com

Android

SQLTool Pro is a professional Android SQL editor for MySQL, SQL Server, PostgreSQL, Sybase, and Oracle Databases.

=== SSIS Data Flow Components for PostgreSQL ===

https://www.devart.com/ssis/

Windows

'''Devart SSIS Data Flow Components for PostgreSQL''' allow you to integrate database and cloud data via SQL Server Integration Services (SSIS).

Devart SSIS Data Flow Components provide easy to set up cost-effective data integration using SSIS ETL engine. They provide high performance data loading, convenient component editors, SQL support for cloud data sources and lots of data source specific features.

=== DbVisualizer ===

http://www.dbvis.com/

Windows/OS X/Linux/UNIX

DbVisualizer is a feature rich, intuitive multi-database tool for developers, database administrators, and increasingly for advanced analysts providing a single powerful interface across a wide variety of operating systems. With its easy-to-use and clean interface, DbVisualizer has proven to be one of the most cost effective database tools available, yet to mention that it runs on all major operating systems and supports all major RDBMS that are available. Users only need to learn and master one application. DbVisualizer integrates transparently with the operating system being used.

[[Category:Tool]]
[[Category:General articles and guides]]

=== Valentina Studio (Free) ===

http://www.valentina-db.com/valentina-studio-overview

Windows/OS X/Linux/

Valentina Studio is a powerful PostgreSQL Database Server administration and development tool. It offers for free many advanced editors:
* Schema Editor with Tree and Column views
* Diagram Editor with reverse engineering
* SQL Editor with auto-completion, syntax-highlighting, recent and favorite queries, templates of commands, many result tab-panels, ...
* Data Editor with easy sorting and filtering of records without SQL, in-cell editing.
* Related Data Editor that allow s you to learn related records in different modes.
* Import/Export
* SQL dumps
* and so on ...

Valentina Studio PRO - adds additional advanced features as:
* Report Editor to developer reports based on Valentina Report Engine with datasources from PostgreSQL and other databases.
* Diagrams forward engineering
* SQL DIFF
* Data Transfer

[[Category:Tool]]

=== JackDB ===

http://www.jackdb.com/

Html5 Web Browser (Linux/Mac OS X/Windows)

JackDB is a database client that runs entirely in your web browser. There's no software to install locally so you can use it on Mac OS X, Linux, and Windows and it works on all major modern browsers (eg. Chrome, Firefox, IE, Safari, and Opera). It supports connecting to PostgreSQL, as well as MySQL, Oracle, and SQL Server databases.

Features:
* Html5 interface with no client installation
* Query editor with syntax highlighting
* Scrolling result sets
* Schema/Object browser
* SSL connections with certificate pinning
* Eliminates password sharing
* Two-factor authentication
* BLOB display (images and Html5 audio/video)

=== Tadpole DB Hub ===

https://github.com/hangum/TadpoleForDBTools/wiki

Tadpole DB Hub is Unified infrastructure tool, a various environment based interface for managing Apache Hive, Amazon RDS, CUBRID, MariaDB, MySQL, Oracle, SQLite, MSSQL, PostgreSQL and MongoDB databases. It enables you to handle typical DB over the World Wide Web.

Features:
* Intuitive web interface (Safari, Chrome, IE 10, Firefox)
* User Management (Admin, Manager, User)
* Select, Insert, Update, Delete
* Download query result
* SQL Syntax Highlighting
* SQL Formatting
* SQL Statement <-> Java, PHP String Literal Each Convert
* SQL Assist
* Execute SQL Statement
* SQL Result Set to CSV
* SQL History And Export text
* Generate SQL Statement (Select, Insert, Update, Delete, Table, View, Index, Procedure, Function, Trigger)
* Generate ER Diagram (Auto Layout)

=== Vertabelo ===

http://www.vertabelo.com

Vertabelo is an online database designer working under Chrome. It free to use for smaller projects and have a proprietary version for larger database projects.

Features:
* Intuitive HTML5 web interface (Chrome)
* OS independent
* Sharing DB model with team members
* Support for PostgreSQL, MySQL, Oracle, MS SQL Server, DB2, SQLite, HSQLDB,
* Model versioning
* Dynamic/Visual search
* Live model validation
* Reverse engineering

=== pgModeler ===

PostgreSQL Database Modeler

http://pgmodeler.com.br

PostgreSQL Database Modeler, or simply, pgModeler is an open source tool for modeling databases that merges the classical concepts of entity-relationship diagrams with specific features that only PostgreSQL implements. The pgModeler translates the models created by the user to SQL code and apply them onto database clusters from version 8.0 to 9.1. $3.50 per copy as of 2014/04/09.

=== GenMyModel ===

https://www.genmymodel.com

GenMyModel is an online modeling tool supporting [http://www.genmymodel.com/database-diagram-online database modeling]. It is free to use for smaller projects and have a proprietary version for larger database projects.

Features:
* Intuitive HTML5 web interface (Chrome, Firefox, Safari, Internet Explorer)
* OS independent
* Instant sharing and collaboration
* Customizable SQL generators
* Model versioning
* Live model validation

=== DBHawk ===

http://www.datasparc.com/

Web Browser (Linux/Mac OS X/Windows)

DBHawk is a web based SQL tool and reporting software designed for PostgreSQL, Oracle, SQL Server and other databases. Its easy to deploy and use.

Features:
* Web based interface with no client installation
* Advanced Query editor with syntax highlighting and multi tabs results
* Online visual query builder
* Online SQL Report Builder
* Online SQL Job Scheduler
* Export results to html, csv, pdf, google docs, amazon s3
* SQL Auditing and Security
* Schema/Object browser
* SQL and data snippet sharing
* Blob data viewer and editor

=== Datazenit ===

https://datazenit.com/

Windows, Mac OS X, Linux

Datazenit is a cross-platform PostgreSQL and MySQL GUI with data grid, schema builder and interactive charts.
It also has query builder, raw query editor with auto-complete, team collaboration features like connection, query and chart sharing among team members.

=== EDB Postgres Enterprise Manager ===

http://www.enterprisedb.com/products/postgres-enterprise-manager

Windows, Mac OS X, Linux

Postgres Enterprise Manager is the only solution available today that allows you to intelligently manage, monitor, and tune large scale Postgres installations from a single GUI console.

Monitoring features include: server auto-discovery, over 225 pre-configured ready to run probes, custom probes, alert management, personalized alerts, remote monitoring, versatile charting, custom dashboards and web client.

DBA tools include: database objects management, Postgres Expert (best practice configuration settings), Audit Manager, Log Manager, Log Analysis Expert, Capacity Manager and Team Support.

Developer tools include: Query Tool, Data Grid, SQL Profiler, SQL Debugger and Import tools.

Tuning tools include: At-A-Glance performance dashboards, Tuning Wizard, Performance Diagnostics and Index Advisor.

=== ClusterControl by Severalnines ===

https://severalnines.com/product/clustercontrol/for_postgresql

ClusterControl is an all-inclusive open source database management system that allows you to deplore, monitor, manage and scale your database environments. ClusterControl provides the basic functionality you need to get PostgreSQL up-and-running using our deployment wizard, monitoring and basic management abilities like automatic failover, backups, and restores.

* Point and Click Replication Deployments - ClusterControl allows you to easily deploy and configure master/slave replication PostgreSQL instances.
* Advanced Performance Monitoring - ClusterControl monitors queries and detects anomalies with built-in alerts.
* Automated Failover Handling - ClusterControl detects master failures and automatically promotes a new master
* Database Automation - ClusterControl lets you manage configurations, schedule, and restore backups.

=== Database Tour Pro ===

https://www.databasetour.net

Database Tour Pro is a database tool with built-in report builder for Windows. It works with different types of relational databases including PostgreSQL.

Key features:

* Creating tables.
* Viewing and editing data.
* Several ways to print data.
* Built-in report engine and visual report designer with templates, expressions, preview etc.
* Expression builder for report and export expressions.
* Building and executing SQL queries. Support for execution of multi statement SQL scripts. Syntax highlighting in SQL editor. Support for parameterized SQL queries.
* Enhanced database grids, which allow to view and manipulate the data in the most convenient way, including sorting by clicking column header, changing row heights, resizing columns etc.
* Command line support for executing queries, opening tables, export-import operations, loading reports etc. with logging the performed operations.
* Searching and replacing text in database with ability to choose fields, record range etc.
* Importing data to table from another table or a query.
* Exporting data from open table or query to file(s) like text, CSV, HTML, XLSX, XML, RTF, DBF or to another relational database.
* Copying data to clipboard.
* Viewing and editing Blob data, such as large text and graphics.
* Tools for editing text fields (trimming, changing case of symbols, replacing text).
* Customized data view (font, background).
* Conditional formatting data in database grids and reports.
* Ability to control transactions.

=== Reportizer ===

https://www.reportizer.net

Reportizer is a database reporting tool, which allows easy creating, modifying, and printing database reports from different types of databases, including PostgreSQL. Reports can be edited in convenient visual report builder or in text mode. It supports calculating fields, multi-column reports, expressions, grouping, displaying images etc. Reportizer can export reports to HTML, XLSX, image, or internal format. There is an ability to load and print reports from command line. Reportizer allows to manage report collections, which can be held either in files or in database tables.

=== Exportizer Pro ===

https://www.vlsoftware.net/exportizer-pro/

Exportizer Pro is a database export tool, which can work with PostgreSQL database either as source or destination. It allows to export data to database, file, clipboard, or printer.
* Possible sources: ODBC data sources, files of DB (Paradox), DBF (dBase, FoxPro), MDB, ACCDB, XLS, XLSX, GDB, IB, FDB, HTML, UDL, DBC, TXT, CSV types, databases specified by ADO connection strings, and databases like Oracle, SQL Server, Postgresql, DB2, Informix, SQLite, Interbase etc.
* Possible destinations: file formats like text, CSV, XLS, XLSX, RTF, XML, HTML, PDF, DBF, SLK, SQL script, and relational database of any supported type.
* It is possible to export all or selected tables from an open database at once.
* Exportizer Pro can automatically detect the most known image types (JPEG, PNG, GIF, BMP, ICO) in BLOB fields and export them, for example, to HTML or XLSX.
* There is an ability to specify the source-to-target field mappings.
* Export operations can be performed either via the program interface or via command line.

=== TiCodeX SQL Schema Compare ===

https://www.ticodex.com/

TiCodeX SQL Schema Compare is a tools that allows database administrators to compare multiple database schema in order to manage versioning. 
The software runs on Windows, Linux and Mac and supports Microsoft SQL (MS-SQL), MySQL, PostgreSQL, Azure SQL and MS-SQL on Amazon RDS.

'''Key Features:'''
* Runs on Windows, Linux and MacOS
* Localized in English, German and Italian
* Compare changes between two SQL Database schemas (as example from development to test to production)
* View database differences and explore schema changes to see what's going on
* Automatically create full database migration scripts
* Securely save database and server login details

=== pgMustard ===

https://www.pgmustard.com/

pgMustard is a performance tool for PostgreSQL that provides a user interface for your EXPLAIN ANALYSE output, as well as tips on what to do to speed up your query.

Features:
* Quickly see the slowest operations
* Code snippets to tie operations back to the query
* Tips to speed up your query💡
* Does the arithmetic for you (including wall clock times)
* Explanations of operation types and key concepts
* Links to relevant documentation and blog posts

Requirements:
* JSON format plans
* Any supported version of PostgreSQL
* English language only
* Web application, no installation required

== No longer Supported/Developed ==

* OpenOffice postgresql SDBC Driver. no work on the project since 2010; last version was a beta. http://www.openoffice.org/dba/drivers/postgresql/index.html
* RedHat: hasn't been refreshed since Pg 8.4. http://sources.redhat.com/rhdb

Community Guide to PostgreSQL GUI Tools

2019-05-04T17:21:26Z

Dfetter: /* DBeaver */

{{Languages}}

== Alternate Guides ==

Another detailed summary from 2009 is available at
[http://www.postgresonline.com/journal/index.php?/archives/133-Database-Administration,-Reporting,-and-Light-application-development.html Database Administration, Reporting, and Light application development]

== Open Source / Free Software ==

=== pgAdmin 4 ===

http://www.pgadmin.org/

MS Windows, GNU/Linux, FreeBSD, Mac OS X, OpenBSD, Solaris

Admin

pgAdmin III is an Open Source management tool for PostgreSQL databases. Features full Unicode support, fast, multithreaded query and data editing tools and support for all PostgreSQL object types.

pgAdmin III is bundled with the Windows installer, and you can use that such a client to administer a remote server on another OS. Note that binary packages for platforms like RPM don't show up in every point release, you currently have to go back to v1.8.0 to get the last full set of packages.

Free Administration Centre for the PostgreSQL database. Includes a graphical administration interface, an SQL query tool, a procedural code editor and much more. pgAdmin III is designed to answer the needs of most users, from writing simple SQL queries to developing complex databases. The graphical interface supports all PostgreSQL features and makes administration easy. Available in more than 30 languages and for several operating systems.

=== phpPgAdmin ===

http://sourceforge.net/projects/phppgadmin

browser-based, requires webserver

Admin

Similar to the ever-popular phpMyAdmin, enhanced for PostgreSQL, supports browsing and modification of most types of PostgreSQL database objects, plus execution of ad-hoc queries. Maintained by (who else?) the phpPgAdmin team. (JMB 11.2002).

phpPgAdmin (and the required Apache and PHP packages) may be easily installed using Stack Builder if you are running a one-click-installer PostgreSQL distribution.

=== SQuirrel ===

http://www.squirrelsql.org/

Platforms that support Java

Admin

SQuirreL SQL Client is a graphical Java program that will allow you to view the structure of a JDBC compliant database, browse the data in tables, issue SQL commands etc. The minimum version of Java supported is 1.8.x as of SQuirreL version 3.8.1.

=== Adminer ===

http://www.adminer.org

browser-based, requires webserver

Adminer (formerly phpMinAdmin) is a full-featured database management tool written in PHP. Conversely to phpMyAdmin, it consist of a single file ready to deploy to the target server. Adminer is available for MySQL, PostgreSQL, SQLite, MS SQL and Oracle.

=== Libre Office ===

http://www.libreoffice.org/download/3-5-new-features-and-fixes/

New native driver for PostgreSQL databases (for versions > 8.4 - support for version 8.4 will be included in LibreOffice 3.5.1).

=== GNOME-DB ===

http://www.gnome-db.org

Linux, Unix

Admin

Database administration/user tool for GNOME, based on libgda/libgnomedb, which are a complete database-independent access layer for UNIX systems, with support for PostgreSQL, MySQL, Sybase, MS SQL Server, Oracle, Interbase/Firebird, MS Access files, xBase.

=== TOra, an Oracle tool with some PostgreSQL support ===

http://tora.sf.net/

Linux & Windows

Admin

An Oracle database administration interface, with limited ability to browse PostgreSQL databases (tables, views, and functions only). I'm told that if you have the Oracle libraries, Tora's sophisticated function editor will work for PostgreSQL as well. Developed by Henrik Johnson as a Quest Toad clone. (JMB 11.2002)

=== Kexi ===

http://www.kexi-project.org/

Kexi is part of the Calligra Suite and is released under the GNU General Public License (GPL) and LGPL.

available for
FreeBSD & Linux, Apple, Windows, (Android)

=== SQL Workbench/J ===

http://www.sql-workbench.net

Java (multi-platform)

An OpenSource SQL GUI tool similar to Squirrel. Data can be edited directly in the result set. It has strong support for exporting and importing data between databases using its own SQL command extension. It can be used in GUI mode or as a console application. All SQL Workbench specific commands can also be run in batch mode to automate export and import task. It supports schema comparison ("diff") and copying data between databases.

=== Druid III ===

http://druid.sourceforge.net/

Java (multi-platform)

The druid is a tools that allows users to create databases in a graphical way. The user can add tables, fields, folders to group tables and can modify most of the database options that follow the SQL-92 standard. In addition to sql options, the user can document each table and each field with HTML information. Once the database is created, the druid can generate:

* HTML documentation: for all tables, with browsing facilities
* PDF documentation: for all tables
* Java classes: (one class for each table) that contain tables' constants (such as fields size) plus java code added by the user
* A data dictionarythat contains all tables and fields present in the database
* SQL script which contains all table definitions that can be piped to the DBMS
* And much more info...

=== Power*Architect ===

http://www.sqlpower.ca/page/architect

Java (multi-platform)

Power*Architect is an ERD modelling tool that is based on Java and JDBC. Support for forward and reverse engineering PostgreSQL databases is supported. It's OpenSource with a GPL license.

=== RISE PostgreSQL code generator ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1889

Windows

The RISE PostgreSQL code generator generates native PL/pgSQL scripts. Model your information in the free RISE Editor and generate your database script. The script incrementally updates the tables, columns, indexes and constraints in the database to match the RISE model. Once the database model is updated, the views defined in the RISE model are created in the database and possible default data, entered in the model, is inserted.

=== Open Source CMS ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=2017

Windows

The CMS is a free Visual Studio 2010 solution template with a set of projects providing a complete Content Management System (CMS) based on RISE Visual Modeling with model, full source, sample site and DB-scripts for PostgreSQL, MySQL and SQL Server.

It’s a complete ready-to-run Visual Studio solution with model, source code and web clients. It illustrates how to use RISE, how to implement a SOA backend and how to build RIA frontends.

=== DBeaver ===

https://dbeaver.io

Eclipse/Java (multi-platform)

Eclipse-based environment, supporting many SQL databases from different vendors, as well as few NoSQL ones (Cassandra, etc).
Good query editor with syntax highlighting, completion and autosave.
Editing of query results. SSH tunneling support. Tons of other cool features.
Quite good, but not 100% perfect PostgreSQL support (yet?). Regularly updated, as of 2018.

=== OmniDB ===

https://github.com/OmniDB/OmniDB

Linux, Windows and macOS

Open source full-featured tool for database management. Currently supports PostgreSQL (9.3 - 11), Oracle (11g - 18c), MySQL (5.6 - 8.0) and MariaDB (10.1 - 10.3). More RDBMS support coming soon, including the ability of converting databases from any supported RDBMS to PostgreSQL and back.

=== Postbird ===

https://github.com/paxa/postbird

MacOs

Open source, desktop application to manage your local or remote PostgreSQL databases.

=== Sohag Developer ===
[http://sohag-developer.com/ Sohag Developer]

Gnu/Linux Windows (Other OS can compile from source code).

Build a powerful database applications following few steps using Sohag Developer .
Sohag Developer currently supports PostgreSQL database and has a set of generators that generates (Qt/C++ code and ui forms - PHP web applications uses web forms and bootstrap framework ) to manipulate the data in the database tables or views.

=== PASH-Viewer: PostgreSQL Active Session History Viewer ===
https://github.com/dbacvetkov/PASH-Viewer

Java (multi-platform).

Open-source software which provides graphical view of active session history and help you to answer questions like "What wait events were taking most time?", "Which sessions were taking most time?", "Which queries were taking most time and what were they doing?". It also supports Active Session History extension by pgsentinel.

=== pgrights: GUI for PostgreSQL roles, privileges and policies ===
https://github.com/apsavin/pgrights

MacOS (based on Electron, so versions for other OS can be build from source code).

Open-source software which allows you to easely understand what can do (and what can't) a PostgreSQL user with a table's data. In other words, it's a viewer of results of GRANT commands and row-level security rules applied for a particular table and for a particular role.

== Proprietary ==

=== SQLGate ===

https://www.sqlgate.com/product/download

Windows

SQLGate is a simple but powerful IDE for multiple Database including PostgreSQL.

* Powerful Data Grid and ERD

* Multiple SQL Execution

* Auto-Complete

* Intuitive UI/UX

* Multiple Themes

* Fast processing speed

Use SQLGate to maximize your productivity!

=== dbForge Studio for PostgreSQL ===

https://www.devart.com/dbforge/postgresql/studio/

PostgreSQL GUI tool for managing and developing databases and objects. The IDE for PostgreSQL allows users to create, develop, and execute queries, edit and adjust the code to your requirements in a convenient and user-friendly interface. It comes in two editions - Standard and Express (free).

Key features:
* SQL Development
* Database Explorer
* Data Editor
* Data Export and Import
* Pivot Table
* Master-Detail Browser
* Data Reports

=== PSequel ===

http://www.psequel.com/

OS X Yosemite only, free, "Sequel Pro" inspired.

=== EMS SQL Manager for PostgreSQL Freeware ===

http://www.sqlmanager.net/en/tools/free

Windows

EMS SQL Manager for PostgreSQL Freeware (EMS SQL Manager Lite for PostgreSQL) is an excellent and easy-to-use freeware graphical tool for PostgreSQL database administration. It has the minimal required set of tools for those users who are new to PostgreSQL server and need only its basic functionality.
EMS SQL Manager for PostgreSQL Freeware allows you to work with servers, databases and schemas, view, edit, search, group, sort and filter any data stored in a database, create and execute SQL queries with powerful SQL editor, handle multiple selected objects at a time and much more.

=== Marshal SQL Utility ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1756

Windows

The Marshal SQL Utility is a generic cross database utility with batch execution capabilities. It allows you to test ODBC connections, browse database schemas, discover tables, views and columns.

Key features of Marshal SQL Utility:

* Execute any query supported by your database server
* Execute batches of queries
* Discover tables and views in your database
* Discover columns for a selected table or view
* Supports BLOBS and CLOBS
* Save your results to file
* Use any ODBC compliant database such as PostgreSQL.

=== RISE PHP for PostgreSQL code generator ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1888

Windows

The RISE PHP for PostgreSQL code generator renders PHP source code for database access. Model your information and programming interfaces in the free RISE Editor and generate your code. The generated code implements the classes and methods corresponding to the information interfaces specified in the RISE model. This includes classes for database access and, optionally, classes implementing SOAP/JSON web services and proxy classes assisting the implementation of a PHP SOAP client.

=== RISE - Model Driven Development using ERD / UML ===

http://www.risetobloome.com

Windows

RISE is a free software suite for model driven information system development. Use a single source RISE model to generate your entire information solution including database, web services and documentation. Boost development throughput and improve quality and maintainability!

The RISE user experience is based on a project concept, similar to that of most integrated development environments. The user works with resources and drawings that are part of a single development project.

RISE supports a fully graphical approach to information modeling and system engineering, using ERD (Entity Relationship Diagram) as well as UML (Unified Modeling Language). This includes drag-and-drop of entities, their attributes and relations, as well as of views and entire web services.

RISE supports graphic editing of complex objects such as views and orchestrated methods. RISE automatically safeguards the combination process, thus, assuring a technically correct result.

RISE provides several ways to generate code from the model; directly to file, via the RISE Server or as an Internet service. RISE provides code generators for the database layer (SQL/DDL) as well as for the server side application layer (web services and persistent classes). All database scripts are incremental allowing you to install and maintain any number of databases from a single model.

Feature list
http://www.risetobloome.com/Page_1_S.aspx?ITEM=1355

=== WaveMaker Ajax GUI Design Tool ===

http://www.wavemaker.com/

Windows, Macintosh, Linux

WaveMaker is an Ajax-based GUI design tool for Postgres. WaveMaker is built using itself! WaveMaker generates a standard Java WAR file based on Spring, Hibernate and Dojo. WaveMaker supports Postgres schema creation and import and includes a visual query editor.

=== AnySQL Maestro ===

http://www.sqlmaestro.com/products/anysql/maestro/

Windows

AnySQL Maestro is a freeware tool for administering any database engine (PostgreSQL, SQL Server, Oracle, MySQL, MS Access, etc.), which is accessible via ODBC driver or OLE DB provider. Includes Database Designer, Visual Query Builder, BLOB Viewer/Editor, SQL Editor, Data export/import and other features.

=== TeamPostgreSQL ===

http://www.teampostgresql.com

browser-based, webserver included

AJAX/JavaScript-powered web interface for PostgreSQL administration. Browse, maintain and create data and database objects from anywhere, in the web browser. Supports SSH for both the web interface and the database connections. Rich interface with tabbed SQL editor with auto-completion, inline row-editing widgets, click-through foreign key navigation between rows and tables, 'favorites' management for commonly used scripts, and more.

Installers available for Windows, Mac and Linux, alternatively download a simple cross-platform archive that runs anywhere with simple script.

=== Postgres Compare ===

[[File:Postgres_compare.png|thumb|left|frameless]]

https://www.postgrescompare.com/

Windows, Mac & Linux

A comprehensive tool for identifying the differences between databases and generating an update script to synchronize them. Postgres Compare reads the system catalogs to determine the structure of the database and compares it to another to find the changes. Generate SQL and deploy the alterations, save snapshots for later. Automate the process via the command line.

Alpha build available now https://www.postgrescompare.com/downloads

<div style="clear:both;"></div>

=== JetBrains IDEs - DataGrip, IntelliJ IDEA, PHPStorm, PyCharm, RubyMine, etc ... ===

http://www.jetbrains.com/

Windows, Mac OS X, Linux

JetBrains has a dedicated SQL IDE — DataGrip which can connect to PostgreSQL as well. It provides code completion, multi cursors, local query history, navigation, refactorings and language injection support.
https://www.jetbrains.com/datagrip/

Other JetBrains Products, for example, PHPStorm, have built-in database plugin, and it has the same functionality as DataGrip.

After you configured the data sources of your project, you can easily create tables, foreign keys, indexes much easier than usual, because the IDE is very smart; for example by foreign keys it automatically sets the name of the key and the related columns. For me, it is so far the best experience by creating a basic database schema. Even with editable EER models was it slower...
By the settings of [http://goo.gl/TuqiPRpantun romantis terbaru] your data source you can configure the SQL dialect of your database. After that, if you want to add stored procedures or triggers, you will have code completion which is favorable too. So I think JetBrains products speed up your work if you exactly know what you want, and how can you make it.

For any JetBrains IDE, there is a free license for open source projects. For enterprise usage there is a 30 days trial, after that, you can buy a personal or proprietary license which is very cheap compared to other products.

For PyCharm (even the Community Edition) you can install the free third-party plugin [http://confluence.jetbrains.com/display/CONTEST/Database+Navigator Database Navigator] (Settings -> IDE Settings -> Plugins). It appears to deliver the same functionality described above for PHPStorm. You will get a new menu DB Navigator, left to the Help menu.

=== TablePlus ===

https://tableplus.io/

macOS

A modern, native tool with an elegant UI that allows you to simultaneously manage multiple databases, including PostgreSQL.

* True native built.

* Workspace supports multiple tabs, multiple windows

* Powerful SQL editor with full features: auto syntax highlight, auto-suggestion, split pane, favorite and history.

* Data Filter & Sorting, import & export

* Full-dark theme & modern shortcut

With plugin system, you can be able to write your own new features to work with database per your needs (export charts, pretty json…).

=== SQLPro for Postgres ===

http://www.hankinsoft.com/SQLProPostgres

Mac OS X 10.8 and above

Features:
* 100% native OS X app with a clean and simple to use interface.
* Query editor with syntax highlighting and autocomplete.
* Support for multiple result set execution.
* History feature, displaying your last ten executed queries.
* Primary key detection for inline result set modifications.
* Custom theme support allowing developers to work with style.

=== Postico ===

https://eggerapps.at/postico/

Mac OS X

Postico is a fully native Mac app for connecting to your PostgreSQL server. It supports encrypted connections via SSL and SSH to PostgreSQL 8.0 and later, including Amazon Redshift.

Postico has a powerful table content editor with in-cell editing and form-based row editing in a sidebar. You can quickly filter tables by keywords or even complex SQL expressions.

There's also a table structure editor for editing columns, types, default values, foreign keys, check constraints etc.

Finally, there's a convenient SQL Query Editor with support for query history and syntax highlighting. It also has convenience features like auto-indent and shortcuts for comment line etc.

=== SEQUEL for PostgreSQL ===

http://www.sequel.tech

macOS

SEQUEL for PostgreSQL is a professional DB administration and management tool, with extremely intuitive and feature-rich GUI that makes it the best assistant tool for developers and admins. SEQUEL is lightweight, fast and powerful that it can significantly simplify the DB management process. For those who cannot live without a CLI, SEQUEL offers a powerful Query Editor with syntax highlight, autocomplete and a Console log view that is always visible, so you can monitor the communication with your databases. It includes:

* Database management forms for Schema, Table, Index, Foreign key, Trigger, Rule, Sequence, Collation, Domain, Enum type, Tablespace and Language objects with full parameters support
* Assistant info views for Object information, Actions, Help, and Documentation
* Jump bar for quick objects selection and navigation
* Taskbar with multi-task monitoring support
* Console log view
* Syntax highlight, autocomplete, current and selection query execution and explain, line numbering and working statement detection
* Direct editing in the results view, query results explanation
* Powerful Field editor
* Transaction based database updates
* Code preview and Content editing

=== dbForge Data Compare for PostgreSQL ===

http://www.devart.com/dbforge/postgresql/datacompare/

Microsoft Windows 2000/XP/2003/Vista and Windows 7, 8, 10

'''dbForge Data Compare for PostgreSQL''' by '''Devart''' is a tool for table data comparison and synchronization. When using PostgreSQL data compare tool developer can detect data differences in compared PostgreSQL tables; generate data synchronization script and execute it to eliminate all these differences.

'''Key features:'''

* Identify the differences between two databases
* Compare separate tables or table groups by table name mask
* Compare tables with different structure
* Generate a report embodying data diff and save it for further analysis
* Sync data in tables and views in full or in part
* Generate SQL script for database synchronization
* Organize database synchronization according to the schedule

=== Full Convert ===

https://www.spectralcore.com/fullconvert

Database conversion and synchronization between PostgreSQL and Microsoft Access, dBase, FoxPro, Microsoft Excel, Firebird, Interbase, MySQL, Oracle, Paradox, Microsoft SQL Server, SQL Server, SQL Server Azure, SQL Server Compact(SQLCE), SQLite, Delimited text files (CSV), XML and many more via ODBC.

=== Replicator Pro ===

https://www.spectralcore.com/replicator

Replicator allows table data comparison and sync - even with heterogeneous databases. It is unique in the fact it can replicate changes only even if source is non-relational (CSV, DBF, Excel documents, Paradox...). Replicator has a built-in scheduler for easy periodic change replication.

=== Nucleon Database Master for PostgreSQL and Others ===

Nucleon Database Master is a modern, powerful, intuitive, easy to use and all in one PostgreSQL MongoDB, Oracle, DB2, Informix, Ingres, SQL Server, SQL Azure, MySQL, FireBird, SQLite client application with a consistent interface that simplifies managing, querying, editing, visualizing, designing and [http://mitraharga.blogspot.co.uk/2014/09/harga-tablet-pc-axioo.htmlharga tablet axioo] reporting relational and schema-free (NoSQL) database systems. You can connect any database system via ODBC and OleDB connections.Using Database Master, you can execute SQL, LINQ, JSON queries or you can create, edit and delete all database objects such as tables, views, procedures, columns, indexes, collections, and triggers. You can execute SQL queries and scripts, view and edit table data including BLOBs (Image, Text or any file), represent tables and its relations as an ER(Entity Relationship) diagram.

Info:
http://www.nucleonsoftware.com/
Windows, other platforms via WINE
Admin

=== DBTools Manager ===

http://www.dbtools.com.br

Windows

Admin

Freeware, available for PostgreSQL and MySQL, allows managing all aspects of the database: db, table, triggers, functions, etc. Includes import/export wizards to migrate data and structure to/from other database engines. Developed by DBTools Software.

=== PgManager ===

http://www.ems-hitech.com/pgmanager

Windows, Linux version just released

Admin

Basically a proprietary, more powerful version of PGAdmin II or PGAccess. Adds support for trigger and constraint editing, metadata logging, and query monitoring. Also includes multiple-format data import/export tools, which are also available on their own for Linux. Developed by EMS Hitech. (JMB 4.2003).

=== DeZign for Databases ===

http://www.datanamic.com

Windows

ERD

DeZign is a database development tool using an entity relationship diagram. It visually supports the layout of the entities and relations and automatically generates SQL schemas for most leading databases including PostgreSQL.

=== Case Studio 2 / Toad Data Modeler ===

http://www.casestudio.com/enu/index.aspx

Windows

ERD

Commenter 1: I just downloaded the trial version, so far it looks really promising and claims to support PostgreSQL. Handles reverse engineering of existing databases, and has a really nice interface for setting up tables, relationships etc. You can get a lite or full version. The description from the website... Professional database modeling tool for various databases. CASE Studio 2 includes following key features:

LITE version features + Reverse Engineering from various database systems Version Manager Data Flow Diagrams Definition of user-defined variables Large COM interface Users, User groups and User permission support and many more.

Case Studio was acquired, and renamed 'Toad Data Modeler'.

Commenter 2: I've used the licensed version before and after the name change. PostgreSQL support is excellent.

=== PostgreSQL PHP Generator ===

http://www.sqlmaestro.com/products/postgresql/phpgenerator/

Windows

PostgreSQL PHP Generator is a freeware but powerful PostgreSQL GUI frontend that allows you to generate high-quality PHP scripts for the selected tables, views and queries for the further working with these objects through the web.

=== pgEdit ===

http://pgedit.com

Macintosh
pgEdit is a high-performance SQL editor and development environment designed specifically for PostgreSQL relational databases. pgEdit features include SQL syntax coloring, direct source code execution, PHP support, integrated documentation, and extensive customizable editing facilities.

pgEdit uses psql, the interactive terminal application included with every PostgreSQL installation. This makes it easy to develop with pgEdit and then transfer your work to any PostgreSQL installation for maintenance and production tasks.

pgEdit is a native application for both Macintosh and Windows. It does not use Java or require installation of external libraries. You have the option of using the version of psql included with pgEdit or a different version installed anywhere on your hard drive.

=== RazorSQL ===

http://www.razorsql.com/

Macintosh/Windows/Linux/Solaris

RazorSQL is an SQL query tool, database browser, SQL editor, and database administration tool that supports PostgreSQL and any other JDBC or ODBC compliant database. Some of the major features are tools for creating, dropping, and altering objects such as tables, views, indexes, triggers, functions, users, and databases; a programming editor that supports 20 different programming languages; import and export tools; auto column and table lookup; and a query builder, query scheduler, and SQL formatter.

=== MicroOLAP Database Designer ===

http://www.microolap.com/products/database/postgresql-designer/

Windows ODBC

Database Designer for PostgreSQL is an easy CASE tool with an intuitive graphical interface allowing you to build a clear and effective database structure visually, see the complete picture (diagram) representing all the tables, references between them, views, stored procedures and other objects. Then you can easily generate a physical database on a server, modify it according to any changes you made to the diagram using fast ALTER statements.

=== Import / Export and synchronization tools for PostgreSQL ===

http://convertdb.com/postgresql

Microsoft Windows 8 / 7 / Vista / XP / 2000 / NT.
The software is able to connect to remote PostgreSQL 9.x/7.4 located on Linux, Solaris, Mac OS X, and Windows.

ConvertDB cross-database migration tools assist in data conversion and synchronization among PostgreSQL, MySQL, MS SQL Server, MS Windows SQL Azure, and MS Access databases

* 1 Million of records can be transferred in 5-10 minutes.
* Bi-directional synchronization between PostgreSQL, MS SQL, MySQL and Oracle
* Scheduling migration and synchronization jobs.

=== dbForge Studio for PostgreSQL ===

https://www.devart.com/dbforge/postgresql/studio/

Microsoft Windows 7, 8, 10

'''dbForge Studio for PostgreSQL''' is a brand new tool for PostgreSQL databases development, management, and editing process enjoyable and easy by Devart. The PostgreSQL IDE allows users to create, develop, and execute queries, edit and adjust the code to the requirements in a convenient and UI. The tool provides the PostgreSQL data editor functionality for queries customization and property window for the viewing all the required information of PostgreSQL database objects.

'''Key features:'''

* Code Completion helps to improve code quality when creating and editing queries with List Members, Parameter Info, Quick Info, Complete Word.
* Object Explorer for easy navigation through the object tree. You can retrieve data from the database on a single SQL document, truncate a table, select Properties to view some information on the object.
* Data Editor for management settings of tables, such as adjust column width, set either paginal or auto-search mode by default. Color and format rows and cells using a rich set of fonts and size. The tool has predefined data type formats to meet your own needs.

=== dotConnect for PostgreSQL ===

https://www.devart.com/dotconnect/postgresql/

Windows

'''dotConnect for PostgreSQL''', formerly known as PostgreSQLDirect .NET, is an enhanced ORM enabled data provider for PostgreSQL that builds on ADO.NET technology to present a complete solution for developing PostgreSQL-based database applications. It introduces new approaches for designing application architecture, boosts productivity, and leverages database applications.

'''Key features:'''

* Direct Mode
* Database Application Development Extension
* PostgreSQL Advanced Features Support
* Optimized Code
* ORM Support
* BIS Support

=== PostgreSQL Data Access Components ===

Windows

https://www.devart.com/pgdac/

PostgreSQL Data Access Components (PgDAC) is a library of components that provides native connectivity to PostgreSQL from Delphi, C++Builder, Lazarus (and Free Pascal) on Windows, Mac OS X, iOS, Android, Linux, and FreeBSD for both 32-bit and 64-bit platforms. PgDAC is designed to help programmers develop really lightweight, faster and cleaner PostgreSQL database applications without deploying any additional libraries.

Native Connectivity to PostgreSQL
PgDAC is a complete replacement for standard PostgreSQL connectivity solutions and presents an efficient alternative to the Borland Database Engine (BDE) and standard dbExpress driver for access to PostgreSQL. It provides direct access to PostgreSQL without PostgreSQL Client.

=== ODBC Driver for PostgreSQL ===

https://www.devart.com/odbc/postgresql/

Windows

Devart ODBC Driver for PostgreSQL provides high-performance and feature-rich connectivity solution for ODBC-based applications to access PostgreSQL databases from Windows, both 32-bit and 64-bit. Full support for standard ODBC API functions and data types implemented in our driver makes the interaction of your database applications with PostgreSQL fast, easy and extremely handy.

=== Excel Add-in for PostgreSQL ===

https://www.devart.com/excel-addins/postgresql.html

Windows

Devart Excel Add-in for PostgreSQL allows you to quickly and easily connect Microsoft Excel to PostgreSQL, load data from PostgreSQL to Excel, instantly refresh data in an Excel workbook from the database, edit these data, and save them back to PostgreSQL. It enables you to work with PostgreSQL data like with usual Excel worksheets, easily perform data cleansing and de-duplication, and apply all the Excel's powerful data processing and analysis capabilities to these data.

=== EMS Database Management Tools for PostgreSQL ===

http://www.sqlmanager.net/en/products/postgresql

Windows

PostgreSQL Tools Products Family:

* [http://www.sqlmanager.net/en/products/studio/postgresql SQL Management Studio for PostgreSQL] - a single workbench for administering PostgreSQL databases, managing database schema and objects as well as for database design, migration, extraction, query building, data import, export, and database comparison.

* [http://www.sqlmanager.net/en/products/postgresql/manager SQL Manager for PostgreSQL] - high performance graphical tool for PostgreSQL database administration and development. It makes creating and editing PostgreSQL database objects easy and fast, and allows you to run SQL scripts, visually design databases, build SQL queries, extract, print and search metadata, import and export PostgreSQL database data and much more.

* [http://www.sqlmanager.net/en/products/postgresql/dataexport Data Export for PostgreSQL] - tool to export PostgreSQL database data quickly to any of 19 available formats, including MS Access, MS Excel, MS Word, RTF, HTML, TXT, ODF and more. Data Export for PostgreSQL has a [http://aurora-ndut.blogspot.fr/2013/10/kata-kata-lucu.htmlkata kata lucu] friendly wizard, which allows you to set various options of PostgreSQL export process visually and a command-line utility to automate your PostgreSQL export jobs using the configuration file.

* [http://www.sqlmanager.net/en/products/postgresql/dataimport Data Import for PostgreSQL] - tool to import data to PostgreSQL tables from MS Excel 97-2007, MS Access, DBF, TXT, CSV, MS Word 2007, RTF, ODF and HTML files. This utility allows you to quickly import data to one or several PostgreSQL tables or views at once, save all PostgreSQL import parameters set on current wizard session, use special batch insert mode to import PostgreSQL data at the maximum possible speed and much more.

* [http://www.sqlmanager.net/en/products/postgresql/datapump Data Pump for PostgreSQL] - migration tool for converting databases and importing table data from an ADO-compatible source (e.g. MS Access, MS SQL database or any other database with ADO support) to PostgreSQL databases.

* [http://www.sqlmanager.net/en/products/postgresql/datagenerator Data Generator for PostgreSQL] - tool for generating test data to PostgreSQL database tables. The utility can help you to simulate the database production environment and allows you to populate several PostgreSQL database tables with test data simultaneously, define tables for generating data, set value ranges, control a wide variety of generation parameters for each field type and much more.

* [http://www.sqlmanager.net/en/products/postgresql/dbcomparer DB Comparer for PostgreSQL] - a tool for comparing PostgreSQL database schemas and discovering differences in their structures. You can view all the differences in compared database objects and execute an automatically generated script to synchronize structure of PostgreSQL databases and eliminate these differences.

* [http://www.sqlmanager.net/en/products/postgresql/extract DB Extract for PostgreSQL] - easy-to-use tool for creating PostgreSQL database backups in a form of SQL scripts. This database script utility allows you to save metadata of all PostgreSQL database objects as well as PostgreSQL table data as database snapshots.

* [http://www.sqlmanager.net/en/products/postgresql/query SQL Query for PostgreSQL] - a useful tool that lets you quickly and simply build SQL queries to PostgreSQL databases. Visual PostgreSQL query building, as well as direct editing of a query text, is available.

* [http://www.sqlmanager.net/en/products/postgresql/datacomparer Data Comparer for PostgreSQL] - tool for PostgreSQL data comparison and synchronization. Using this utility you can view all the differences in compared PostgreSQL tables and execute an automatically generated script to eliminate these differences.

=== SQL Maestro Group products for PostgreSQL ===

http://www.sqlmaestro.com/products/postgresql/

Windows

[http://www.sqlmaestro.com SQL Maestro Group] offers a number of tools for PostgreSQL.

* [http://www.sqlmaestro.com/products/postgresql/maestro/ PostgreSQL Maestro] allows you to create, edit, copy, drop and dump database objects easy and fast. You can also design your database as ER diagram, build queries visually, execute SQL queries and scripts, debug PL/pgSQL functions, view and edit data including BLOBs, represent data as diagrams, export and import data to/from most popular file formats, analyze your data summarized into multidimensional views and hierarchies (OLAP cubes), manage PostgreSQL roles, users, groups and privileges, and use a lot of other admin tools designed for making your work with PostgreSQL database server comfortable and efficient.

* [http://www.sqlmaestro.com/products/postgresql/datawizard/ PostgreSQL Data Wizard] provides you with a number of easy-to-use wizards to transfer any database to PostgreSQL, export data from PostgreSQL tables, views and queries to most popular formats, and import data from various sources into PostgreSQL tables.

* [http://www.sqlmaestro.com/products/postgresql/codefactory/ PostgreSQL Code Factory] is a GUI tool aimed at the SQL queries and scripts development.

* [http://www.sqlmaestro.com/products/postgresql/datasync/ PostgreSQL Data Sync] is a powerful and easy-to-use tool for database contents comparison and synchronization.

* [http://www.sqlmaestro.com/products/postgresql/phpgenerator/ PostgreSQL PHP Generator Professional] is a frontend that allows you to generate high-quality PHP applications for your database in a few mouse clicks.

SQL Maestro Group also produces similar tools for MySQL, Oracle, MS SQL Server, SQLite, Firebird, DB2, SQL Anywhere, and MaxDB.

=== Datanamic DataDiff for PostgreSQL ===

http://www.datanamic.com/datadiff-for-postgresql/

Windows

Datanamic DataDiff for PostgreSQL is a utility for data comparison and synchronization. Compare data for selected tables in two databases, view differences and publish changes quickly and safely. Flexible comparison and synchronization settings will enable you to set up a customized comparison key and to select tables and fields for comparison and for synchronization.
DB Data Difftective can be used for data migrations, verification of (corrupt) data, data auditing etc.

=== Datanamic SchemaDiff for PostgreSQL ===

http://www.datanamic.com/schemadiff-for-postgresql/index.html

Windows

Datanamic SchemaDiff for PostgreSQL is a tool for comparison and synchronization of database schemas. It allows you to compare and synchronize tables, views, functions, sequences (generators), stored procedures, triggers and constraints between two databases.

=== DB MultiRun PostgreSQL Edition ===

http://www.datanamic.com/multirun/index.html

Windows

DB MultiRun is a simple tool to execute multiple SQL scripts on multiple databases quickly.
Define a list of databases, add SQL scripts to execute on these databases and click "execute" to run those scripts on the databases in the list. The multi-threaded execution of the SQL scripts makes it complete the task fast. After execution of the scripts, you can examine the results of the executed scripts on each database.

=== SQLPro ===

http://www.vive.net/products/sqlpro.htm

Windows

SqlPro is an easy to use database GUI tool for six popular databases (Oracle, MySQL, PostgreSQL, SQL Server, SQLite, and Access). One IDE makes database administration and development faster and error free.
SQLPro Key Features: color-coding of the SQL, drag-and-drop of objects into the editor pane to save you from typing their names, retrieval of SQL code for things like stored procedures and triggers from the underlying database, and one-click creation of SELECT and INSERT statements. You can open, save and print SQL scripts.
SQLPro uses native drivers to connect to the databases (no ODBS or third party engines to install).

=== DB Doc ===

http://www.yohz.com/dbdoc_details.htm

Windows/Linux(Wine)

DB Doc helps you document your database structure and objects. Documents can be generated as PDF reports, HTML pages, Microsoft Word (docx) file, or a single compiled HTML file. The layout is fully customizable, and you can quickly view inter-object dependencies using hyperlinks.

DB Doc supports PostgreSQL 8.3 to 9.4.

=== SQL Blob Export ===

http://www.yohz.com/sbe_details.htm

Windows

SQL Blob Export exports unlimited images and files from your tables or queries in 5 simple steps.

=== SQL File Import ===

http://www.yohz.com/sfi_overview.htm

Windows

SQL File Import allows you to upload files, images, and other data into your database, without having to write any SQL statements. SQL File Import supports PostgreSQL, Firebird, MySQL, Oracle, SQLite, SQL Server, and various ODBC-supported databases (e.g. DB2 and PostgreSQL).

A scripting engine allows you to transform data before importing them into your database. A command line version is also included to allow you to perform unattended upload/import tasks.

=== SQL Image Viewer ===

http://www.yohz.com/siv_details.htm

Windows

SQL Image Viewer allows you to retrieve, view, convert and export images stored in Firebird, MySQL, Oracle, SQLite, SQL Server, and various ODBC-supported databases (e.g. DB2 and PostgreSQL). It supports the following image formats: BMP, GIF, JPG, PNG, PSD, and TIFF.

It also allows you to export binary data and recognises the following binary file types: PDF, MP3, WAV, 7Z, BZ2, GZ, RAR, ZIP, and has experimental support for DOC, PPT and XLS file types.

A command line version is also included to allow you to perform unattended scheduled exports of binary data.

=== SQL Multi Select ===

http://www.yohz.com/sms_details.htm

Windows

SQL Multi Select is a query tool that allows you to run multiple scripts on multiple servers with a single click. Result sets from different servers are consolidated into a single view, allowing for easy comparison and analysis.

=== SQLTool Pro Database Editor ===

http://www.sqltoolpro.com

Android

SQLTool Pro is a professional Android SQL editor for MySQL, SQL Server, PostgreSQL, Sybase, and Oracle Databases.

=== SSIS Data Flow Components for PostgreSQL ===

https://www.devart.com/ssis/

Windows

'''Devart SSIS Data Flow Components for PostgreSQL''' allow you to integrate database and cloud data via SQL Server Integration Services (SSIS).

Devart SSIS Data Flow Components provide easy to set up cost-effective data integration using SSIS ETL engine. They provide high performance data loading, convenient component editors, SQL support for cloud data sources and lots of data source specific features.

=== DbVisualizer ===

http://www.dbvis.com/

Windows/OS X/Linux/UNIX

DbVisualizer is a feature rich, intuitive multi-database tool for developers, database administrators, and increasingly for advanced analysts providing a single powerful interface across a wide variety of operating systems. With its easy-to-use and clean interface, DbVisualizer has proven to be one of the most cost effective database tools available, yet to mention that it runs on all major operating systems and supports all major RDBMS that are available. Users only need to learn and master one application. DbVisualizer integrates transparently with the operating system being used.

[[Category:Tool]]
[[Category:General articles and guides]]

=== Valentina Studio (Free) ===

http://www.valentina-db.com/valentina-studio-overview

Windows/OS X/Linux/

Valentina Studio is a powerful PostgreSQL Database Server administration and development tool. It offers for free many advanced editors:
* Schema Editor with Tree and Column views
* Diagram Editor with reverse engineering
* SQL Editor with auto-completion, syntax-highlighting, recent and favorite queries, templates of commands, many result tab-panels, ...
* Data Editor with easy sorting and filtering of records without SQL, in-cell editing.
* Related Data Editor that allow s you to learn related records in different modes.
* Import/Export
* SQL dumps
* and so on ...

Valentina Studio PRO - adds additional advanced features as:
* Report Editor to developer reports based on Valentina Report Engine with datasources from PostgreSQL and other databases.
* Diagrams forward engineering
* SQL DIFF
* Data Transfer

[[Category:Tool]]

=== JackDB ===

http://www.jackdb.com/

Html5 Web Browser (Linux/Mac OS X/Windows)

JackDB is a database client that runs entirely in your web browser. There's no software to install locally so you can use it on Mac OS X, Linux, and Windows and it works on all major modern browsers (eg. Chrome, Firefox, IE, Safari, and Opera). It supports connecting to PostgreSQL, as well as MySQL, Oracle, and SQL Server databases.

Features:
* Html5 interface with no client installation
* Query editor with syntax highlighting
* Scrolling result sets
* Schema/Object browser
* SSL connections with certificate pinning
* Eliminates password sharing
* Two-factor authentication
* BLOB display (images and Html5 audio/video)

=== Tadpole DB Hub ===

https://github.com/hangum/TadpoleForDBTools/wiki

Tadpole DB Hub is Unified infrastructure tool, a various environment based interface for managing Apache Hive, Amazon RDS, CUBRID, MariaDB, MySQL, Oracle, SQLite, MSSQL, PostgreSQL and MongoDB databases. It enables you to handle typical DB over the World Wide Web.

Features:
* Intuitive web interface (Safari, Chrome, IE 10, Firefox)
* User Management (Admin, Manager, User)
* Select, Insert, Update, Delete
* Download query result
* SQL Syntax Highlighting
* SQL Formatting
* SQL Statement <-> Java, PHP String Literal Each Convert
* SQL Assist
* Execute SQL Statement
* SQL Result Set to CSV
* SQL History And Export text
* Generate SQL Statement (Select, Insert, Update, Delete, Table, View, Index, Procedure, Function, Trigger)
* Generate ER Diagram (Auto Layout)

=== Vertabelo ===

http://www.vertabelo.com

Vertabelo is an online database designer working under Chrome. It free to use for smaller projects and have a proprietary version for larger database projects.

Features:
* Intuitive HTML5 web interface (Chrome)
* OS independent
* Sharing DB model with team members
* Support for PostgreSQL, MySQL, Oracle, MS SQL Server, DB2, SQLite, HSQLDB,
* Model versioning
* Dynamic/Visual search
* Live model validation
* Reverse engineering

=== pgModeler ===

PostgreSQL Database Modeler

http://pgmodeler.com.br

PostgreSQL Database Modeler, or simply, pgModeler is an open source tool for modeling databases that merges the classical concepts of entity-relationship diagrams with specific features that only PostgreSQL implements. The pgModeler translates the models created by the user to SQL code and apply them onto database clusters from version 8.0 to 9.1. $3.50 per copy as of 2014/04/09.

=== GenMyModel ===

https://www.genmymodel.com

GenMyModel is an online modeling tool supporting [http://www.genmymodel.com/database-diagram-online database modeling]. It is free to use for smaller projects and have a proprietary version for larger database projects.

Features:
* Intuitive HTML5 web interface (Chrome, Firefox, Safari, Internet Explorer)
* OS independent
* Instant sharing and collaboration
* Customizable SQL generators
* Model versioning
* Live model validation

=== DBHawk ===

http://www.datasparc.com/

Web Browser (Linux/Mac OS X/Windows)

DBHawk is a web based SQL tool and reporting software designed for PostgreSQL, Oracle, SQL Server and other databases. Its easy to deploy and use.

Features:
* Web based interface with no client installation
* Advanced Query editor with syntax highlighting and multi tabs results
* Online visual query builder
* Online SQL Report Builder
* Online SQL Job Scheduler
* Export results to html, csv, pdf, google docs, amazon s3
* SQL Auditing and Security
* Schema/Object browser
* SQL and data snippet sharing
* Blob data viewer and editor

=== Datazenit ===

https://datazenit.com/

Windows, Mac OS X, Linux

Datazenit is a cross-platform PostgreSQL and MySQL GUI with data grid, schema builder and interactive charts.
It also has query builder, raw query editor with auto-complete, team collaboration features like connection, query and chart sharing among team members.

=== EDB Postgres Enterprise Manager ===

http://www.enterprisedb.com/products/postgres-enterprise-manager

Windows, Mac OS X, Linux

Postgres Enterprise Manager is the only solution available today that allows you to intelligently manage, monitor, and tune large scale Postgres installations from a single GUI console.

Monitoring features include: server auto-discovery, over 225 pre-configured ready to run probes, custom probes, alert management, personalized alerts, remote monitoring, versatile charting, custom dashboards and web client.

DBA tools include: database objects management, Postgres Expert (best practice configuration settings), Audit Manager, Log Manager, Log Analysis Expert, Capacity Manager and Team Support.

Developer tools include: Query Tool, Data Grid, SQL Profiler, SQL Debugger and Import tools.

Tuning tools include: At-A-Glance performance dashboards, Tuning Wizard, Performance Diagnostics and Index Advisor.

=== ClusterControl by Severalnines ===

https://severalnines.com/product/clustercontrol/for_postgresql

ClusterControl is an all-inclusive open source database management system that allows you to deplore, monitor, manage and scale your database environments. ClusterControl provides the basic functionality you need to get PostgreSQL up-and-running using our deployment wizard, monitoring and basic management abilities like automatic failover, backups, and restores.

* Point and Click Replication Deployments - ClusterControl allows you to easily deploy and configure master/slave replication PostgreSQL instances.
* Advanced Performance Monitoring - ClusterControl monitors queries and detects anomalies with built-in alerts.
* Automated Failover Handling - ClusterControl detects master failures and automatically promotes a new master
* Database Automation - ClusterControl lets you manage configurations, schedule, and restore backups.

=== Database Tour Pro ===

https://www.databasetour.net

Database Tour Pro is a database tool with built-in report builder for Windows. It works with different types of relational databases including PostgreSQL.

Key features:

* Creating tables.
* Viewing and editing data.
* Several ways to print data.
* Built-in report engine and visual report designer with templates, expressions, preview etc.
* Expression builder for report and export expressions.
* Building and executing SQL queries. Support for execution of multi statement SQL scripts. Syntax highlighting in SQL editor. Support for parameterized SQL queries.
* Enhanced database grids, which allow to view and manipulate the data in the most convenient way, including sorting by clicking column header, changing row heights, resizing columns etc.
* Command line support for executing queries, opening tables, export-import operations, loading reports etc. with logging the performed operations.
* Searching and replacing text in database with ability to choose fields, record range etc.
* Importing data to table from another table or a query.
* Exporting data from open table or query to file(s) like text, CSV, HTML, XLSX, XML, RTF, DBF or to another relational database.
* Copying data to clipboard.
* Viewing and editing Blob data, such as large text and graphics.
* Tools for editing text fields (trimming, changing case of symbols, replacing text).
* Customized data view (font, background).
* Conditional formatting data in database grids and reports.
* Ability to control transactions.

=== Reportizer ===

https://www.reportizer.net

Reportizer is a database reporting tool, which allows easy creating, modifying, and printing database reports from different types of databases, including PostgreSQL. Reports can be edited in convenient visual report builder or in text mode. It supports calculating fields, multi-column reports, expressions, grouping, displaying images etc. Reportizer can export reports to HTML, XLSX, image, or internal format. There is an ability to load and print reports from command line. Reportizer allows to manage report collections, which can be held either in files or in database tables.

=== Exportizer Pro ===

https://www.vlsoftware.net/exportizer-pro/

Exportizer Pro is a database export tool, which can work with PostgreSQL database either as source or destination. It allows to export data to database, file, clipboard, or printer.
* Possible sources: ODBC data sources, files of DB (Paradox), DBF (dBase, FoxPro), MDB, ACCDB, XLS, XLSX, GDB, IB, FDB, HTML, UDL, DBC, TXT, CSV types, databases specified by ADO connection strings, and databases like Oracle, SQL Server, Postgresql, DB2, Informix, SQLite, Interbase etc.
* Possible destinations: file formats like text, CSV, XLS, XLSX, RTF, XML, HTML, PDF, DBF, SLK, SQL script, and relational database of any supported type.
* It is possible to export all or selected tables from an open database at once.
* Exportizer Pro can automatically detect the most known image types (JPEG, PNG, GIF, BMP, ICO) in BLOB fields and export them, for example, to HTML or XLSX.
* There is an ability to specify the source-to-target field mappings.
* Export operations can be performed either via the program interface or via command line.

=== TiCodeX SQL Schema Compare ===

https://www.ticodex.com/

TiCodeX SQL Schema Compare is a tools that allows database administrators to compare multiple database schema in order to manage versioning. 
The software runs on Windows, Linux and Mac and supports Microsoft SQL (MS-SQL), MySQL, PostgreSQL, Azure SQL and MS-SQL on Amazon RDS.

'''Key Features:'''
* Runs on Windows, Linux and MacOS
* Localized in English, German and Italian
* Compare changes between two SQL Database schemas (as example from development to test to production)
* View database differences and explore schema changes to see what's going on
* Automatically create full database migration scripts
* Securely save database and server login details

=== pgMustard ===

https://www.pgmustard.com/

pgMustard is a performance tool for PostgreSQL that provides a user interface for your EXPLAIN ANALYSE output, as well as tips on what to do to speed up your query.

Features:
* Quickly see the slowest operations
* Code snippets to tie operations back to the query
* Tips to speed up your query💡
* Does the arithmetic for you (including wall clock times)
* Explanations of operation types and key concepts
* Links to relevant documentation and blog posts

Requirements:
* JSON format plans
* Any supported version of PostgreSQL
* English language only
* Web application, no installation required

== No longer Supported/Developed ==

* OpenOffice postgresql SDBC Driver. no work on the project since 2010; last version was a beta. http://www.openoffice.org/dba/drivers/postgresql/index.html
* RedHat: hasn't been refreshed since Pg 8.4. http://sources.redhat.com/rhdb

List of drivers

2019-04-16T02:57:58Z

Dfetter: /* Drivers */

= Drivers =

The list below are PostgreSQL drivers (also referred to as "client libraries") that developers can use to [https://www.postgresql.org/docs/current/protocol.html interface with PostgreSQL] from various programming languages. The list is alphabetized by programming language, and also indicates if the driver is based on [https://www.postgresql.org/docs/current/libpq.html libpq] and whether or not it supports the [https://www.postgresql.org/docs/current/sasl-authentication.html#SASL-SCRAM-SHA-256 SCRAM-SHA-256] authentication protocol that was added in [https://www.postgresql.org/docs/release/10.0/ PostgreSQL 10].

'''NOTE''': The drivers listed below are in various states of development. Some of them have been stable for many years and have been proven in various environments, whereas others are in early development. This listed is strictly informational: it is up to you to select the driver that is best for your environment.

If you would like to add additional drivers to the list, please add them in alphabetical order based on the programming language for the driver.

{| border="1"
!Driver
!Language
!uses libpq?
!Supports SCRAM?
|-
|[http://www.postgresql.org/docs/current/static/libpq.html libpq]
|C
|Yes
|Yes
|-
|[http://odbc.postgresql.org ODBC]
|C
|Yes
|Yes
|-
|[http://pqxx.org/development/libpqxx/ libpqxx]
|C++
|Yes
|Yes
|-
|[https://doc.qt.io/qt-5/sql-driver.html#qpsql QPSQL]
|C++ (Qt)
|Yes
|Yes
|-
|[https://github.com/dmitigr/pgfe pgfe]
|C++
|Yes
|Yes
|-
|[https://github.com/yandex/ozo OZO]
|C++
|Yes
|Yes
|-
|[http://www.npgsql.org npgsql]
|C#
|No
|Yes, as of 3.2.7
|-
|[https://github.com/will/crystal-pg crystal-pg]
|Crystal
|No
|No
|-
|[https://github.com/elixir-ecto/postgrex Postgrex]
|Elixir
|No
|Yes, as of 0.14.0
|-
|[https://github.com/anse1/emacs-libpq emacs-libpq]
|Emacs Lisp
|Yes
|Yes
|-
|[https://github.com/epgsql/epgsql epgsql]
|Erlang
|No
|Yes [https://github.com/epgsql/epgsql/issues/142]
|-
|[https://github.com/lib/pq github.com/lib/pq]
|Go
|No
|Yes, since 1.1.0
|-
|[https://github.com/jackc/pgx pgx]
|Go
|No
|No
|-
|[https://github.com/go-pg/pg go-pg]
|Go
|No
|Yes, since 6.15
|-
|[https://github.com/hdbc/hdbc-postgresql/wiki HDBC]
|Haskell
|Yes
|Yes
|-
|[https://hackage.haskell.org/package/postgresql-simple postgresql-simple]
|Haskell
|Yes
|Yes
|-
|[https://jdbc.postgresql.org/ JDBC]
|Java
|No
|Yes, as of 42.2.0.
|-
|[https://github.com/brianc/node-postgres node-postgres]
|JavaScript
|Optional
| Yes [https://github.com/brianc/node-postgres/pull/1835], from 7.9.0
|-
|[https://metacpan.org/release/DBD-Pg DBD::Pg]
|Perl
|Yes
|Yes
|-
|[https://www.php.net/manual/en/book.pgsql.php php-pgsql]
|PHP
|Yes
|Yes
|-
|[https://www.php.net/manual/en/ref.pdo-pgsql.php PDO_PGSQL]
|PHP
|Yes
|Yes
|-
|[https://github.com/m6w6/ext-pq ext-pq]
|PHP
|Yes
|Yes
|-
|[http://www.pomm-project.org/ Pomm]
|PHP
|Yes
|Yes
|-
|[http://initd.org/psycopg/ psycopg2]
|Python (CPython only)
|Yes
|Yes
|-
|[https://github.com/MagicStack/asyncpg asyncpg]
|Python
|No
|No [https://github.com/MagicStack/asyncpg/issues/314]
|-
|[https://github.com/chtd/psycopg2cffi psycopg2cffi]
|Python, PyPi
|Yes
|Yes
|-
|[https://cran.r-project.org/package=RPostgreSQL RPostgreSQL]
|R
|Yes
|Yes
|-
|[https://rubyforge.org/projects/ruby-pg ruby-pg]
|Ruby
|Yes
|Yes
|-
|[https://github.com/sfackler/rust-postgres rust-postgres]
|Rust
|No
|Yes [https://github.com/sfackler/rust-postgres/commit/11ffcac087fef8907dd5cdfc3c082ff13f76557b]
|-
|[https://flightaware.github.io/Pgtcl/ Pgtcl]
|Tcl
|Yes
|Yes
|-
|[http://sourceforge.net/projects/pgtclng/ pgtclng]
|Tcl
|Yes
|Yes
|}

== Unsupported Drivers ==

Below is a list of drivers that are no longer maintained.

{| border="1"
!Driver
!Language
|-
|[https://github.com/sshirokov/CLSQL CLSQL]
|Common Lisp
|-
|[http://marijnhaverbeke.nl/postmodern/ Postmodern]
|Common Lisp
|-
|[http://frihjul.net/pgsql pgsql]
|Erlang
|-
|[http://code.google.com/p/erlang-psql-driver/ erlang-psql-driver]
|Erlang
|-
|[https://metacpan.org/pod/release/ARC/DBD-PgPP-0.08/lib/DBD/PgPP.pm PgPP]
|Perl
|}

= See Also =

* [http://www.postgresql.org/download/products/2 Software catalog list]

[[Category: Language interface|!]]

List of drivers

2019-04-15T18:09:30Z

Dfetter:

= Drivers =

The list below are PostgreSQL drivers (also referred to as "client libraries") that developers can use to [https://www.postgresql.org/docs/current/protocol.html interface with PostgreSQL] from various programming languages. The list is alphabetized by programming language, and also indicates if the driver is based on [https://www.postgresql.org/docs/current/libpq.html libpq] and whether or not it supports the [https://www.postgresql.org/docs/current/sasl-authentication.html#SASL-SCRAM-SHA-256 SCRAM-SHA-256] authentication protocol that was added in [https://www.postgresql.org/docs/release/10.0/ PostgreSQL 10].

'''NOTE''': The drivers listed below are in various states of development. Some of them have been stable for many years and have been proven in various environments, whereas others are in early development. This listed is strictly informational: it is up to you to select the driver that is best for your environment.

If you would like to add additional drivers to the list, please add them in alphabetical order based on the programming language for the driver.

{| border="1"
!Driver
!Language
!uses libpq?
!Supports SCRAM?
|-
|[http://www.postgresql.org/docs/current/static/libpq.html libpq]
|C
|Yes
|Yes
|-
|[http://odbc.postgresql.org ODBC]
|C
|Yes
|Yes
|-
|[http://pqxx.org/development/libpqxx/ libpqxx]
|C++
|Yes
|Yes
|-
|[https://doc.qt.io/qt-5/sql-driver.html#qpsql QPSQL]
|C++ (Qt)
|Yes
|Yes
|-
|[https://github.com/dmitigr/pgfe pgfe]
|C++
|Yes
|Yes
|-
|[https://github.com/yandex/ozo OZO]
|C++
|Yes
|Yes
|-
|[http://www.npgsql.org npgsql]
|C#
|No
|Yes from version 3.2.7
|-
|[https://github.com/will/crystal-pg crystal-pg]
|Crystal
|No
|No
|-
|[https://github.com/elixir-ecto/postgrex Postgrex]
|Elixir
|No
|Yes, from version 0.14.0
|-
|[https://github.com/anse1/emacs-libpq emacs-libpq]
|Emacs Lisp
|Yes
|Yes
|-
|[https://github.com/epgsql/epgsql epgsql]
|Erlang
|No
|Yes [https://github.com/epgsql/epgsql/issues/142]
|-
|[https://github.com/lib/pq github.com/lib/pq]
|Go
|No
|Yes
|-
|[https://github.com/jackc/pgx pgx]
|Go
|No
|No
|-
|[https://github.com/go-pg/pg go-pg]
|Go
|No
|Yes, since 6.15
|-
|[https://github.com/hdbc/hdbc-postgresql/wiki HDBC]
|Haskell
|Yes
|Yes
|-
|[https://hackage.haskell.org/package/postgresql-simple postgresql-simple]
|Haskell
|Yes
|Yes
|-
|[https://jdbc.postgresql.org/ JDBC]
|Java
|No
|Yes, from version 42.2.0.
|-
|[https://github.com/brianc/node-postgres node-postgres]
|JavaScript
|Optional
| Yes [https://github.com/brianc/node-postgres/pull/1835], from 7.9.0
|-
|[https://metacpan.org/release/DBD-Pg DBD::Pg]
|Perl
|Yes
|Yes
|-
|[https://www.php.net/manual/en/book.pgsql.php php-pgsql]
|PHP
|Yes
|Yes
|-
|[https://www.php.net/manual/en/ref.pdo-pgsql.php PDO_PGSQL]
|PHP
|Yes
|Yes
|-
|[https://github.com/m6w6/ext-pq ext-pq]
|PHP
|Yes
|Yes
|-
|[http://www.pomm-project.org/ Pomm]
|PHP
|Yes
|Yes
|-
|[http://initd.org/psycopg/ psycopg2]
|Python (CPython only)
|Yes
|Yes
|-
|[https://github.com/MagicStack/asyncpg asyncpg]
|Python
|No
|No [https://github.com/MagicStack/asyncpg/issues/314]
|-
|[https://github.com/chtd/psycopg2cffi psycopg2cffi]
|Python, PyPi
|Yes
|Yes
|-
|[https://cran.r-project.org/package=RPostgreSQL RPostgreSQL]
|R
|Yes
|Yes
|-
|[https://rubyforge.org/projects/ruby-pg ruby-pg]
|Ruby
|Yes
|Yes
|-
|[https://github.com/sfackler/rust-postgres rust-postgres]
|Rust
|No
|Yes [https://github.com/sfackler/rust-postgres/commit/11ffcac087fef8907dd5cdfc3c082ff13f76557b]
|-
|[https://flightaware.github.io/Pgtcl/ Pgtcl]
|Tcl
|Yes
|Yes
|-
|[http://sourceforge.net/projects/pgtclng/ pgtclng]
|Tcl
|Yes
|Yes
|}

== Unsupported Drivers ==

Below is a list of drivers that are no longer maintained.

{| border="1"
!Driver
!Language
|-
|[https://github.com/sshirokov/CLSQL CLSQL]
|Common Lisp
|-
|[http://marijnhaverbeke.nl/postmodern/ Postmodern]
|Common Lisp
|-
|[http://frihjul.net/pgsql pgsql]
|Erlang
|-
|[http://code.google.com/p/erlang-psql-driver/ erlang-psql-driver]
|Erlang
|-
|[https://metacpan.org/pod/release/ARC/DBD-PgPP-0.08/lib/DBD/PgPP.pm PgPP]
|Perl
|}

= See Also =

* [http://www.postgresql.org/download/products/2 Software catalog list]

[[Category: Language interface|!]]

GSoC 2019

2019-04-13T16:54:09Z

Dfetter: /* References */

This page is for collecting ideas for future Summer of Code projects.

== Regarding Project Ideas ==

Project ideas are to be added here by community members.

'''NOTE:''' Google wants each idea to be supported by a few sentences and then a list of skills/reqs, difficulty level, potential mentors, expected outcomes, etc. Please add sections in this format.

== Mentors (2019) ==

The following individuals have been listed as possible mentors on the below projects, and/or offered to be mentors for student-proposed projects:

* Stephen Frost
* David Steele
* Andrey Borodin
* Vladimir Leskov
* Dave Page
* Andreas Scherbaum
* Mark Wong

== WAL-G safety features (2019) ==

===== Project Description =====
WAL-G is the simple backup tool for PostgreSQL. Essentially, it supports backup and WAL archiving to cloud storages. WAL-G repository. Currently, we want to improve backup storing. To be more precise, we would like to see implemented following features:
* Retention policy improvement -- currently, we can only delete everything before specified backup or retain fix number of backups. We want to improve backup management, E.g. give user ability to mark important backup permanent to avoid its deletion.
* WAL's history consistency check -- we want to ensure, that we can provide PITR (point in time recovery) for the user.
* Page checksum verification -- it's one of the key features needed for backup verification.

===== Skills needed =====
* Go language
* Ability to read technical papers and documentation to understand PostgreSQL inner structure.
===== Difficulty level =====
Moderate

===== Potential Mentors =====
* Andrey Borodin can mentor. Andrey is WAL-G developer and PostgreSQL contributor.
* Vladimir Leskov can mentor. Vladimir is WAL-G developer.

===== Expected Outcomes =====
All before mentioned features properly implemented, covered with tests and Pull-Requested to WAL-G.

== GiST API advancement (2019) ==

=====Project Description=====
GiST API was designed at the beginning of 90th to reduce boilerplate code around data access methods over a balanced tree. Now, after 30 years, there are some ideas on improving this API.

Opclass developer must specify 4 core operations to make a type GiST-indexable:

1. Split: a function to split set of datatype instances into two parts.

2. Penalty calculation: a function to measure penalty for unification of two keys.

3. Collision check: a function which determines whether two keys may have overlap or are not intersecting.

4. Unification: a function to combine two keys into one so that combined key collides with both input keys.

Functions 2 and 3 can be improved.

For example, Revised R*-tree[1] algorithm of insertion cannot be expressed in terms of penalty-based algorithms. There were some attempts to bring parts of RR*-tree insertion, but they come down to ugly hacks [2]. Current GiST API, due to penalty-based insertion algorithm, does not allow to implement an important feature of RR*-tree: overlap optimization. As Norbert Beckman, author of RR*-tree, put it in the discussion: “Overlap optimization is one of the main elements, if not the main query performance tuning element of the RR*-tree. You would fall back to old R-Tree times if that would be left off.”

Collision check currently returns a binary result:

1. Query may be collides with subtree MBR

2. Query do not collides with subtree

This result may be augmented with a third state: subtree is totally within the query. In this case, GiST scan can scan down subtree without key checks.

The potential effect of these improvements must be benchmarked. Probably, implementation of these two will spawn more ideas on GiST performance improvements.

Another feature of RR*-tree is storing in the page additional MBR. Such additional MBR covers all the entries MBRs just after page creation but don't updated afterwards. Then, when this page is being split, such additional MBR could be used to select better split ration, and in turn in order to have better space utilization. Currently GiST doesn't allow to store some additional datum per page, but it would be nice to have.

Finally, GiST do not provide API for bulk loading. Alexander Korotkov during GSoC 2011 implemented buffered GiST build. This index construction is faster, but yields the index tree with virtually same querying performance. There are different algorithms aiming to provide better indexing tree due to some knowledge of data, e.g. [3]

=====Skills needed=====
*ability to understand searches within GiST
*ability to describe and set up datasets for performance features demostration
*ability to produce committable patch

=====Difficulty Level=====

Easy

=====Potential Mentors=====

* Andrey Borodin can mentor.
* Alexander Korotkov can mentor. Alexander is major contributor and committer.

=====Expected Outcomes=====
Expected outcomes are the benchmark for API features and committable patch implementing them.

=====References=====
[1] Beckmann, Norbert, and Bernhard Seeger. "A revised r*-tree in comparison with related index structures." Proceedings of the 2009 ACM SIGMOD International Conference on Management of data. ACM, 2009.

[2] https://www.postgresql.org/message-id/flat/CAJEAwVFMo-FXaJ6Lkj8Wtb1br0MtBY48EGMVEJBOodROEGykKg%40mail.gmail.com#CAJEAwVFMo-FXaJ6Lkj8Wtb1br0MtBY48EGMVEJBOodROEGykKg@mail.gmail.com

[3] Achakeev, Daniar, Bernhard Seeger, and Peter Widmayer. https://www.mathematik.uni-marburg.de/~achakeye/publications/sortBasedLoading.pdf Proceedings of the 21st ACM international conference on Information and knowledge management. ACM, 2012.

== TOAST'ing in slices (2019) ==

=====Project Description=====
Currently, an entire individual value is compressed all together and then stored in data chunks in the TOAST table without an indication of which piece of the original data made it into what chunk of the TOAST table. What this ends up meaning is that to get a subset of the TOAST'd value, all of the chunks (or at least all of them up to the point which is being searched for, if that is known) have to be re-formed and the entire value de-compressed.

=====Project details=====
The best approach to slicing a given value will likely depend on the data type. A text field, for example, would most likely be naturally split upon character (not byte) boundaries, while an array data type would likely be split upon its element boundary. A JSON document might be split in another way (presumably based on how a JSONB is structured). A possible additional task would be to consider if it's possible to include in an index the information about which keys or values exist in a given TOAST chunk. For the JSONB case, in particular, one can imagine that it would eventually be possible to extract out just the JSON chunks which have the key or value being searched for.

=====Skills needed=====
* C skills
* Ability to understand complex on-disk data structures
* Ability to understand inverted indexing
* Ability to understand how traditional compression and block-based compression algorithms function

=====Difficulty Level=====
* Moderate-level

=====Potential Mentors=====

* Stephen Frost can mentor. Stephen is a major contributor and committer.

=====Expected Outcomes=====
Expected outcomes are a patch which implements the ability to split up a single value into known-sized pre-compressed chunks which are then stored in TOAST, and functions able to be optimized based on that knowledge.

----

== de-TOAST'ing using an iterator (2019) ==

=====Project Description=====
Currently, an entire individual value is compressed all together and then stored in data chunks in the TOAST table without an indication of which piece of the original data made it into what chunk of the TOAST table. What this ends up meaning is that to get a subset of the TOAST'd value, all of the chunks (or at least all of them up to the point which is being searched for, if that is known) have to be re-formed and the entire value de-compressed.

=====Project details=====
This project would aim to provide the ability to de-TOAST a fully TOAST'd and compressed field using an iterator, and then update the appropriate parts of the code to use the iterator where possible instead of de-TOAST'ing and de-compressing the entire value. Examples where this can be helpful include using substring() from the beginning of the value, or doing a pattern or substring match. This is distinct and simpler than the above project which envisions a larger change to the TOAST system.

=====Skills needed=====
* C skills
* Ability to understand how traditional compression and block-based compression algorithms function

=====Difficulty Level=====
* Easy-level

=====Potential Mentors=====

* Stephen Frost can mentor. Stephen is a major contributor and committer.

=====Expected Outcomes=====
Expected outcomes are a patch which implements de-TOAST'ing a value using an iterator and then updates to the other parts of the code to use that iterator, resulting in a significant performance improvements for certain queries.

----

==Improve PostgreSQL Regression Test Coverage (2019)==

=====Project Description=====

The current regression test coverage for PostgreSQL isn't great, to the point where some areas of the code are covered only at single-digit-percent levels.

Having good regression tests for such an important project as PostgreSQL is really key to minimizing the chance that any regressions are introduced. While this might seem like a small project, it isn't, particularly when it comes to PostgreSQL. PostgreSQL is over 1.3M lines of code and some of the code paths can be tricky to reach.

The current regression test coverage can be see here: https://coverage.postgresql.org

PostgreSQL's build system includes a "make coverage-html" to generate the report.

Please note that this project involves writing SQL code and Perl code, at a minimum, to implement the tests necessary to increase the code coverage of the PostgreSQL regression tests. This is not a small task as PostgreSQL is currently at only about 73% LOC coverage.

=====Skills needed=====
* Perl, as many PostgreSQL regression tests are written using the Perl TAP system and new ones will likely need to be.
* SQL, to craft tests that hit certain code paths
* Ability to read C code enough to work through a way to get a particular line or lines of code tested.

=====Difficulty Level=====

For someone with the skills listed, even at a relatively beginner level, should make this a very straight-forward if tedious project.

=====Potential Mentors=====

* Stephen Frost can mentor. Stephen is a major contributor and committer and has been working on improving regression tests in PG for quite a while.
* Andreas Scherbaum can mentor. Andreas mentored GSoC and Code-In in the past, and in general helps boosting PostgreSQL in Europe.

=====Expected Outcomes=====

* Significantly improved code coverage for the PostgreSQL regression test suite, ie: 73% -> 80%.

==Enhancing amcheck for all AMs (2019)==

=====Project Description=====

Amcheck is a PostgreSQL extension to verify the integrity of index against invariants that should always hold in the valid index. This tool is designed to diagnose corruption and help developers during the implementation of new features in access methods. Currently, amcheck supports only B-tree. Also, work on GiST is in progress https://github.com/petergeoghegan/amcheck/pull/11
But amcheck could be used for many other indexes: GIN, SP-GiST, BRIN, RUM.
For each AM it is necessary to deduce invariants to check, implement this checks and test against various index states.
Also, it would be useful to unite all AM check methods in a single entry point for checking index.
The interface of check functions can also be enhanced in favor of more detailed corruption information. It would be useful to model various corruptions, including both those which can be found by data_checksums and those which cannot.

=====Skills needed=====
* Good C code skills
* Understanging of access methods ideas and details

=====Difficulty Level=====

The project requires to grasp algorithms behind very sophisticated data structures, along with concurrency and recovery over them.

=====Potential Mentors=====

* Andrey Borodin can mentor. Peter Geoghegan can consult team on controversial cases. Peter Geoghegan is the original author of amcheck.

=====Expected Outcomes=====

* Support for all major PostgreSQL AMs in amcheck.

==Develop Performance Farm Database and Website (2019)==

=====Project Description=====

The PostgreSQL Performance Farm project is a community project to collect performance data from tests as code changes are made to PostgreSQL. To support this effort, a database needs to be created for storing results, and a Web site developed to review results. This project will focus on developing the Web site on top of the database.

The database will be using PostgreSQL in the back-end. Test results will come in the form of JSON and flat files. The Web application will be developed using the Django Web framework.

For reference, the code that will be supplying test results is https://git.postgresql.org/gitweb/?p=pgperffarm.git;a=summary.

As an example, the PostgreSQL Build Farm site [1] is a central repository for the results of testing source code changes for PostgreSQL as they occur, on a wide variety of platforms.

=====Skills needed=====

* Python programming
* SQL programming

=====Difficulty Level=====

This project requires familiarity with Python programming and basic database experience.

=====Potential Mentors=====

* Mark Wong can mentor.
* Andreas Scherbaum can mentor.
* Pavan Agrawal can mentor.

=====Expected Outcomes=====

* A functional Web site where clients can upload test results, and users can search and review uploaded results.

=====References=====

[1] https://buildfarm.postgresql.org/

==Read/write transaction-level routing in Odyssey (2019)==

=====Project Description=====

Odyssey is an advanced multi-threaded PostgreSQL connection pooler and request router.
Odyssey allows defining client routing rules by specifying client database, client user name and storage connection. In some HA scenarios, it is necessary to define different routing for read-only and read-write transactions.
Odyssey can parse transaction opening statements and assign different routes depending on transaction types.

It would be cool to support many consistency models for reads on standby:
1. Redirecting read query on standby only if standby is lagging no more than X seconds
2. Redirecting read query on standby unless there was recent write (writer should see his writes)
3. Redirecting some read queries on syn or async standby

=====Skills needed=====

* C programming

=====Difficulty Level=====

Moderate.

=====Potential Mentors=====

* Andrey Borodin can mentor.

=====Expected Outcomes=====

* Pull request to Odyssey with described feature

=====References=====

[1] https://github.com/yandex/odyssey

==pgAdmin 4 Query Tool Graphing (2019)==

=====Project Description=====

pgAdmin has a GIS Viewer built into it's Query Tool as the result of a 2018 GSoC Project, that allows the user to render PostGIS shapes and points etc. and view them on a plain canvas or over one of a number of map sources.

This project would be to add a similar capability to allow the user to plot query results in graph formats, for example, selecting column(s) to view on the X/Y axis and then rendering the output as a line chart, bar chart, or even a pie chart.

=====Skills needed=====

* Python
* Javascript/JQuery
* HTML/CSS

=====Difficulty Level=====

Moderate.

=====Potential Mentors=====

* Dave Page

=====Expected Outcomes=====

* Feature committed to the pgAdmin tree for the next release, with documentation and test cases.

=====References=====

[1] https://www.pgadmin.org/

[2] https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=summary

==pgAdmin 4 Query Tool bytea support (2019)==

=====Project Description=====

pgAdmin's Query Tool currently doesn't render bytea data in its Query Tool, or allow options to update such columns. This project would have 2 core aims:

* Update the Query Tool to enable bytea data to be uploaded when editing a row.
* Add viewers to the Query Tool output grid such that when it can be detected that the data in a field is of a known type (image, sound or video file), a button can be displayed in the grid that when clicked will display or play the media.

=====Skills needed=====

* Python
* Javascript/JQuery
* HTML/CSS

=====Difficulty Level=====

Moderate.

=====Potential Mentors=====

* Dave Page

=====Expected Outcomes=====

* Feature committed to the pgAdmin tree for the next release, with documentation and test cases.

=====References=====

[1] https://www.pgadmin.org/

[2] https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=summary

==pgAdmin 4 Query Tool automatic mode detection (2019)==

=====Project Description=====

pgAdmin's Query Tool currently works in 2 different modes:

* View Data mode allows modifications to the SQL Query only through the UI, but allows editing of data when used with a table with an appropriate primary key.
* Query mode allows arbitrary queries to be written and executed, but the user cannot edit the results.

The aim of this project is to automatically detect if the query entered will produce in an updatable resultset and enable/disable editing of the results and other parts of the UI as appropriate (for example, disabling the sort/filter UI options if the query string is not one that can be programmatically changed).

=====Skills needed=====

* Python
* Javascript/JQuery
* HTML/CSS

=====Difficulty Level=====

High.

=====Potential Mentors=====

* Dave Page

=====Expected Outcomes=====

* Feature committed to the pgAdmin tree for the next release, with documentation and test cases.

=====References=====

[1] https://www.pgadmin.org/

[2] https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=summary

==pgBackRest port to Windows (2019)==

=====Project Description=====

pgBackRest is being reimplemented into C currently and it is well on its way. There is already enough of the code in C that it's time to start working on porting pgBackRest to Windows. This project would aim to have all of the C code ported to Windows, which would also include some changes in how pgBackRest operates. The necessary changes for running pgBackRest on Windows have been contemplated during the architecture and design of pgBackRest and therefore should be reasonably straight-forward to implement.

=====Skills needed=====

* C
* Working in a Windows development environment

=====Difficulty Level=====

Medium.

=====Potential Mentors=====

* Stephen Frost
* David Steele

=====Expected Outcomes=====

* pgBackRest able to be built and run on Windows.

=====References=====

[1] https://www.pgbackrest.org/

[2] https://github.com/pgbackrest

==Extract scanning strategy to the separate entity from GiST/GIN/SP-GiST opclasses (2019)==

=====Project Description=====

PostgreSQL offers great indexing extensibility. It supports index access methods which are templates for particular kinds of indexes. Opclasses specify application of access method to particular data type. There could be multiple opclasses for same access method and data type with different capabilities. Moreover, since PostgreSQL 9.6+ index access methods could be user-defined themselves.

However, there are still shortcomings in this extendability system. Opclass specifies particular kind of index and its scanning strategies. One problem is that scanning strategies of opclass can't be extended. For instance, extension could add more spatial operators to built-in GiST opclasses for geometrical datatypes; or fuzzy string matching operators to build-in SP-GiST opclass for text (radix tree). In order to overcome such shortcoming we need to make a scanning strategy a separate entity. Such entity should contain search/order by operators itself as well as corresponding supporting functions such as:

* consistent, distance for GiST,
* inner_consistent and leaf_consistent for SP-GiST,
* extractQuery, consistent, triConsistent and comparePartial for GIN.

=====Skills needed=====

* The ability to read technical papers and documentation to understand index access methods extendability
** http://minds.wisconsin.edu/bitstream/handle/1793/59976/TR1274.pdf
** http://zeus.sai.msu.ru/~megera/postgres/gist/papers/csd-97-950.pdf
** https://www.postgresql.org/docs/current/static/gist.html
** https://www.postgresql.org/docs/current/static/spgist.html
** https://www.postgresql.org/docs/current/static/gin.html
* Ability to refactor system catalog, to find the appropriate places in each of the index AMs to use new entities. Therefore, the ability to navigate over functionality scattered among large and complex project.

=====Difficulty Level=====

The project is difficult from the implementation side, because it requires consistent modification of many places in the source code. Design question doesn't seem to be hard tough.

=====Potential Mentors=====

* Alexander Korotkov can mentor. Alexander is a major contributor and committer.
* Oleg Bartunov can mentor. Oleg is a major contributor.
* Teodor Sigaev can mentor. Teodor is a major contributor and committer.

=====Expected Outcomes=====

The expected outcome is ability of extensions to add new extensions to existing opclasses.

[[Category:Google Summer of Code]]

GSoC 2019

2019-04-13T16:52:19Z

Dfetter: /* Project Description */

This page is for collecting ideas for future Summer of Code projects.

== Regarding Project Ideas ==

Project ideas are to be added here by community members.

'''NOTE:''' Google wants each idea to be supported by a few sentences and then a list of skills/reqs, difficulty level, potential mentors, expected outcomes, etc. Please add sections in this format.

== Mentors (2019) ==

The following individuals have been listed as possible mentors on the below projects, and/or offered to be mentors for student-proposed projects:

* Stephen Frost
* David Steele
* Andrey Borodin
* Vladimir Leskov
* Dave Page
* Andreas Scherbaum
* Mark Wong

== WAL-G safety features (2019) ==

===== Project Description =====
WAL-G is the simple backup tool for PostgreSQL. Essentially, it supports backup and WAL archiving to cloud storages. WAL-G repository. Currently, we want to improve backup storing. To be more precise, we would like to see implemented following features:
* Retention policy improvement -- currently, we can only delete everything before specified backup or retain fix number of backups. We want to improve backup management, E.g. give user ability to mark important backup permanent to avoid its deletion.
* WAL's history consistency check -- we want to ensure, that we can provide PITR (point in time recovery) for the user.
* Page checksum verification -- it's one of the key features needed for backup verification.

===== Skills needed =====
* Go language
* Ability to read technical papers and documentation to understand PostgreSQL inner structure.
===== Difficulty level =====
Moderate

===== Potential Mentors =====
* Andrey Borodin can mentor. Andrey is WAL-G developer and PostgreSQL contributor.
* Vladimir Leskov can mentor. Vladimir is WAL-G developer.

===== Expected Outcomes =====
All before mentioned features properly implemented, covered with tests and Pull-Requested to WAL-G.

== GiST API advancement (2019) ==

=====Project Description=====
GiST API was designed at the beginning of 90th to reduce boilerplate code around data access methods over a balanced tree. Now, after 30 years, there are some ideas on improving this API.

Opclass developer must specify 4 core operations to make a type GiST-indexable:

1. Split: a function to split set of datatype instances into two parts.

2. Penalty calculation: a function to measure penalty for unification of two keys.

3. Collision check: a function which determines whether two keys may have overlap or are not intersecting.

4. Unification: a function to combine two keys into one so that combined key collides with both input keys.

Functions 2 and 3 can be improved.

For example, Revised R*-tree[1] algorithm of insertion cannot be expressed in terms of penalty-based algorithms. There were some attempts to bring parts of RR*-tree insertion, but they come down to ugly hacks [2]. Current GiST API, due to penalty-based insertion algorithm, does not allow to implement an important feature of RR*-tree: overlap optimization. As Norbert Beckman, author of RR*-tree, put it in the discussion: “Overlap optimization is one of the main elements, if not the main query performance tuning element of the RR*-tree. You would fall back to old R-Tree times if that would be left off.”

Collision check currently returns a binary result:

1. Query may be collides with subtree MBR

2. Query do not collides with subtree

This result may be augmented with a third state: subtree is totally within the query. In this case, GiST scan can scan down subtree without key checks.

The potential effect of these improvements must be benchmarked. Probably, implementation of these two will spawn more ideas on GiST performance improvements.

Another feature of RR*-tree is storing in the page additional MBR. Such additional MBR covers all the entries MBRs just after page creation but don't updated afterwards. Then, when this page is being split, such additional MBR could be used to select better split ration, and in turn in order to have better space utilization. Currently GiST doesn't allow to store some additional datum per page, but it would be nice to have.

Finally, GiST do not provide API for bulk loading. Alexander Korotkov during GSoC 2011 implemented buffered GiST build. This index construction is faster, but yields the index tree with virtually same querying performance. There are different algorithms aiming to provide better indexing tree due to some knowledge of data, e.g. [3]

=====Skills needed=====
*ability to understand searches within GiST
*ability to describe and set up datasets for performance features demostration
*ability to produce committable patch

=====Difficulty Level=====

Easy

=====Potential Mentors=====

* Andrey Borodin can mentor.
* Alexander Korotkov can mentor. Alexander is major contributor and committer.

=====Expected Outcomes=====
Expected outcomes are the benchmark for API features and committable patch implementing them.

=====References=====
[1] Beckmann, Norbert, and Bernhard Seeger. "A revised r*-tree in comparison with related index structures." Proceedings of the 2009 ACM SIGMOD International Conference on Management of data. ACM, 2009.

[2] https://www.postgresql.org/message-id/flat/CAJEAwVFMo-FXaJ6Lkj8Wtb1br0MtBY48EGMVEJBOodROEGykKg%40mail.gmail.com#CAJEAwVFMo-FXaJ6Lkj8Wtb1br0MtBY48EGMVEJBOodROEGykKg@mail.gmail.com

[3] Achakeev, Daniar, Bernhard Seeger, and Peter Widmayer. "Sort-based query-adaptive loading of r-trees." Proceedings of the 21st ACM international conference on Information and knowledge management. ACM, 2012.

== TOAST'ing in slices (2019) ==

=====Project Description=====
Currently, an entire individual value is compressed all together and then stored in data chunks in the TOAST table without an indication of which piece of the original data made it into what chunk of the TOAST table. What this ends up meaning is that to get a subset of the TOAST'd value, all of the chunks (or at least all of them up to the point which is being searched for, if that is known) have to be re-formed and the entire value de-compressed.

=====Project details=====
The best approach to slicing a given value will likely depend on the data type. A text field, for example, would most likely be naturally split upon character (not byte) boundaries, while an array data type would likely be split upon its element boundary. A JSON document might be split in another way (presumably based on how a JSONB is structured). A possible additional task would be to consider if it's possible to include in an index the information about which keys or values exist in a given TOAST chunk. For the JSONB case, in particular, one can imagine that it would eventually be possible to extract out just the JSON chunks which have the key or value being searched for.

=====Skills needed=====
* C skills
* Ability to understand complex on-disk data structures
* Ability to understand inverted indexing
* Ability to understand how traditional compression and block-based compression algorithms function

=====Difficulty Level=====
* Moderate-level

=====Potential Mentors=====

* Stephen Frost can mentor. Stephen is a major contributor and committer.

=====Expected Outcomes=====
Expected outcomes are a patch which implements the ability to split up a single value into known-sized pre-compressed chunks which are then stored in TOAST, and functions able to be optimized based on that knowledge.

----

== de-TOAST'ing using an iterator (2019) ==

=====Project Description=====
Currently, an entire individual value is compressed all together and then stored in data chunks in the TOAST table without an indication of which piece of the original data made it into what chunk of the TOAST table. What this ends up meaning is that to get a subset of the TOAST'd value, all of the chunks (or at least all of them up to the point which is being searched for, if that is known) have to be re-formed and the entire value de-compressed.

=====Project details=====
This project would aim to provide the ability to de-TOAST a fully TOAST'd and compressed field using an iterator, and then update the appropriate parts of the code to use the iterator where possible instead of de-TOAST'ing and de-compressing the entire value. Examples where this can be helpful include using substring() from the beginning of the value, or doing a pattern or substring match. This is distinct and simpler than the above project which envisions a larger change to the TOAST system.

=====Skills needed=====
* C skills
* Ability to understand how traditional compression and block-based compression algorithms function

=====Difficulty Level=====
* Easy-level

=====Potential Mentors=====

* Stephen Frost can mentor. Stephen is a major contributor and committer.

=====Expected Outcomes=====
Expected outcomes are a patch which implements de-TOAST'ing a value using an iterator and then updates to the other parts of the code to use that iterator, resulting in a significant performance improvements for certain queries.

----

==Improve PostgreSQL Regression Test Coverage (2019)==

=====Project Description=====

The current regression test coverage for PostgreSQL isn't great, to the point where some areas of the code are covered only at single-digit-percent levels.

Having good regression tests for such an important project as PostgreSQL is really key to minimizing the chance that any regressions are introduced. While this might seem like a small project, it isn't, particularly when it comes to PostgreSQL. PostgreSQL is over 1.3M lines of code and some of the code paths can be tricky to reach.

The current regression test coverage can be see here: https://coverage.postgresql.org

PostgreSQL's build system includes a "make coverage-html" to generate the report.

Please note that this project involves writing SQL code and Perl code, at a minimum, to implement the tests necessary to increase the code coverage of the PostgreSQL regression tests. This is not a small task as PostgreSQL is currently at only about 73% LOC coverage.

=====Skills needed=====
* Perl, as many PostgreSQL regression tests are written using the Perl TAP system and new ones will likely need to be.
* SQL, to craft tests that hit certain code paths
* Ability to read C code enough to work through a way to get a particular line or lines of code tested.

=====Difficulty Level=====

For someone with the skills listed, even at a relatively beginner level, should make this a very straight-forward if tedious project.

=====Potential Mentors=====

* Stephen Frost can mentor. Stephen is a major contributor and committer and has been working on improving regression tests in PG for quite a while.
* Andreas Scherbaum can mentor. Andreas mentored GSoC and Code-In in the past, and in general helps boosting PostgreSQL in Europe.

=====Expected Outcomes=====

* Significantly improved code coverage for the PostgreSQL regression test suite, ie: 73% -> 80%.

==Enhancing amcheck for all AMs (2019)==

=====Project Description=====

Amcheck is a PostgreSQL extension to verify the integrity of index against invariants that should always hold in the valid index. This tool is designed to diagnose corruption and help developers during the implementation of new features in access methods. Currently, amcheck supports only B-tree. Also, work on GiST is in progress https://github.com/petergeoghegan/amcheck/pull/11
But amcheck could be used for many other indexes: GIN, SP-GiST, BRIN, RUM.
For each AM it is necessary to deduce invariants to check, implement this checks and test against various index states.
Also, it would be useful to unite all AM check methods in a single entry point for checking index.
The interface of check functions can also be enhanced in favor of more detailed corruption information. It would be useful to model various corruptions, including both those which can be found by data_checksums and those which cannot.

=====Skills needed=====
* Good C code skills
* Understanging of access methods ideas and details

=====Difficulty Level=====

The project requires to grasp algorithms behind very sophisticated data structures, along with concurrency and recovery over them.

=====Potential Mentors=====

* Andrey Borodin can mentor. Peter Geoghegan can consult team on controversial cases. Peter Geoghegan is the original author of amcheck.

=====Expected Outcomes=====

* Support for all major PostgreSQL AMs in amcheck.

==Develop Performance Farm Database and Website (2019)==

=====Project Description=====

The PostgreSQL Performance Farm project is a community project to collect performance data from tests as code changes are made to PostgreSQL. To support this effort, a database needs to be created for storing results, and a Web site developed to review results. This project will focus on developing the Web site on top of the database.

The database will be using PostgreSQL in the back-end. Test results will come in the form of JSON and flat files. The Web application will be developed using the Django Web framework.

For reference, the code that will be supplying test results is https://git.postgresql.org/gitweb/?p=pgperffarm.git;a=summary.

As an example, the PostgreSQL Build Farm site [1] is a central repository for the results of testing source code changes for PostgreSQL as they occur, on a wide variety of platforms.

=====Skills needed=====

* Python programming
* SQL programming

=====Difficulty Level=====

This project requires familiarity with Python programming and basic database experience.

=====Potential Mentors=====

* Mark Wong can mentor.
* Andreas Scherbaum can mentor.
* Pavan Agrawal can mentor.

=====Expected Outcomes=====

* A functional Web site where clients can upload test results, and users can search and review uploaded results.

=====References=====

[1] https://buildfarm.postgresql.org/

==Read/write transaction-level routing in Odyssey (2019)==

=====Project Description=====

Odyssey is an advanced multi-threaded PostgreSQL connection pooler and request router.
Odyssey allows defining client routing rules by specifying client database, client user name and storage connection. In some HA scenarios, it is necessary to define different routing for read-only and read-write transactions.
Odyssey can parse transaction opening statements and assign different routes depending on transaction types.

It would be cool to support many consistency models for reads on standby:
1. Redirecting read query on standby only if standby is lagging no more than X seconds
2. Redirecting read query on standby unless there was recent write (writer should see his writes)
3. Redirecting some read queries on syn or async standby

=====Skills needed=====

* C programming

=====Difficulty Level=====

Moderate.

=====Potential Mentors=====

* Andrey Borodin can mentor.

=====Expected Outcomes=====

* Pull request to Odyssey with described feature

=====References=====

[1] https://github.com/yandex/odyssey

==pgAdmin 4 Query Tool Graphing (2019)==

=====Project Description=====

pgAdmin has a GIS Viewer built into it's Query Tool as the result of a 2018 GSoC Project, that allows the user to render PostGIS shapes and points etc. and view them on a plain canvas or over one of a number of map sources.

This project would be to add a similar capability to allow the user to plot query results in graph formats, for example, selecting column(s) to view on the X/Y axis and then rendering the output as a line chart, bar chart, or even a pie chart.

=====Skills needed=====

* Python
* Javascript/JQuery
* HTML/CSS

=====Difficulty Level=====

Moderate.

=====Potential Mentors=====

* Dave Page

=====Expected Outcomes=====

* Feature committed to the pgAdmin tree for the next release, with documentation and test cases.

=====References=====

[1] https://www.pgadmin.org/

[2] https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=summary

==pgAdmin 4 Query Tool bytea support (2019)==

=====Project Description=====

pgAdmin's Query Tool currently doesn't render bytea data in its Query Tool, or allow options to update such columns. This project would have 2 core aims:

* Update the Query Tool to enable bytea data to be uploaded when editing a row.
* Add viewers to the Query Tool output grid such that when it can be detected that the data in a field is of a known type (image, sound or video file), a button can be displayed in the grid that when clicked will display or play the media.

=====Skills needed=====

* Python
* Javascript/JQuery
* HTML/CSS

=====Difficulty Level=====

Moderate.

=====Potential Mentors=====

* Dave Page

=====Expected Outcomes=====

* Feature committed to the pgAdmin tree for the next release, with documentation and test cases.

=====References=====

[1] https://www.pgadmin.org/

[2] https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=summary

==pgAdmin 4 Query Tool automatic mode detection (2019)==

=====Project Description=====

pgAdmin's Query Tool currently works in 2 different modes:

* View Data mode allows modifications to the SQL Query only through the UI, but allows editing of data when used with a table with an appropriate primary key.
* Query mode allows arbitrary queries to be written and executed, but the user cannot edit the results.

The aim of this project is to automatically detect if the query entered will produce in an updatable resultset and enable/disable editing of the results and other parts of the UI as appropriate (for example, disabling the sort/filter UI options if the query string is not one that can be programmatically changed).

=====Skills needed=====

* Python
* Javascript/JQuery
* HTML/CSS

=====Difficulty Level=====

High.

=====Potential Mentors=====

* Dave Page

=====Expected Outcomes=====

* Feature committed to the pgAdmin tree for the next release, with documentation and test cases.

=====References=====

[1] https://www.pgadmin.org/

[2] https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=summary

==pgBackRest port to Windows (2019)==

=====Project Description=====

pgBackRest is being reimplemented into C currently and it is well on its way. There is already enough of the code in C that it's time to start working on porting pgBackRest to Windows. This project would aim to have all of the C code ported to Windows, which would also include some changes in how pgBackRest operates. The necessary changes for running pgBackRest on Windows have been contemplated during the architecture and design of pgBackRest and therefore should be reasonably straight-forward to implement.

=====Skills needed=====

* C
* Working in a Windows development environment

=====Difficulty Level=====

Medium.

=====Potential Mentors=====

* Stephen Frost
* David Steele

=====Expected Outcomes=====

* pgBackRest able to be built and run on Windows.

=====References=====

[1] https://www.pgbackrest.org/

[2] https://github.com/pgbackrest

==Extract scanning strategy to the separate entity from GiST/GIN/SP-GiST opclasses (2019)==

=====Project Description=====

PostgreSQL offers great indexing extensibility. It supports index access methods which are templates for particular kinds of indexes. Opclasses specify application of access method to particular data type. There could be multiple opclasses for same access method and data type with different capabilities. Moreover, since PostgreSQL 9.6+ index access methods could be user-defined themselves.

However, there are still shortcomings in this extendability system. Opclass specifies particular kind of index and its scanning strategies. One problem is that scanning strategies of opclass can't be extended. For instance, extension could add more spatial operators to built-in GiST opclasses for geometrical datatypes; or fuzzy string matching operators to build-in SP-GiST opclass for text (radix tree). In order to overcome such shortcoming we need to make a scanning strategy a separate entity. Such entity should contain search/order by operators itself as well as corresponding supporting functions such as:

* consistent, distance for GiST,
* inner_consistent and leaf_consistent for SP-GiST,
* extractQuery, consistent, triConsistent and comparePartial for GIN.

=====Skills needed=====

* The ability to read technical papers and documentation to understand index access methods extendability
** http://minds.wisconsin.edu/bitstream/handle/1793/59976/TR1274.pdf
** http://zeus.sai.msu.ru/~megera/postgres/gist/papers/csd-97-950.pdf
** https://www.postgresql.org/docs/current/static/gist.html
** https://www.postgresql.org/docs/current/static/spgist.html
** https://www.postgresql.org/docs/current/static/gin.html
* Ability to refactor system catalog, to find the appropriate places in each of the index AMs to use new entities. Therefore, the ability to navigate over functionality scattered among large and complex project.

=====Difficulty Level=====

The project is difficult from the implementation side, because it requires consistent modification of many places in the source code. Design question doesn't seem to be hard tough.

=====Potential Mentors=====

* Alexander Korotkov can mentor. Alexander is a major contributor and committer.
* Oleg Bartunov can mentor. Oleg is a major contributor.
* Teodor Sigaev can mentor. Teodor is a major contributor and committer.

=====Expected Outcomes=====

The expected outcome is ability of extensions to add new extensions to existing opclasses.

[[Category:Google Summer of Code]]

GSoC 2019

2019-04-13T16:51:23Z

Dfetter: /* Extract scanning strategy to the separate entity from GiST/GIN/SP-GiST opclasses (2019) */

This page is for collecting ideas for future Summer of Code projects.

== Regarding Project Ideas ==

Project ideas are to be added here by community members.

'''NOTE:''' Google wants each idea to be supported by a few sentences and then a list of skills/reqs, difficulty level, potential mentors, expected outcomes, etc. Please add sections in this format.

== Mentors (2019) ==

The following individuals have been listed as possible mentors on the below projects, and/or offered to be mentors for student-proposed projects:

* Stephen Frost
* David Steele
* Andrey Borodin
* Vladimir Leskov
* Dave Page
* Andreas Scherbaum
* Mark Wong

== WAL-G safety features (2019) ==

===== Project Description =====
WAL-G is the simple backup tool for PostgreSQL. Essentially, it supports backup and WAL archiving to cloud storages. WAL-G repository. Currently, we want to improve backup storing. To be more precise, we would like to see implemented following features:
* Retention policy improvement -- currently, we can only delete everything before specified backup or retain fix number of backups. We want to improve backup management, E.g. give user ability to mark important backup permanent to avoid its deletion.
* WAL's history consistency check -- we want to ensure, that we can provide PITR (point in time recovery) for the user.
* Page checksum verification -- it's one of the key features needed for backup verification.

===== Skills needed =====
* Go language
* Ability to read technical papers and documentation to understand PostgreSQL inner structure.
===== Difficulty level =====
Moderate

===== Potential Mentors =====
* Andrey Borodin can mentor. Andrey is WAL-G developer and PostgreSQL contributor.
* Vladimir Leskov can mentor. Vladimir is WAL-G developer.

===== Expected Outcomes =====
All before mentioned features properly implemented, covered with tests and Pull-Requested to WAL-G.

== GiST API advancement (2019) ==

=====Project Description=====
GiST API was designed at the beginning of 90th to reduce boilerplate code around data access methods over a balanced tree. Now, after 30 years, there are some ideas on improving this API.

Opclass developer must specify 4 core operations to make a type GiST-indexable:

1. Split: a function to split set of datatype instances into two parts.

2. Penalty calculation: a function to measure penalty for unification of two keys.

3. Collision check: a function which determines whether two keys may have overlap or are not intersecting.

4. Unification: a function to combine two keys into one so that combined key collides with both input keys.

Functions 2 and 3 can be improved.

For example, Revised R*-tree[1] algorithm of insertion cannot be expressed in terms of penalty-based algorithms. There were some attempts to bring parts of RR*-tree insertion, but they come down to ugly hacks [2]. Current GiST API, due to penalty-based insertion algorithm, does not allow to implement an important feature of RR*-tree: overlap optimization. As Norbert Beckman, author of RR*-tree, put it in the discussion: “Overlap optimization is one of the main elements, if not the main query performance tuning element of the RR*-tree. You would fall back to old R-Tree times if that would be left off.”

Collision check currently returns a binary result:

1. Query may be collides with subtree MBR

2. Query do not collides with subtree

This result may be augmented with a third state: subtree is totally within the query. In this case, GiST scan can scan down subtree without key checks.

The potential effect of these improvements must be benchmarked. Probably, implementation of these two will spawn more ideas on GiST performance improvements.

Another feature of RR*-tree is storing in the page additional MBR. Such additional MBR covers all the entries MBRs just after page creation but don't updated afterwards. Then, when this page is being split, such additional MBR could be used to select better split ration, and in turn in order to have better space utilization. Currently GiST doesn't allow to store some additional datum per page, but it would be nice to have.

Finally, GiST do not provide API for bulk loading. Alexander Korotkov during GSoC 2011 implemented buffered GiST build. This index construction is faster, but yields the index tree with virtually same querying performance. There are different algorithms aiming to provide better indexing tree due to some knowledge of data, e.g. [3]

=====Skills needed=====
*ability to understand searches within GiST
*ability to describe and set up datasets for performance features demostration
*ability to produce committable patch

=====Difficulty Level=====

Easy

=====Potential Mentors=====

* Andrey Borodin can mentor.
* Alexander Korotkov can mentor. Alexander is major contributor and committer.

=====Expected Outcomes=====
Expected outcomes are the benchmark for API features and committable patch implementing them.

=====References=====
[1] Beckmann, Norbert, and Bernhard Seeger. "A revised r*-tree in comparison with related index structures." Proceedings of the 2009 ACM SIGMOD International Conference on Management of data. ACM, 2009.

[2] https://www.postgresql.org/message-id/flat/CAJEAwVFMo-FXaJ6Lkj8Wtb1br0MtBY48EGMVEJBOodROEGykKg%40mail.gmail.com#CAJEAwVFMo-FXaJ6Lkj8Wtb1br0MtBY48EGMVEJBOodROEGykKg@mail.gmail.com

[3] Achakeev, Daniar, Bernhard Seeger, and Peter Widmayer. "Sort-based query-adaptive loading of r-trees." Proceedings of the 21st ACM international conference on Information and knowledge management. ACM, 2012.

== TOAST'ing in slices (2019) ==

=====Project Description=====
Currently, an entire individual value is compressed all together and then stored in data chunks in the TOAST table without an indication of which piece of the original data made it into what chunk of the TOAST table. What this ends up meaning is that to get a subset of the TOAST'd value, all of the chunks (or at least all of them up to the point which is being searched for, if that is known) have to be re-formed and the entire value de-compressed.

=====Project details=====
The best approach to slicing a given value will likely depend on the data type. A text field, for example, would most likely be naturally split upon character (not byte) boundaries, while an array data type would likely be split upon its element boundary. A JSON document might be split in another way (presumably based on how a JSONB is structured). A possible additional task would be to consider if it's possible to include in an index the information about which keys or values exist in a given TOAST chunk. For the JSONB case, in particular, one can imagine that it would eventually be possible to extract out just the JSON chunks which have the key or value being searched for.

=====Skills needed=====
* C skills
* Ability to understand complex on-disk data structures
* Ability to understand inverted indexing
* Ability to understand how traditional compression and block-based compression algorithms function

=====Difficulty Level=====
* Moderate-level

=====Potential Mentors=====

* Stephen Frost can mentor. Stephen is a major contributor and committer.

=====Expected Outcomes=====
Expected outcomes are a patch which implements the ability to split up a single value into known-sized pre-compressed chunks which are then stored in TOAST, and functions able to be optimized based on that knowledge.

----

== de-TOAST'ing using an iterator (2019) ==

=====Project Description=====
Currently, an entire individual value is compressed all together and then stored in data chunks in the TOAST table without an indication of which piece of the original data made it into what chunk of the TOAST table. What this ends up meaning is that to get a subset of the TOAST'd value, all of the chunks (or at least all of them up to the point which is being searched for, if that is known) have to be re-formed and the entire value de-compressed.

=====Project details=====
This project would aim to provide the ability to de-TOAST a fully TOAST'd and compressed field using an iterator, and then update the appropriate parts of the code to use the iterator where possible instead of de-TOAST'ing and de-compressing the entire value. Examples where this can be helpful include using substring() from the beginning of the value, or doing a pattern or substring match. This is distinct and simpler than the above project which envisions a larger change to the TOAST system.

=====Skills needed=====
* C skills
* Ability to understand how traditional compression and block-based compression algorithms function

=====Difficulty Level=====
* Easy-level

=====Potential Mentors=====

* Stephen Frost can mentor. Stephen is a major contributor and committer.

=====Expected Outcomes=====
Expected outcomes are a patch which implements de-TOAST'ing a value using an iterator and then updates to the other parts of the code to use that iterator, resulting in a significant performance improvements for certain queries.

----

==Improve PostgreSQL Regression Test Coverage (2019)==

=====Project Description=====

The current regression test coverage for PostgreSQL isn't great, to the point where some areas of the code are covered only at single-digit-percent levels.

Having good regression tests for such an important project as PostgreSQL is really key to minimizing the chance that any regressions are introduced. While this might seem like a small project, it isn't, particularly when it comes to PostgreSQL. PostgreSQL is over 1.3M lines of code and some of the code paths can be tricky to reach.

The current regression test coverage can be see here: https://coverage.postgresql.org

PostgreSQL's build system includes a "make coverage-html" to generate the report.

Please note that this project involves writing SQL code and Perl code, at a minimum, to implement the tests necessary to increase the code coverage of the PostgreSQL regression tests. This is not a small task as PostgreSQL is currently at only about 73% LOC coverage.

=====Skills needed=====
* Perl, as many PostgreSQL regression tests are written using the Perl TAP system and new ones will likely need to be.
* SQL, to craft tests that hit certain code paths
* Ability to read C code enough to work through a way to get a particular line or lines of code tested.

=====Difficulty Level=====

For someone with the skills listed, even at a relatively beginner level, should make this a very straight-forward if tedious project.

=====Potential Mentors=====

* Stephen Frost can mentor. Stephen is a major contributor and committer and has been working on improving regression tests in PG for quite a while.
* Andreas Scherbaum can mentor. Andreas mentored GSoC and Code-In in the past, and in general helps boosting PostgreSQL in Europe.

=====Expected Outcomes=====

* Significantly improved code coverage for the PostgreSQL regression test suite, ie: 73% -> 80%.

==Enhancing amcheck for all AMs (2019)==

=====Project Description=====

Amcheck is a PostgreSQL extension to verify the integrity of index against invariants that should always hold in the valid index. This tool is designed to diagnose corruption and help developers during the implementation of new features in access methods. Currently, amcheck supports only B-tree. Also, work on GiST is in progress https://github.com/petergeoghegan/amcheck/pull/11
But amcheck could be used for many other indexes: GIN, SP-GiST, BRIN, RUM.
For each AM it is necessary to deduce invariants to check, implement this checks and test against various index states.
Also, it would be useful to unite all AM check methods in a single entry point for checking index.
The interface of check functions can also be enhanced in favor of more detailed corruption information. It would be useful to model various corruptions, including both those which can be found by data_checksums and those which cannot.

=====Skills needed=====
* Good C code skills
* Understanging of access methods ideas and details

=====Difficulty Level=====

The project requires to grasp algorithms behind very sophisticated data structures, along with concurrency and recovery over them.

=====Potential Mentors=====

* Andrey Borodin can mentor. Peter Geoghegan can consult team on controversial cases. Peter Geoghegan is the original author of amcheck.

=====Expected Outcomes=====

* Support for all major PostgreSQL AMs in amcheck.

==Develop Performance Farm Database and Website (2019)==

=====Project Description=====

The PostgreSQL Performance Farm project is a community project to collect performance data from tests as code changes are made to PostgreSQL. To support this effort, a database needs to be created for storing results, and a Web site developed to review results. This project will focus on developing the Web site on top of the database.

The database will be using PostgreSQL in the back-end. Test results will come in the form of JSON and flat files. The Web application will be developed using the Django Web framework.

For reference, the code that will be supplying test results is https://git.postgresql.org/gitweb/?p=pgperffarm.git;a=summary.

As an example, the PostgreSQL Build Farm site [1] is a central repository for the results of testing source code changes for PostgreSQL as they occur, on a wide variety of platforms.

=====Skills needed=====

* Python programming
* SQL programming

=====Difficulty Level=====

This project requires familiarity with Python programming and basic database experience.

=====Potential Mentors=====

* Mark Wong can mentor.
* Andreas Scherbaum can mentor.
* Pavan Agrawal can mentor.

=====Expected Outcomes=====

* A functional Web site where clients can upload test results, and users can search and review uploaded results.

=====References=====

[1] https://buildfarm.postgresql.org/

==Read/write transaction-level routing in Odyssey (2019)==

=====Project Description=====

Odyssey is an advanced multi-threaded PostgreSQL connection pooler and request router.
Odyssey allows defining client routing rules by specifying client database, client user name and storage connection. In some HA scenarios, it is necessary to define different routing for read-only and r\w transactions.
Odyssey can parse transaction opening statements and assign different routes depending on transaction types.

It would be cool to support many consistency models for reads on standby:
1. Redirecting read query on standby only if standby is lagging no more than X seconds
2. Redirecting read query on standby unless there was recent write (writer should see his writes)
3. Redirecting some read queries on syn or async standby

=====Skills needed=====

* C programming

=====Difficulty Level=====

Moderate.

=====Potential Mentors=====

* Andrey Borodin can mentor.

=====Expected Outcomes=====

* Pull request to Odyssey with described feature

=====References=====

[1] https://github.com/yandex/odyssey

==pgAdmin 4 Query Tool Graphing (2019)==

=====Project Description=====

pgAdmin has a GIS Viewer built into it's Query Tool as the result of a 2018 GSoC Project, that allows the user to render PostGIS shapes and points etc. and view them on a plain canvas or over one of a number of map sources.

This project would be to add a similar capability to allow the user to plot query results in graph formats, for example, selecting column(s) to view on the X/Y axis and then rendering the output as a line chart, bar chart, or even a pie chart.

=====Skills needed=====

* Python
* Javascript/JQuery
* HTML/CSS

=====Difficulty Level=====

Moderate.

=====Potential Mentors=====

* Dave Page

=====Expected Outcomes=====

* Feature committed to the pgAdmin tree for the next release, with documentation and test cases.

=====References=====

[1] https://www.pgadmin.org/

[2] https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=summary

==pgAdmin 4 Query Tool bytea support (2019)==

=====Project Description=====

pgAdmin's Query Tool currently doesn't render bytea data in its Query Tool, or allow options to update such columns. This project would have 2 core aims:

* Update the Query Tool to enable bytea data to be uploaded when editing a row.
* Add viewers to the Query Tool output grid such that when it can be detected that the data in a field is of a known type (image, sound or video file), a button can be displayed in the grid that when clicked will display or play the media.

=====Skills needed=====

* Python
* Javascript/JQuery
* HTML/CSS

=====Difficulty Level=====

Moderate.

=====Potential Mentors=====

* Dave Page

=====Expected Outcomes=====

* Feature committed to the pgAdmin tree for the next release, with documentation and test cases.

=====References=====

[1] https://www.pgadmin.org/

[2] https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=summary

==pgAdmin 4 Query Tool automatic mode detection (2019)==

=====Project Description=====

pgAdmin's Query Tool currently works in 2 different modes:

* View Data mode allows modifications to the SQL Query only through the UI, but allows editing of data when used with a table with an appropriate primary key.
* Query mode allows arbitrary queries to be written and executed, but the user cannot edit the results.

The aim of this project is to automatically detect if the query entered will produce in an updatable resultset and enable/disable editing of the results and other parts of the UI as appropriate (for example, disabling the sort/filter UI options if the query string is not one that can be programmatically changed).

=====Skills needed=====

* Python
* Javascript/JQuery
* HTML/CSS

=====Difficulty Level=====

High.

=====Potential Mentors=====

* Dave Page

=====Expected Outcomes=====

* Feature committed to the pgAdmin tree for the next release, with documentation and test cases.

=====References=====

[1] https://www.pgadmin.org/

[2] https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=summary

==pgBackRest port to Windows (2019)==

=====Project Description=====

pgBackRest is being reimplemented into C currently and it is well on its way. There is already enough of the code in C that it's time to start working on porting pgBackRest to Windows. This project would aim to have all of the C code ported to Windows, which would also include some changes in how pgBackRest operates. The necessary changes for running pgBackRest on Windows have been contemplated during the architecture and design of pgBackRest and therefore should be reasonably straight-forward to implement.

=====Skills needed=====

* C
* Working in a Windows development environment

=====Difficulty Level=====

Medium.

=====Potential Mentors=====

* Stephen Frost
* David Steele

=====Expected Outcomes=====

* pgBackRest able to be built and run on Windows.

=====References=====

[1] https://www.pgbackrest.org/

[2] https://github.com/pgbackrest

==Extract scanning strategy to the separate entity from GiST/GIN/SP-GiST opclasses (2019)==

=====Project Description=====

PostgreSQL offers great indexing extensibility. It supports index access methods which are templates for particular kinds of indexes. Opclasses specify application of access method to particular data type. There could be multiple opclasses for same access method and data type with different capabilities. Moreover, since PostgreSQL 9.6+ index access methods could be user-defined themselves.

However, there are still shortcomings in this extendability system. Opclass specifies particular kind of index and its scanning strategies. One problem is that scanning strategies of opclass can't be extended. For instance, extension could add more spatial operators to built-in GiST opclasses for geometrical datatypes; or fuzzy string matching operators to build-in SP-GiST opclass for text (radix tree). In order to overcome such shortcoming we need to make a scanning strategy a separate entity. Such entity should contain search/order by operators itself as well as corresponding supporting functions such as:

* consistent, distance for GiST,
* inner_consistent and leaf_consistent for SP-GiST,
* extractQuery, consistent, triConsistent and comparePartial for GIN.

=====Skills needed=====

* The ability to read technical papers and documentation to understand index access methods extendability
** http://minds.wisconsin.edu/bitstream/handle/1793/59976/TR1274.pdf
** http://zeus.sai.msu.ru/~megera/postgres/gist/papers/csd-97-950.pdf
** https://www.postgresql.org/docs/current/static/gist.html
** https://www.postgresql.org/docs/current/static/spgist.html
** https://www.postgresql.org/docs/current/static/gin.html
* Ability to refactor system catalog, to find the appropriate places in each of the index AMs to use new entities. Therefore, the ability to navigate over functionality scattered among large and complex project.

=====Difficulty Level=====

The project is difficult from the implementation side, because it requires consistent modification of many places in the source code. Design question doesn't seem to be hard tough.

=====Potential Mentors=====

* Alexander Korotkov can mentor. Alexander is a major contributor and committer.
* Oleg Bartunov can mentor. Oleg is a major contributor.
* Teodor Sigaev can mentor. Teodor is a major contributor and committer.

=====Expected Outcomes=====

The expected outcome is ability of extensions to add new extensions to existing opclasses.

[[Category:Google Summer of Code]]

Performance Optimization

2019-04-10T01:15:28Z

Dfetter: /* Removed extremely obsolete links. */

{{Languages}}

== How to Effectively Ask Questions Regarding Performance on Postgres Lists ==
* [[Slow_Query_Questions]]

== General Setup and Optimization ==
* [[Tuning Your PostgreSQL Server]] by Greg Smith, Robert Treat, and Christopher Browne
* [http://www.revsys.com/writings/postgresql-performance.html Performance Tuning PostgreSQL] by Frank Wiles
* [http://linuxfinances.info/info/quickstart.html QuickStart Guide to Tuning PostgreSQL] by Christopher Browne
* [http://www.varlena.com/GeneralBits/Tidbits/perf.html Performance Tuning] by Josh Berkus and Shridhar Daithankar
* [http://old.zope.org/Members/pupq/pg_in_aggregates/howto_view Replacing Slow Loops in PostgreSQL] by Joel Burton
* [http://momjian.us/main/writings/pgsql/hw_performance/ PostgreSQL Hardware Performance Tuning] by Bruce Momjian
* [http://www.targeted.org/articles/databases/fragmentation.html The effects of data fragmentation in a mixed load database] by Dmitry Dvoinikov
* [http://www.craigkerstiens.com/2012/10/01/understanding-postgres-performance/ Understanding Postgres Performance] by Craig Kerstiens
* [http://www.craigkerstiens.com/2013/01/10/more-on-postgres-performance/ More on Postgres Performance] by Craig Kerstiens
* [https://www.citusdata.com/blog/2016/10/12/count-performance/ Faster PostgreSQL counting]
* [https://medium.com/pgmustard/row-count-estimates-in-postgres-8540087a826e/ Row count estimates in Postgres] by David Conlin
* [https://medium.com/pgmustard/index-only-scans-in-postgres-a1603f551ee/ Index-only scans in Postgres] by David Conlin

Performance courses are available from a number of companies. Check [http://www.postgresql.org/about/eventarchive events and trainings] for further details.

==Critical maintenance for performance==
*[[Introduction to VACUUM, ANALYZE, EXPLAIN, and COUNT]] by Jim Nasby.
*[[VACUUM FULL]] and why you should avoid it
*[[Planner Statistics]]
*[[Using EXPLAIN]]
*[[Logging Difficult Queries]]
*[[Logging Checkpoints]]
*[[Bulk Loading and Restores]]
*[[Performance Analysis Tools]] by Craig Ringer

== Database architecture ==
* [[Priorities|Limiting and prioritizing user/query/database resource usage]] by Craig Ringer
* [[Prioritizing databases by separating into multiple clusters]] by Craig Ringer
* [[Clustering]]
* [[Shared Storage]]

==Database Hardware Selection and Setup==
* [[Database Hardware]]
* [[Reliable Writes]]

==Benchmark Workloads==
* [[:Category:Benchmarking]]

[[Category:Administration]][[Category:Performance]][[Category:Benchmarking]]
[[Category:General articles and guides]]

Community Guide to PostgreSQL GUI Tools

2019-04-10T01:11:11Z

Dfetter: /* SQuirrel */

{{Languages}}

== Alternate Guides ==

Another detailed summary from 2009 is available at
[http://www.postgresonline.com/journal/index.php?/archives/133-Database-Administration,-Reporting,-and-Light-application-development.html Database Administration, Reporting, and Light application development]

== Open Source / Free Software ==

=== pgAdmin 4 ===

http://www.pgadmin.org/

MS Windows, GNU/Linux, FreeBSD, Mac OS X, OpenBSD, Solaris

Admin

pgAdmin III is an Open Source management tool for PostgreSQL databases. Features full Unicode support, fast, multithreaded query and data editing tools and support for all PostgreSQL object types.

pgAdmin III is bundled with the Windows installer, and you can use that such a client to administer a remote server on another OS. Note that binary packages for platforms like RPM don't show up in every point release, you currently have to go back to v1.8.0 to get the last full set of packages.

Free Administration Centre for the PostgreSQL database. Includes a graphical administration interface, an SQL query tool, a procedural code editor and much more. pgAdmin III is designed to answer the needs of most users, from writing simple SQL queries to developing complex databases. The graphical interface supports all PostgreSQL features and makes administration easy. Available in more than 30 languages and for several operating systems.

=== phpPgAdmin ===

http://sourceforge.net/projects/phppgadmin

browser-based, requires webserver

Admin

Similar to the ever-popular phpMyAdmin, enhanced for PostgreSQL, supports browsing and modification of most types of PostgreSQL database objects, plus execution of ad-hoc queries. Maintained by (who else?) the phpPgAdmin team. (JMB 11.2002).

phpPgAdmin (and the required Apache and PHP packages) may be easily installed using Stack Builder if you are running a one-click-installer PostgreSQL distribution.

=== SQuirrel ===

http://www.squirrelsql.org/

Platforms that support Java

Admin

SQuirreL SQL Client is a graphical Java program that will allow you to view the structure of a JDBC compliant database, browse the data in tables, issue SQL commands etc. The minimum version of Java supported is 1.8.x as of SQuirreL version 3.8.1.

=== Adminer ===

http://www.adminer.org

browser-based, requires webserver

Adminer (formerly phpMinAdmin) is a full-featured database management tool written in PHP. Conversely to phpMyAdmin, it consist of a single file ready to deploy to the target server. Adminer is available for MySQL, PostgreSQL, SQLite, MS SQL and Oracle.

=== Libre Office ===

http://www.libreoffice.org/download/3-5-new-features-and-fixes/

New native driver for PostgreSQL databases (for versions > 8.4 - support for version 8.4 will be included in LibreOffice 3.5.1).

=== GNOME-DB ===

http://www.gnome-db.org

Linux, Unix

Admin

Database administration/user tool for GNOME, based on libgda/libgnomedb, which are a complete database-independent access layer for UNIX systems, with support for PostgreSQL, MySQL, Sybase, MS SQL Server, Oracle, Interbase/Firebird, MS Access files, xBase.

=== TOra, an Oracle tool with some PostgreSQL support ===

http://tora.sf.net/

Linux & Windows

Admin

An Oracle database administration interface, with limited ability to browse PostgreSQL databases (tables, views, and functions only). I'm told that if you have the Oracle libraries, Tora's sophisticated function editor will work for PostgreSQL as well. Developed by Henrik Johnson as a Quest Toad clone. (JMB 11.2002)

=== Kexi ===

http://www.kexi-project.org/

Kexi is part of the Calligra Suite and is released under the GNU General Public License (GPL) and LGPL.

available for
FreeBSD & Linux, Apple, Windows, (Android)

=== SQL Workbench/J ===

http://www.sql-workbench.net

Java (multi-platform)

An OpenSource SQL GUI tool similar to Squirrel. Data can be edited directly in the result set. It has strong support for exporting and importing data between databases using its own SQL command extension. It can be used in GUI mode or as a console application. All SQL Workbench specific commands can also be run in batch mode to automate export and import task. It supports schema comparison ("diff") and copying data between databases.

=== Druid III ===

http://druid.sourceforge.net/

Java (multi-platform)

The druid is a tools that allows users to create databases in a graphical way. The user can add tables, fields, folders to group tables and can modify most of the database options that follow the SQL-92 standard. In addition to sql options, the user can document each table and each field with HTML information. Once the database is created, the druid can generate:

* HTML documentation: for all tables, with browsing facilities
* PDF documentation: for all tables
* Java classes: (one class for each table) that contain tables' constants (such as fields size) plus java code added by the user
* A data dictionarythat contains all tables and fields present in the database
* SQL script which contains all table definitions that can be piped to the DBMS
* And much more info...

=== Power*Architect ===

http://www.sqlpower.ca/page/architect

Java (multi-platform)

Power*Architect is an ERD modelling tool that is based on Java and JDBC. Support for forward and reverse engineering PostgreSQL databases is supported. It's OpenSource with a GPL license.

=== RISE PostgreSQL code generator ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1889

Windows

The RISE PostgreSQL code generator generates native PL/pgSQL scripts. Model your information in the free RISE Editor and generate your database script. The script incrementally updates the tables, columns, indexes and constraints in the database to match the RISE model. Once the database model is updated, the views defined in the RISE model are created in the database and possible default data, entered in the model, is inserted.

=== Open Source CMS ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=2017

Windows

The CMS is a free Visual Studio 2010 solution template with a set of projects providing a complete Content Management System (CMS) based on RISE Visual Modeling with model, full source, sample site and DB-scripts for PostgreSQL, MySQL and SQL Server.

It’s a complete ready-to-run Visual Studio solution with model, source code and web clients. It illustrates how to use RISE, how to implement a SOA backend and how to build RIA frontends.

=== DBeaver ===

http://dbeaver.jkiss.org/

Eclipse/Java (multi-platform)

Eclipse-based environment, supporting many SQL databases from different vendors, as well as few NoSQL ones (Cassandra, etc).
Good query editor with syntax highlighting, completion and autosave.
Editing of query results. SSH tunneling support. Tons of other cool features.
Quite good, but not 100% perfect PostgreSQL support (yet?). Regularly updated, as of 2018.

=== OmniDB ===

https://github.com/OmniDB/OmniDB

Linux, Windows and macOS

Open source full-featured tool for database management. Currently supports PostgreSQL (9.3 - 11), Oracle (11g - 18c), MySQL (5.6 - 8.0) and MariaDB (10.1 - 10.3). More RDBMS support coming soon, including the ability of converting databases from any supported RDBMS to PostgreSQL and back.

=== Postbird ===

https://github.com/paxa/postbird

MacOs

Open source, desktop application to manage your local or remote PostgreSQL databases.

=== Sohag Developer ===
[http://sohag-developer.com/ Sohag Developer]

Gnu/Linux Windows (Other OS can compile from source code).

Build a powerful database applications following few steps using Sohag Developer .
Sohag Developer currently supports PostgreSQL database and has a set of generators that generates (Qt/C++ code and ui forms - PHP web applications uses web forms and bootstrap framework ) to manipulate the data in the database tables or views.

=== PASH-Viewer: PostgreSQL Active Session History Viewer ===
https://github.com/dbacvetkov/PASH-Viewer

Java (multi-platform).

Open-source software which provides graphical view of active session history and help you to answer questions like "What wait events were taking most time?", "Which sessions were taking most time?", "Which queries were taking most time and what were they doing?". It also supports Active Session History extension by pgsentinel.

=== pgrights: GUI for PostgreSQL roles, privileges and policies ===
https://github.com/apsavin/pgrights

MacOS (based on Electron, so versions for other OS can be build from source code).

Open-source software which allows you to easely understand what can do (and what can't) a PostgreSQL user with a table's data. In other words, it's a viewer of results of GRANT commands and row-level security rules applied for a particular table and for a particular role.

== Proprietary ==

=== SQLGate ===

https://www.sqlgate.com/product/download

Windows

SQLGate is a simple but powerful IDE for multiple Database including PostgreSQL.

* Powerful Data Grid and ERD

* Multiple SQL Execution

* Auto-Complete

* Intuitive UI/UX

* Multiple Themes

* Fast processing speed

Use SQLGate to maximize your productivity!

=== dbForge Studio for PostgreSQL ===

https://www.devart.com/dbforge/postgresql/studio/

PostgreSQL GUI tool for managing and developing databases and objects. The IDE for PostgreSQL allows users to create, develop, and execute queries, edit and adjust the code to your requirements in a convenient and user-friendly interface. It comes in two editions - Standard and Express (free).

Key features:
* SQL Development
* Database Explorer
* Data Editor
* Data Export and Import
* Pivot Table
* Master-Detail Browser
* Data Reports

=== PSequel ===

http://www.psequel.com/

OS X Yosemite only, free, "Sequel Pro" inspired.

=== EMS SQL Manager for PostgreSQL Freeware ===

http://www.sqlmanager.net/en/tools/free

Windows

EMS SQL Manager for PostgreSQL Freeware (EMS SQL Manager Lite for PostgreSQL) is an excellent and easy-to-use freeware graphical tool for PostgreSQL database administration. It has the minimal required set of tools for those users who are new to PostgreSQL server and need only its basic functionality.
EMS SQL Manager for PostgreSQL Freeware allows you to work with servers, databases and schemas, view, edit, search, group, sort and filter any data stored in a database, create and execute SQL queries with powerful SQL editor, handle multiple selected objects at a time and much more.

=== Marshal SQL Utility ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1756

Windows

The Marshal SQL Utility is a generic cross database utility with batch execution capabilities. It allows you to test ODBC connections, browse database schemas, discover tables, views and columns.

Key features of Marshal SQL Utility:

* Execute any query supported by your database server
* Execute batches of queries
* Discover tables and views in your database
* Discover columns for a selected table or view
* Supports BLOBS and CLOBS
* Save your results to file
* Use any ODBC compliant database such as PostgreSQL.

=== RISE PHP for PostgreSQL code generator ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1888

Windows

The RISE PHP for PostgreSQL code generator renders PHP source code for database access. Model your information and programming interfaces in the free RISE Editor and generate your code. The generated code implements the classes and methods corresponding to the information interfaces specified in the RISE model. This includes classes for database access and, optionally, classes implementing SOAP/JSON web services and proxy classes assisting the implementation of a PHP SOAP client.

=== RISE - Model Driven Development using ERD / UML ===

http://www.risetobloome.com

Windows

RISE is a free software suite for model driven information system development. Use a single source RISE model to generate your entire information solution including database, web services and documentation. Boost development throughput and improve quality and maintainability!

The RISE user experience is based on a project concept, similar to that of most integrated development environments. The user works with resources and drawings that are part of a single development project.

RISE supports a fully graphical approach to information modeling and system engineering, using ERD (Entity Relationship Diagram) as well as UML (Unified Modeling Language). This includes drag-and-drop of entities, their attributes and relations, as well as of views and entire web services.

RISE supports graphic editing of complex objects such as views and orchestrated methods. RISE automatically safeguards the combination process, thus, assuring a technically correct result.

RISE provides several ways to generate code from the model; directly to file, via the RISE Server or as an Internet service. RISE provides code generators for the database layer (SQL/DDL) as well as for the server side application layer (web services and persistent classes). All database scripts are incremental allowing you to install and maintain any number of databases from a single model.

Feature list
http://www.risetobloome.com/Page_1_S.aspx?ITEM=1355

=== WaveMaker Ajax GUI Design Tool ===

http://www.wavemaker.com/

Windows, Macintosh, Linux

WaveMaker is an Ajax-based GUI design tool for Postgres. WaveMaker is built using itself! WaveMaker generates a standard Java WAR file based on Spring, Hibernate and Dojo. WaveMaker supports Postgres schema creation and import and includes a visual query editor.

=== AnySQL Maestro ===

http://www.sqlmaestro.com/products/anysql/maestro/

Windows

AnySQL Maestro is a freeware tool for administering any database engine (PostgreSQL, SQL Server, Oracle, MySQL, MS Access, etc.), which is accessible via ODBC driver or OLE DB provider. Includes Database Designer, Visual Query Builder, BLOB Viewer/Editor, SQL Editor, Data export/import and other features.

=== TeamPostgreSQL ===

http://www.teampostgresql.com

browser-based, webserver included

AJAX/JavaScript-powered web interface for PostgreSQL administration. Browse, maintain and create data and database objects from anywhere, in the web browser. Supports SSH for both the web interface and the database connections. Rich interface with tabbed SQL editor with auto-completion, inline row-editing widgets, click-through foreign key navigation between rows and tables, 'favorites' management for commonly used scripts, and more.

Installers available for Windows, Mac and Linux, alternatively download a simple cross-platform archive that runs anywhere with simple script.

=== Postgres Compare ===

[[File:Postgres_compare.png|thumb|left|frameless]]

https://www.postgrescompare.com/

Windows, Mac & Linux

A comprehensive tool for identifying the differences between databases and generating an update script to synchronize them. Postgres Compare reads the system catalogs to determine the structure of the database and compares it to another to find the changes. Generate SQL and deploy the alterations, save snapshots for later. Automate the process via the command line.

Alpha build available now https://www.postgrescompare.com/downloads

<div style="clear:both;"></div>

=== JetBrains IDEs - DataGrip, IntelliJ IDEA, PHPStorm, PyCharm, RubyMine, etc ... ===

http://www.jetbrains.com/

Windows, Mac OS X, Linux

JetBrains has a dedicated SQL IDE — DataGrip which can connect to PostgreSQL as well. It provides code completion, multi cursors, local query history, navigation, refactorings and language injection support.
https://www.jetbrains.com/datagrip/

Other JetBrains Products, for example, PHPStorm, have built-in database plugin, and it has the same functionality as DataGrip.

After you configured the data sources of your project, you can easily create tables, foreign keys, indexes much easier than usual, because the IDE is very smart; for example by foreign keys it automatically sets the name of the key and the related columns. For me, it is so far the best experience by creating a basic database schema. Even with editable EER models was it slower...
By the settings of [http://goo.gl/TuqiPRpantun romantis terbaru] your data source you can configure the SQL dialect of your database. After that, if you want to add stored procedures or triggers, you will have code completion which is favorable too. So I think JetBrains products speed up your work if you exactly know what you want, and how can you make it.

For any JetBrains IDE, there is a free license for open source projects. For enterprise usage there is a 30 days trial, after that, you can buy a personal or proprietary license which is very cheap compared to other products.

For PyCharm (even the Community Edition) you can install the free third-party plugin [http://confluence.jetbrains.com/display/CONTEST/Database+Navigator Database Navigator] (Settings -> IDE Settings -> Plugins). It appears to deliver the same functionality described above for PHPStorm. You will get a new menu DB Navigator, left to the Help menu.

=== TablePlus ===

https://tableplus.io/

macOS

A modern, native tool with an elegant UI that allows you to simultaneously manage multiple databases, including PostgreSQL.

* True native built.

* Workspace supports multiple tabs, multiple windows

* Powerful SQL editor with full features: auto syntax highlight, auto-suggestion, split pane, favorite and history.

* Data Filter & Sorting, import & export

* Full-dark theme & modern shortcut

With plugin system, you can be able to write your own new features to work with database per your needs (export charts, pretty json…).

=== SQLPro for Postgres ===

http://www.hankinsoft.com/SQLProPostgres

Mac OS X 10.8 and above

Features:
* 100% native OS X app with a clean and simple to use interface.
* Query editor with syntax highlighting and autocomplete.
* Support for multiple result set execution.
* History feature, displaying your last ten executed queries.
* Primary key detection for inline result set modifications.
* Custom theme support allowing developers to work with style.

=== Postico ===

https://eggerapps.at/postico/

Mac OS X

Postico is a fully native Mac app for connecting to your PostgreSQL server. It supports encrypted connections via SSL and SSH to PostgreSQL 8.0 and later, including Amazon Redshift.

Postico has a powerful table content editor with in-cell editing and form-based row editing in a sidebar. You can quickly filter tables by keywords or even complex SQL expressions.

There's also a table structure editor for editing columns, types, default values, foreign keys, check constraints etc.

Finally, there's a convenient SQL Query Editor with support for query history and syntax highlighting. It also has convenience features like auto-indent and shortcuts for comment line etc.

=== SEQUEL for PostgreSQL ===

http://www.sequel.tech

macOS

SEQUEL for PostgreSQL is a professional DB administration and management tool, with extremely intuitive and feature-rich GUI that makes it the best assistant tool for developers and admins. SEQUEL is lightweight, fast and powerful that it can significantly simplify the DB management process. For those who cannot live without a CLI, SEQUEL offers a powerful Query Editor with syntax highlight, autocomplete and a Console log view that is always visible, so you can monitor the communication with your databases. It includes:

* Database management forms for Schema, Table, Index, Foreign key, Trigger, Rule, Sequence, Collation, Domain, Enum type, Tablespace and Language objects with full parameters support
* Assistant info views for Object information, Actions, Help, and Documentation
* Jump bar for quick objects selection and navigation
* Taskbar with multi-task monitoring support
* Console log view
* Syntax highlight, autocomplete, current and selection query execution and explain, line numbering and working statement detection
* Direct editing in the results view, query results explanation
* Powerful Field editor
* Transaction based database updates
* Code preview and Content editing

=== dbForge Data Compare for PostgreSQL ===

http://www.devart.com/dbforge/postgresql/datacompare/

Microsoft Windows 2000/XP/2003/Vista and Windows 7, 8, 10

'''dbForge Data Compare for PostgreSQL''' by '''Devart''' is a tool for table data comparison and synchronization. When using PostgreSQL data compare tool developer can detect data differences in compared PostgreSQL tables; generate data synchronization script and execute it to eliminate all these differences.

'''Key features:'''

* Identify the differences between two databases
* Compare separate tables or table groups by table name mask
* Compare tables with different structure
* Generate a report embodying data diff and save it for further analysis
* Sync data in tables and views in full or in part
* Generate SQL script for database synchronization
* Organize database synchronization according to the schedule

=== Full Convert ===

https://www.spectralcore.com/fullconvert

Database conversion and synchronization between PostgreSQL and Microsoft Access, dBase, FoxPro, Microsoft Excel, Firebird, Interbase, MySQL, Oracle, Paradox, Microsoft SQL Server, SQL Server, SQL Server Azure, SQL Server Compact(SQLCE), SQLite, Delimited text files (CSV), XML and many more via ODBC.

=== Replicator Pro ===

https://www.spectralcore.com/replicator

Replicator allows table data comparison and sync - even with heterogeneous databases. It is unique in the fact it can replicate changes only even if source is non-relational (CSV, DBF, Excel documents, Paradox...). Replicator has a built-in scheduler for easy periodic change replication.

=== Nucleon Database Master for PostgreSQL and Others ===

Nucleon Database Master is a modern, powerful, intuitive, easy to use and all in one PostgreSQL MongoDB, Oracle, DB2, Informix, Ingres, SQL Server, SQL Azure, MySQL, FireBird, SQLite client application with a consistent interface that simplifies managing, querying, editing, visualizing, designing and [http://mitraharga.blogspot.co.uk/2014/09/harga-tablet-pc-axioo.htmlharga tablet axioo] reporting relational and schema-free (NoSQL) database systems. You can connect any database system via ODBC and OleDB connections.Using Database Master, you can execute SQL, LINQ, JSON queries or you can create, edit and delete all database objects such as tables, views, procedures, columns, indexes, collections, and triggers. You can execute SQL queries and scripts, view and edit table data including BLOBs (Image, Text or any file), represent tables and its relations as an ER(Entity Relationship) diagram.

Info:
http://www.nucleonsoftware.com/
Windows, other platforms via WINE
Admin

=== DBTools Manager ===

http://www.dbtools.com.br

Windows

Admin

Freeware, available for PostgreSQL and MySQL, allows managing all aspects of the database: db, table, triggers, functions, etc. Includes import/export wizards to migrate data and structure to/from other database engines. Developed by DBTools Software.

=== PgManager ===

http://www.ems-hitech.com/pgmanager

Windows, Linux version just released

Admin

Basically a proprietary, more powerful version of PGAdmin II or PGAccess. Adds support for trigger and constraint editing, metadata logging, and query monitoring. Also includes multiple-format data import/export tools, which are also available on their own for Linux. Developed by EMS Hitech. (JMB 4.2003).

=== DeZign for Databases ===

http://www.datanamic.com

Windows

ERD

DeZign is a database development tool using an entity relationship diagram. It visually supports the layout of the entities and relations and automatically generates SQL schemas for most leading databases including PostgreSQL.

=== Case Studio 2 / Toad Data Modeler ===

http://www.casestudio.com/enu/index.aspx

Windows

ERD

Commenter 1: I just downloaded the trial version, so far it looks really promising and claims to support PostgreSQL. Handles reverse engineering of existing databases, and has a really nice interface for setting up tables, relationships etc. You can get a lite or full version. The description from the website... Professional database modeling tool for various databases. CASE Studio 2 includes following key features:

LITE version features + Reverse Engineering from various database systems Version Manager Data Flow Diagrams Definition of user-defined variables Large COM interface Users, User groups and User permission support and many more.

Case Studio was acquired, and renamed 'Toad Data Modeler'.

Commenter 2: I've used the licensed version before and after the name change. PostgreSQL support is excellent.

=== PostgreSQL PHP Generator ===

http://www.sqlmaestro.com/products/postgresql/phpgenerator/

Windows

PostgreSQL PHP Generator is a freeware but powerful PostgreSQL GUI frontend that allows you to generate high-quality PHP scripts for the selected tables, views and queries for the further working with these objects through the web.

=== pgEdit ===

http://pgedit.com

Macintosh
pgEdit is a high-performance SQL editor and development environment designed specifically for PostgreSQL relational databases. pgEdit features include SQL syntax coloring, direct source code execution, PHP support, integrated documentation, and extensive customizable editing facilities.

pgEdit uses psql, the interactive terminal application included with every PostgreSQL installation. This makes it easy to develop with pgEdit and then transfer your work to any PostgreSQL installation for maintenance and production tasks.

pgEdit is a native application for both Macintosh and Windows. It does not use Java or require installation of external libraries. You have the option of using the version of psql included with pgEdit or a different version installed anywhere on your hard drive.

=== RazorSQL ===

http://www.razorsql.com/

Macintosh/Windows/Linux/Solaris

RazorSQL is an SQL query tool, database browser, SQL editor, and database administration tool that supports PostgreSQL and any other JDBC or ODBC compliant database. Some of the major features are tools for creating, dropping, and altering objects such as tables, views, indexes, triggers, functions, users, and databases; a programming editor that supports 20 different programming languages; import and export tools; auto column and table lookup; and a query builder, query scheduler, and SQL formatter.

=== MicroOLAP Database Designer ===

http://www.microolap.com/products/database/postgresql-designer/

Windows ODBC

Database Designer for PostgreSQL is an easy CASE tool with an intuitive graphical interface allowing you to build a clear and effective database structure visually, see the complete picture (diagram) representing all the tables, references between them, views, stored procedures and other objects. Then you can easily generate a physical database on a server, modify it according to any changes you made to the diagram using fast ALTER statements.

=== Import / Export and synchronization tools for PostgreSQL ===

http://convertdb.com/postgresql

Microsoft Windows 8 / 7 / Vista / XP / 2000 / NT.
The software is able to connect to remote PostgreSQL 9.x/7.4 located on Linux, Solaris, Mac OS X, and Windows.

ConvertDB cross-database migration tools assist in data conversion and synchronization among PostgreSQL, MySQL, MS SQL Server, MS Windows SQL Azure, and MS Access databases

* 1 Million of records can be transferred in 5-10 minutes.
* Bi-directional synchronization between PostgreSQL, MS SQL, MySQL and Oracle
* Scheduling migration and synchronization jobs.

=== dbForge Studio for PostgreSQL ===

https://www.devart.com/dbforge/postgresql/studio/

Microsoft Windows 7, 8, 10

'''dbForge Studio for PostgreSQL''' is a brand new tool for PostgreSQL databases development, management, and editing process enjoyable and easy by Devart. The PostgreSQL IDE allows users to create, develop, and execute queries, edit and adjust the code to the requirements in a convenient and UI. The tool provides the PostgreSQL data editor functionality for queries customization and property window for the viewing all the required information of PostgreSQL database objects.

'''Key features:'''

* Code Completion helps to improve code quality when creating and editing queries with List Members, Parameter Info, Quick Info, Complete Word.
* Object Explorer for easy navigation through the object tree. You can retrieve data from the database on a single SQL document, truncate a table, select Properties to view some information on the object.
* Data Editor for management settings of tables, such as adjust column width, set either paginal or auto-search mode by default. Color and format rows and cells using a rich set of fonts and size. The tool has predefined data type formats to meet your own needs.

=== dotConnect for PostgreSQL ===

https://www.devart.com/dotconnect/postgresql/

Windows

'''dotConnect for PostgreSQL''', formerly known as PostgreSQLDirect .NET, is an enhanced ORM enabled data provider for PostgreSQL that builds on ADO.NET technology to present a complete solution for developing PostgreSQL-based database applications. It introduces new approaches for designing application architecture, boosts productivity, and leverages database applications.

'''Key features:'''

* Direct Mode
* Database Application Development Extension
* PostgreSQL Advanced Features Support
* Optimized Code
* ORM Support
* BIS Support

=== PostgreSQL Data Access Components ===

Windows

https://www.devart.com/pgdac/

PostgreSQL Data Access Components (PgDAC) is a library of components that provides native connectivity to PostgreSQL from Delphi, C++Builder, Lazarus (and Free Pascal) on Windows, Mac OS X, iOS, Android, Linux, and FreeBSD for both 32-bit and 64-bit platforms. PgDAC is designed to help programmers develop really lightweight, faster and cleaner PostgreSQL database applications without deploying any additional libraries.

Native Connectivity to PostgreSQL
PgDAC is a complete replacement for standard PostgreSQL connectivity solutions and presents an efficient alternative to the Borland Database Engine (BDE) and standard dbExpress driver for access to PostgreSQL. It provides direct access to PostgreSQL without PostgreSQL Client.

=== ODBC Driver for PostgreSQL ===

https://www.devart.com/odbc/postgresql/

Windows

Devart ODBC Driver for PostgreSQL provides high-performance and feature-rich connectivity solution for ODBC-based applications to access PostgreSQL databases from Windows, both 32-bit and 64-bit. Full support for standard ODBC API functions and data types implemented in our driver makes the interaction of your database applications with PostgreSQL fast, easy and extremely handy.

=== Excel Add-in for PostgreSQL ===

https://www.devart.com/excel-addins/postgresql.html

Windows

Devart Excel Add-in for PostgreSQL allows you to quickly and easily connect Microsoft Excel to PostgreSQL, load data from PostgreSQL to Excel, instantly refresh data in an Excel workbook from the database, edit these data, and save them back to PostgreSQL. It enables you to work with PostgreSQL data like with usual Excel worksheets, easily perform data cleansing and de-duplication, and apply all the Excel's powerful data processing and analysis capabilities to these data.

=== EMS Database Management Tools for PostgreSQL ===

http://www.sqlmanager.net/en/products/postgresql

Windows

PostgreSQL Tools Products Family:

* [http://www.sqlmanager.net/en/products/studio/postgresql SQL Management Studio for PostgreSQL] - a single workbench for administering PostgreSQL databases, managing database schema and objects as well as for database design, migration, extraction, query building, data import, export, and database comparison.

* [http://www.sqlmanager.net/en/products/postgresql/manager SQL Manager for PostgreSQL] - high performance graphical tool for PostgreSQL database administration and development. It makes creating and editing PostgreSQL database objects easy and fast, and allows you to run SQL scripts, visually design databases, build SQL queries, extract, print and search metadata, import and export PostgreSQL database data and much more.

* [http://www.sqlmanager.net/en/products/postgresql/dataexport Data Export for PostgreSQL] - tool to export PostgreSQL database data quickly to any of 19 available formats, including MS Access, MS Excel, MS Word, RTF, HTML, TXT, ODF and more. Data Export for PostgreSQL has a [http://aurora-ndut.blogspot.fr/2013/10/kata-kata-lucu.htmlkata kata lucu] friendly wizard, which allows you to set various options of PostgreSQL export process visually and a command-line utility to automate your PostgreSQL export jobs using the configuration file.

* [http://www.sqlmanager.net/en/products/postgresql/dataimport Data Import for PostgreSQL] - tool to import data to PostgreSQL tables from MS Excel 97-2007, MS Access, DBF, TXT, CSV, MS Word 2007, RTF, ODF and HTML files. This utility allows you to quickly import data to one or several PostgreSQL tables or views at once, save all PostgreSQL import parameters set on current wizard session, use special batch insert mode to import PostgreSQL data at the maximum possible speed and much more.

* [http://www.sqlmanager.net/en/products/postgresql/datapump Data Pump for PostgreSQL] - migration tool for converting databases and importing table data from an ADO-compatible source (e.g. MS Access, MS SQL database or any other database with ADO support) to PostgreSQL databases.

* [http://www.sqlmanager.net/en/products/postgresql/datagenerator Data Generator for PostgreSQL] - tool for generating test data to PostgreSQL database tables. The utility can help you to simulate the database production environment and allows you to populate several PostgreSQL database tables with test data simultaneously, define tables for generating data, set value ranges, control a wide variety of generation parameters for each field type and much more.

* [http://www.sqlmanager.net/en/products/postgresql/dbcomparer DB Comparer for PostgreSQL] - a tool for comparing PostgreSQL database schemas and discovering differences in their structures. You can view all the differences in compared database objects and execute an automatically generated script to synchronize structure of PostgreSQL databases and eliminate these differences.

* [http://www.sqlmanager.net/en/products/postgresql/extract DB Extract for PostgreSQL] - easy-to-use tool for creating PostgreSQL database backups in a form of SQL scripts. This database script utility allows you to save metadata of all PostgreSQL database objects as well as PostgreSQL table data as database snapshots.

* [http://www.sqlmanager.net/en/products/postgresql/query SQL Query for PostgreSQL] - a useful tool that lets you quickly and simply build SQL queries to PostgreSQL databases. Visual PostgreSQL query building, as well as direct editing of a query text, is available.

* [http://www.sqlmanager.net/en/products/postgresql/datacomparer Data Comparer for PostgreSQL] - tool for PostgreSQL data comparison and synchronization. Using this utility you can view all the differences in compared PostgreSQL tables and execute an automatically generated script to eliminate these differences.

=== SQL Maestro Group products for PostgreSQL ===

http://www.sqlmaestro.com/products/postgresql/

Windows

[http://www.sqlmaestro.com SQL Maestro Group] offers a number of tools for PostgreSQL.

* [http://www.sqlmaestro.com/products/postgresql/maestro/ PostgreSQL Maestro] allows you to create, edit, copy, drop and dump database objects easy and fast. You can also design your database as ER diagram, build queries visually, execute SQL queries and scripts, debug PL/pgSQL functions, view and edit data including BLOBs, represent data as diagrams, export and import data to/from most popular file formats, analyze your data summarized into multidimensional views and hierarchies (OLAP cubes), manage PostgreSQL roles, users, groups and privileges, and use a lot of other admin tools designed for making your work with PostgreSQL database server comfortable and efficient.

* [http://www.sqlmaestro.com/products/postgresql/datawizard/ PostgreSQL Data Wizard] provides you with a number of easy-to-use wizards to transfer any database to PostgreSQL, export data from PostgreSQL tables, views and queries to most popular formats, and import data from various sources into PostgreSQL tables.

* [http://www.sqlmaestro.com/products/postgresql/codefactory/ PostgreSQL Code Factory] is a GUI tool aimed at the SQL queries and scripts development.

* [http://www.sqlmaestro.com/products/postgresql/datasync/ PostgreSQL Data Sync] is a powerful and easy-to-use tool for database contents comparison and synchronization.

* [http://www.sqlmaestro.com/products/postgresql/phpgenerator/ PostgreSQL PHP Generator Professional] is a frontend that allows you to generate high-quality PHP applications for your database in a few mouse clicks.

SQL Maestro Group also produces similar tools for MySQL, Oracle, MS SQL Server, SQLite, Firebird, DB2, SQL Anywhere, and MaxDB.

=== Datanamic DataDiff for PostgreSQL ===

http://www.datanamic.com/datadiff-for-postgresql/

Windows

Datanamic DataDiff for PostgreSQL is a utility for data comparison and synchronization. Compare data for selected tables in two databases, view differences and publish changes quickly and safely. Flexible comparison and synchronization settings will enable you to set up a customized comparison key and to select tables and fields for comparison and for synchronization.
DB Data Difftective can be used for data migrations, verification of (corrupt) data, data auditing etc.

=== Datanamic SchemaDiff for PostgreSQL ===

http://www.datanamic.com/schemadiff-for-postgresql/index.html

Windows

Datanamic SchemaDiff for PostgreSQL is a tool for comparison and synchronization of database schemas. It allows you to compare and synchronize tables, views, functions, sequences (generators), stored procedures, triggers and constraints between two databases.

=== DB MultiRun PostgreSQL Edition ===

http://www.datanamic.com/multirun/index.html

Windows

DB MultiRun is a simple tool to execute multiple SQL scripts on multiple databases quickly.
Define a list of databases, add SQL scripts to execute on these databases and click "execute" to run those scripts on the databases in the list. The multi-threaded execution of the SQL scripts makes it complete the task fast. After execution of the scripts, you can examine the results of the executed scripts on each database.

=== SQLPro ===

http://www.vive.net/products/sqlpro.htm

Windows

SqlPro is an easy to use database GUI tool for six popular databases (Oracle, MySQL, PostgreSQL, SQL Server, SQLite, and Access). One IDE makes database administration and development faster and error free.
SQLPro Key Features: color-coding of the SQL, drag-and-drop of objects into the editor pane to save you from typing their names, retrieval of SQL code for things like stored procedures and triggers from the underlying database, and one-click creation of SELECT and INSERT statements. You can open, save and print SQL scripts.
SQLPro uses native drivers to connect to the databases (no ODBS or third party engines to install).

=== DB Doc ===

http://www.yohz.com/dbdoc_details.htm

Windows/Linux(Wine)

DB Doc helps you document your database structure and objects. Documents can be generated as PDF reports, HTML pages, Microsoft Word (docx) file, or a single compiled HTML file. The layout is fully customizable, and you can quickly view inter-object dependencies using hyperlinks.

DB Doc supports PostgreSQL 8.3 to 9.4.

=== SQL Blob Export ===

http://www.yohz.com/sbe_details.htm

Windows

SQL Blob Export exports unlimited images and files from your tables or queries in 5 simple steps.

=== SQL File Import ===

http://www.yohz.com/sfi_overview.htm

Windows

SQL File Import allows you to upload files, images, and other data into your database, without having to write any SQL statements. SQL File Import supports PostgreSQL, Firebird, MySQL, Oracle, SQLite, SQL Server, and various ODBC-supported databases (e.g. DB2 and PostgreSQL).

A scripting engine allows you to transform data before importing them into your database. A command line version is also included to allow you to perform unattended upload/import tasks.

=== SQL Image Viewer ===

http://www.yohz.com/siv_details.htm

Windows

SQL Image Viewer allows you to retrieve, view, convert and export images stored in Firebird, MySQL, Oracle, SQLite, SQL Server, and various ODBC-supported databases (e.g. DB2 and PostgreSQL). It supports the following image formats: BMP, GIF, JPG, PNG, PSD, and TIFF.

It also allows you to export binary data and recognises the following binary file types: PDF, MP3, WAV, 7Z, BZ2, GZ, RAR, ZIP, and has experimental support for DOC, PPT and XLS file types.

A command line version is also included to allow you to perform unattended scheduled exports of binary data.

=== SQL Multi Select ===

http://www.yohz.com/sms_details.htm

Windows

SQL Multi Select is a query tool that allows you to run multiple scripts on multiple servers with a single click. Result sets from different servers are consolidated into a single view, allowing for easy comparison and analysis.

=== SQLTool Pro Database Editor ===

http://www.sqltoolpro.com

Android

SQLTool Pro is a professional Android SQL editor for MySQL, SQL Server, PostgreSQL, Sybase, and Oracle Databases.

=== SSIS Data Flow Components for PostgreSQL ===

https://www.devart.com/ssis/

Windows

'''Devart SSIS Data Flow Components for PostgreSQL''' allow you to integrate database and cloud data via SQL Server Integration Services (SSIS).

Devart SSIS Data Flow Components provide easy to set up cost-effective data integration using SSIS ETL engine. They provide high performance data loading, convenient component editors, SQL support for cloud data sources and lots of data source specific features.

=== DbVisualizer ===

http://www.dbvis.com/

Windows/OS X/Linux/UNIX

DbVisualizer is a feature rich, intuitive multi-database tool for developers, database administrators, and increasingly for advanced analysts providing a single powerful interface across a wide variety of operating systems. With its easy-to-use and clean interface, DbVisualizer has proven to be one of the most cost effective database tools available, yet to mention that it runs on all major operating systems and supports all major RDBMS that are available. Users only need to learn and master one application. DbVisualizer integrates transparently with the operating system being used.

[[Category:Tool]]
[[Category:General articles and guides]]

=== Valentina Studio (Free) ===

http://www.valentina-db.com/valentina-studio-overview

Windows/OS X/Linux/

Valentina Studio is a powerful PostgreSQL Database Server administration and development tool. It offers for free many advanced editors:
* Schema Editor with Tree and Column views
* Diagram Editor with reverse engineering
* SQL Editor with auto-completion, syntax-highlighting, recent and favorite queries, templates of commands, many result tab-panels, ...
* Data Editor with easy sorting and filtering of records without SQL, in-cell editing.
* Related Data Editor that allow s you to learn related records in different modes.
* Import/Export
* SQL dumps
* and so on ...

Valentina Studio PRO - adds additional advanced features as:
* Report Editor to developer reports based on Valentina Report Engine with datasources from PostgreSQL and other databases.
* Diagrams forward engineering
* SQL DIFF
* Data Transfer

[[Category:Tool]]

=== JackDB ===

http://www.jackdb.com/

Html5 Web Browser (Linux/Mac OS X/Windows)

JackDB is a database client that runs entirely in your web browser. There's no software to install locally so you can use it on Mac OS X, Linux, and Windows and it works on all major modern browsers (eg. Chrome, Firefox, IE, Safari, and Opera). It supports connecting to PostgreSQL, as well as MySQL, Oracle, and SQL Server databases.

Features:
* Html5 interface with no client installation
* Query editor with syntax highlighting
* Scrolling result sets
* Schema/Object browser
* SSL connections with certificate pinning
* Eliminates password sharing
* Two-factor authentication
* BLOB display (images and Html5 audio/video)

=== Tadpole DB Hub ===

https://github.com/hangum/TadpoleForDBTools/wiki

Tadpole DB Hub is Unified infrastructure tool, a various environment based interface for managing Apache Hive, Amazon RDS, CUBRID, MariaDB, MySQL, Oracle, SQLite, MSSQL, PostgreSQL and MongoDB databases. It enables you to handle typical DB over the World Wide Web.

Features:
* Intuitive web interface (Safari, Chrome, IE 10, Firefox)
* User Management (Admin, Manager, User)
* Select, Insert, Update, Delete
* Download query result
* SQL Syntax Highlighting
* SQL Formatting
* SQL Statement <-> Java, PHP String Literal Each Convert
* SQL Assist
* Execute SQL Statement
* SQL Result Set to CSV
* SQL History And Export text
* Generate SQL Statement (Select, Insert, Update, Delete, Table, View, Index, Procedure, Function, Trigger)
* Generate ER Diagram (Auto Layout)

=== Vertabelo ===

http://www.vertabelo.com

Vertabelo is an online database designer working under Chrome. It free to use for smaller projects and have a proprietary version for larger database projects.

Features:
* Intuitive HTML5 web interface (Chrome)
* OS independent
* Sharing DB model with team members
* Support for PostgreSQL, MySQL, Oracle, MS SQL Server, DB2, SQLite, HSQLDB,
* Model versioning
* Dynamic/Visual search
* Live model validation
* Reverse engineering

=== pgModeler ===

PostgreSQL Database Modeler

http://pgmodeler.com.br

PostgreSQL Database Modeler, or simply, pgModeler is an open source tool for modeling databases that merges the classical concepts of entity-relationship diagrams with specific features that only PostgreSQL implements. The pgModeler translates the models created by the user to SQL code and apply them onto database clusters from version 8.0 to 9.1. $3.50 per copy as of 2014/04/09.

=== GenMyModel ===

https://www.genmymodel.com

GenMyModel is an online modeling tool supporting [http://www.genmymodel.com/database-diagram-online database modeling]. It is free to use for smaller projects and have a proprietary version for larger database projects.

Features:
* Intuitive HTML5 web interface (Chrome, Firefox, Safari, Internet Explorer)
* OS independent
* Instant sharing and collaboration
* Customizable SQL generators
* Model versioning
* Live model validation

=== DBHawk ===

http://www.datasparc.com/

Web Browser (Linux/Mac OS X/Windows)

DBHawk is a web based SQL tool and reporting software designed for PostgreSQL, Oracle, SQL Server and other databases. Its easy to deploy and use.

Features:
* Web based interface with no client installation
* Advanced Query editor with syntax highlighting and multi tabs results
* Online visual query builder
* Online SQL Report Builder
* Online SQL Job Scheduler
* Export results to html, csv, pdf, google docs, amazon s3
* SQL Auditing and Security
* Schema/Object browser
* SQL and data snippet sharing
* Blob data viewer and editor

=== Datazenit ===

https://datazenit.com/

Windows, Mac OS X, Linux

Datazenit is a cross-platform PostgreSQL and MySQL GUI with data grid, schema builder and interactive charts.
It also has query builder, raw query editor with auto-complete, team collaboration features like connection, query and chart sharing among team members.

=== EDB Postgres Enterprise Manager ===

http://www.enterprisedb.com/products/postgres-enterprise-manager

Windows, Mac OS X, Linux

Postgres Enterprise Manager is the only solution available today that allows you to intelligently manage, monitor, and tune large scale Postgres installations from a single GUI console.

Monitoring features include: server auto-discovery, over 225 pre-configured ready to run probes, custom probes, alert management, personalized alerts, remote monitoring, versatile charting, custom dashboards and web client.

DBA tools include: database objects management, Postgres Expert (best practice configuration settings), Audit Manager, Log Manager, Log Analysis Expert, Capacity Manager and Team Support.

Developer tools include: Query Tool, Data Grid, SQL Profiler, SQL Debugger and Import tools.

Tuning tools include: At-A-Glance performance dashboards, Tuning Wizard, Performance Diagnostics and Index Advisor.

=== ClusterControl by Severalnines ===

https://severalnines.com/product/clustercontrol/for_postgresql

ClusterControl is an all-inclusive open source database management system that allows you to deplore, monitor, manage and scale your database environments. ClusterControl provides the basic functionality you need to get PostgreSQL up-and-running using our deployment wizard, monitoring and basic management abilities like automatic failover, backups, and restores.

* Point and Click Replication Deployments - ClusterControl allows you to easily deploy and configure master/slave replication PostgreSQL instances.
* Advanced Performance Monitoring - ClusterControl monitors queries and detects anomalies with built-in alerts.
* Automated Failover Handling - ClusterControl detects master failures and automatically promotes a new master
* Database Automation - ClusterControl lets you manage configurations, schedule, and restore backups.

=== Database Tour Pro ===

https://www.databasetour.net

Database Tour Pro is a database tool with built-in report builder for Windows. It works with different types of relational databases including PostgreSQL.

Key features:

* Creating tables.
* Viewing and editing data.
* Several ways to print data.
* Built-in report engine and visual report designer with templates, expressions, preview etc.
* Expression builder for report and export expressions.
* Building and executing SQL queries. Support for execution of multi statement SQL scripts. Syntax highlighting in SQL editor. Support for parameterized SQL queries.
* Enhanced database grids, which allow to view and manipulate the data in the most convenient way, including sorting by clicking column header, changing row heights, resizing columns etc.
* Command line support for executing queries, opening tables, export-import operations, loading reports etc. with logging the performed operations.
* Searching and replacing text in database with ability to choose fields, record range etc.
* Importing data to table from another table or a query.
* Exporting data from open table or query to file(s) like text, CSV, HTML, XLSX, XML, RTF, DBF or to another relational database.
* Copying data to clipboard.
* Viewing and editing Blob data, such as large text and graphics.
* Tools for editing text fields (trimming, changing case of symbols, replacing text).
* Customized data view (font, background).
* Conditional formatting data in database grids and reports.
* Ability to control transactions.

=== Reportizer ===

https://www.reportizer.net

Reportizer is a database reporting tool, which allows easy creating, modifying, and printing database reports from different types of databases, including PostgreSQL. Reports can be edited in convenient visual report builder or in text mode. It supports calculating fields, multi-column reports, expressions, grouping, displaying images etc. Reportizer can export reports to HTML, XLSX, image, or internal format. There is an ability to load and print reports from command line. Reportizer allows to manage report collections, which can be held either in files or in database tables.

=== Exportizer Pro ===

https://www.vlsoftware.net/exportizer-pro/

Exportizer Pro is a database export tool, which can work with PostgreSQL database either as source or destination. It allows to export data to database, file, clipboard, or printer.
* Possible sources: ODBC data sources, files of DB (Paradox), DBF (dBase, FoxPro), MDB, ACCDB, XLS, XLSX, GDB, IB, FDB, HTML, UDL, DBC, TXT, CSV types, databases specified by ADO connection strings, and databases like Oracle, SQL Server, Postgresql, DB2, Informix, SQLite, Interbase etc.
* Possible destinations: file formats like text, CSV, XLS, XLSX, RTF, XML, HTML, PDF, DBF, SLK, SQL script, and relational database of any supported type.
* It is possible to export all or selected tables from an open database at once.
* Exportizer Pro can automatically detect the most known image types (JPEG, PNG, GIF, BMP, ICO) in BLOB fields and export them, for example, to HTML or XLSX.
* There is an ability to specify the source-to-target field mappings.
* Export operations can be performed either via the program interface or via command line.

=== TiCodeX SQL Schema Compare ===

https://www.ticodex.com/

TiCodeX SQL Schema Compare is a tools that allows database administrators to compare multiple database schema in order to manage versioning. 
The software runs on Windows, Linux and Mac and supports Microsoft SQL (MS-SQL), MySQL, PostgreSQL, Azure SQL and MS-SQL on Amazon RDS.

'''Key Features:'''
* Runs on Windows, Linux and MacOS
* Localized in English, German and Italian
* Compare changes between two SQL Database schemas (as example from development to test to production)
* View database differences and explore schema changes to see what's going on
* Automatically create full database migration scripts
* Securely save database and server login details

=== pgMustard ===

https://www.pgmustard.com/

pgMustard is a performance tool for PostgreSQL that provides a user interface for your EXPLAIN ANALYSE output, as well as tips on what to do to speed up your query.

Features:
* Quickly see the slowest operations
* Code snippets to tie operations back to the query
* Tips to speed up your query💡
* Does the arithmetic for you (including wall clock times)
* Explanations of operation types and key concepts
* Links to relevant documentation and blog posts

Requirements:
* JSON format plans
* Any supported version of PostgreSQL
* English language only
* Web application, no installation required

== No longer Supported/Developed ==

* OpenOffice postgresql SDBC Driver. no work on the project since 2010; last version was a beta. http://www.openoffice.org/dba/drivers/postgresql/index.html
* RedHat: hasn't been refreshed since Pg 8.4. http://sources.redhat.com/rhdb

Community Guide to PostgreSQL GUI Tools

2019-04-10T00:54:17Z

Dfetter:

{{Languages}}

== Alternate Guides ==

Another detailed summary from 2009 is available at
[http://www.postgresonline.com/journal/index.php?/archives/133-Database-Administration,-Reporting,-and-Light-application-development.html Database Administration, Reporting, and Light application development]

== Open Source / Free Software ==

=== pgAdmin 4 ===

http://www.pgadmin.org/

MS Windows, GNU/Linux, FreeBSD, Mac OS X, OpenBSD, Solaris

Admin

pgAdmin III is an Open Source management tool for PostgreSQL databases. Features full Unicode support, fast, multithreaded query and data editing tools and support for all PostgreSQL object types.

pgAdmin III is bundled with the Windows installer, and you can use that such a client to administer a remote server on another OS. Note that binary packages for platforms like RPM don't show up in every point release, you currently have to go back to v1.8.0 to get the last full set of packages.

Free Administration Centre for the PostgreSQL database. Includes a graphical administration interface, an SQL query tool, a procedural code editor and much more. pgAdmin III is designed to answer the needs of most users, from writing simple SQL queries to developing complex databases. The graphical interface supports all PostgreSQL features and makes administration easy. Available in more than 30 languages and for several operating systems.

=== phpPgAdmin ===

http://sourceforge.net/projects/phppgadmin

browser-based, requires webserver

Admin

Similar to the ever-popular phpMyAdmin, enhanced for PostgreSQL, supports browsing and modification of most types of PostgreSQL database objects, plus execution of ad-hoc queries. Maintained by (who else?) the phpPgAdmin team. (JMB 11.2002).

phpPgAdmin (and the required Apache and PHP packages) may be easily installed using Stack Builder if you are running a one-click-installer PostgreSQL distribution.

=== SQuirrel ===

http://squirrel-sql.sourceforge.net/

Platforms that support Java

Admin

SQuirreL SQL Client is a graphical Java program that will allow you to view the structure of a JDBC compliant database, browse the data in tables, issue SQL commands etc. The minimum version of Java supported is 1.8.x as of SQuirreL version 3.8.1.

=== Adminer ===

http://www.adminer.org

browser-based, requires webserver

Adminer (formerly phpMinAdmin) is a full-featured database management tool written in PHP. Conversely to phpMyAdmin, it consist of a single file ready to deploy to the target server. Adminer is available for MySQL, PostgreSQL, SQLite, MS SQL and Oracle.

=== Libre Office ===

http://www.libreoffice.org/download/3-5-new-features-and-fixes/

New native driver for PostgreSQL databases (for versions > 8.4 - support for version 8.4 will be included in LibreOffice 3.5.1).

=== GNOME-DB ===

http://www.gnome-db.org

Linux, Unix

Admin

Database administration/user tool for GNOME, based on libgda/libgnomedb, which are a complete database-independent access layer for UNIX systems, with support for PostgreSQL, MySQL, Sybase, MS SQL Server, Oracle, Interbase/Firebird, MS Access files, xBase.

=== TOra, an Oracle tool with some PostgreSQL support ===

http://tora.sf.net/

Linux & Windows

Admin

An Oracle database administration interface, with limited ability to browse PostgreSQL databases (tables, views, and functions only). I'm told that if you have the Oracle libraries, Tora's sophisticated function editor will work for PostgreSQL as well. Developed by Henrik Johnson as a Quest Toad clone. (JMB 11.2002)

=== Kexi ===

http://www.kexi-project.org/

Kexi is part of the Calligra Suite and is released under the GNU General Public License (GPL) and LGPL.

available for
FreeBSD & Linux, Apple, Windows, (Android)

=== SQL Workbench/J ===

http://www.sql-workbench.net

Java (multi-platform)

An OpenSource SQL GUI tool similar to Squirrel. Data can be edited directly in the result set. It has strong support for exporting and importing data between databases using its own SQL command extension. It can be used in GUI mode or as a console application. All SQL Workbench specific commands can also be run in batch mode to automate export and import task. It supports schema comparison ("diff") and copying data between databases.

=== Druid III ===

http://druid.sourceforge.net/

Java (multi-platform)

The druid is a tools that allows users to create databases in a graphical way. The user can add tables, fields, folders to group tables and can modify most of the database options that follow the SQL-92 standard. In addition to sql options, the user can document each table and each field with HTML information. Once the database is created, the druid can generate:

* HTML documentation: for all tables, with browsing facilities
* PDF documentation: for all tables
* Java classes: (one class for each table) that contain tables' constants (such as fields size) plus java code added by the user
* A data dictionarythat contains all tables and fields present in the database
* SQL script which contains all table definitions that can be piped to the DBMS
* And much more info...

=== Power*Architect ===

http://www.sqlpower.ca/page/architect

Java (multi-platform)

Power*Architect is an ERD modelling tool that is based on Java and JDBC. Support for forward and reverse engineering PostgreSQL databases is supported. It's OpenSource with a GPL license.

=== RISE PostgreSQL code generator ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1889

Windows

The RISE PostgreSQL code generator generates native PL/pgSQL scripts. Model your information in the free RISE Editor and generate your database script. The script incrementally updates the tables, columns, indexes and constraints in the database to match the RISE model. Once the database model is updated, the views defined in the RISE model are created in the database and possible default data, entered in the model, is inserted.

=== Open Source CMS ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=2017

Windows

The CMS is a free Visual Studio 2010 solution template with a set of projects providing a complete Content Management System (CMS) based on RISE Visual Modeling with model, full source, sample site and DB-scripts for PostgreSQL, MySQL and SQL Server.

It’s a complete ready-to-run Visual Studio solution with model, source code and web clients. It illustrates how to use RISE, how to implement a SOA backend and how to build RIA frontends.

=== DBeaver ===

http://dbeaver.jkiss.org/

Eclipse/Java (multi-platform)

Eclipse-based environment, supporting many SQL databases from different vendors, as well as few NoSQL ones (Cassandra, etc).
Good query editor with syntax highlighting, completion and autosave.
Editing of query results. SSH tunneling support. Tons of other cool features.
Quite good, but not 100% perfect PostgreSQL support (yet?). Regularly updated, as of 2018.

=== OmniDB ===

https://github.com/OmniDB/OmniDB

Linux, Windows and macOS

Open source full-featured tool for database management. Currently supports PostgreSQL (9.3 - 11), Oracle (11g - 18c), MySQL (5.6 - 8.0) and MariaDB (10.1 - 10.3). More RDBMS support coming soon, including the ability of converting databases from any supported RDBMS to PostgreSQL and back.

=== Postbird ===

https://github.com/paxa/postbird

MacOs

Open source, desktop application to manage your local or remote PostgreSQL databases.

=== Sohag Developer ===
[http://sohag-developer.com/ Sohag Developer]

Gnu/Linux Windows (Other OS can compile from source code).

Build a powerful database applications following few steps using Sohag Developer .
Sohag Developer currently supports PostgreSQL database and has a set of generators that generates (Qt/C++ code and ui forms - PHP web applications uses web forms and bootstrap framework ) to manipulate the data in the database tables or views.

=== PASH-Viewer: PostgreSQL Active Session History Viewer ===
https://github.com/dbacvetkov/PASH-Viewer

Java (multi-platform).

Open-source software which provides graphical view of active session history and help you to answer questions like "What wait events were taking most time?", "Which sessions were taking most time?", "Which queries were taking most time and what were they doing?". It also supports Active Session History extension by pgsentinel.

=== pgrights: GUI for PostgreSQL roles, privileges and policies ===
https://github.com/apsavin/pgrights

MacOS (based on Electron, so versions for other OS can be build from source code).

Open-source software which allows you to easely understand what can do (and what can't) a PostgreSQL user with a table's data. In other words, it's a viewer of results of GRANT commands and row-level security rules applied for a particular table and for a particular role.

== Proprietary ==

=== SQLGate ===

https://www.sqlgate.com/product/download

Windows

SQLGate is a simple but powerful IDE for multiple Database including PostgreSQL.

* Powerful Data Grid and ERD

* Multiple SQL Execution

* Auto-Complete

* Intuitive UI/UX

* Multiple Themes

* Fast processing speed

Use SQLGate to maximize your productivity!

=== dbForge Studio for PostgreSQL ===

https://www.devart.com/dbforge/postgresql/studio/

PostgreSQL GUI tool for managing and developing databases and objects. The IDE for PostgreSQL allows users to create, develop, and execute queries, edit and adjust the code to your requirements in a convenient and user-friendly interface. It comes in two editions - Standard and Express (free).

Key features:
* SQL Development
* Database Explorer
* Data Editor
* Data Export and Import
* Pivot Table
* Master-Detail Browser
* Data Reports

=== PSequel ===

http://www.psequel.com/

OS X Yosemite only, free, "Sequel Pro" inspired.

=== EMS SQL Manager for PostgreSQL Freeware ===

http://www.sqlmanager.net/en/tools/free

Windows

EMS SQL Manager for PostgreSQL Freeware (EMS SQL Manager Lite for PostgreSQL) is an excellent and easy-to-use freeware graphical tool for PostgreSQL database administration. It has the minimal required set of tools for those users who are new to PostgreSQL server and need only its basic functionality.
EMS SQL Manager for PostgreSQL Freeware allows you to work with servers, databases and schemas, view, edit, search, group, sort and filter any data stored in a database, create and execute SQL queries with powerful SQL editor, handle multiple selected objects at a time and much more.

=== Marshal SQL Utility ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1756

Windows

The Marshal SQL Utility is a generic cross database utility with batch execution capabilities. It allows you to test ODBC connections, browse database schemas, discover tables, views and columns.

Key features of Marshal SQL Utility:

* Execute any query supported by your database server
* Execute batches of queries
* Discover tables and views in your database
* Discover columns for a selected table or view
* Supports BLOBS and CLOBS
* Save your results to file
* Use any ODBC compliant database such as PostgreSQL.

=== RISE PHP for PostgreSQL code generator ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1888

Windows

The RISE PHP for PostgreSQL code generator renders PHP source code for database access. Model your information and programming interfaces in the free RISE Editor and generate your code. The generated code implements the classes and methods corresponding to the information interfaces specified in the RISE model. This includes classes for database access and, optionally, classes implementing SOAP/JSON web services and proxy classes assisting the implementation of a PHP SOAP client.

=== RISE - Model Driven Development using ERD / UML ===

http://www.risetobloome.com

Windows

RISE is a free software suite for model driven information system development. Use a single source RISE model to generate your entire information solution including database, web services and documentation. Boost development throughput and improve quality and maintainability!

The RISE user experience is based on a project concept, similar to that of most integrated development environments. The user works with resources and drawings that are part of a single development project.

RISE supports a fully graphical approach to information modeling and system engineering, using ERD (Entity Relationship Diagram) as well as UML (Unified Modeling Language). This includes drag-and-drop of entities, their attributes and relations, as well as of views and entire web services.

RISE supports graphic editing of complex objects such as views and orchestrated methods. RISE automatically safeguards the combination process, thus, assuring a technically correct result.

RISE provides several ways to generate code from the model; directly to file, via the RISE Server or as an Internet service. RISE provides code generators for the database layer (SQL/DDL) as well as for the server side application layer (web services and persistent classes). All database scripts are incremental allowing you to install and maintain any number of databases from a single model.

Feature list
http://www.risetobloome.com/Page_1_S.aspx?ITEM=1355

=== WaveMaker Ajax GUI Design Tool ===

http://www.wavemaker.com/

Windows, Macintosh, Linux

WaveMaker is an Ajax-based GUI design tool for Postgres. WaveMaker is built using itself! WaveMaker generates a standard Java WAR file based on Spring, Hibernate and Dojo. WaveMaker supports Postgres schema creation and import and includes a visual query editor.

=== AnySQL Maestro ===

http://www.sqlmaestro.com/products/anysql/maestro/

Windows

AnySQL Maestro is a freeware tool for administering any database engine (PostgreSQL, SQL Server, Oracle, MySQL, MS Access, etc.), which is accessible via ODBC driver or OLE DB provider. Includes Database Designer, Visual Query Builder, BLOB Viewer/Editor, SQL Editor, Data export/import and other features.

=== TeamPostgreSQL ===

http://www.teampostgresql.com

browser-based, webserver included

AJAX/JavaScript-powered web interface for PostgreSQL administration. Browse, maintain and create data and database objects from anywhere, in the web browser. Supports SSH for both the web interface and the database connections. Rich interface with tabbed SQL editor with auto-completion, inline row-editing widgets, click-through foreign key navigation between rows and tables, 'favorites' management for commonly used scripts, and more.

Installers available for Windows, Mac and Linux, alternatively download a simple cross-platform archive that runs anywhere with simple script.

=== Postgres Compare ===

[[File:Postgres_compare.png|thumb|left|frameless]]

https://www.postgrescompare.com/

Windows, Mac & Linux

A comprehensive tool for identifying the differences between databases and generating an update script to synchronize them. Postgres Compare reads the system catalogs to determine the structure of the database and compares it to another to find the changes. Generate SQL and deploy the alterations, save snapshots for later. Automate the process via the command line.

Alpha build available now https://www.postgrescompare.com/downloads

<div style="clear:both;"></div>

=== JetBrains IDEs - DataGrip, IntelliJ IDEA, PHPStorm, PyCharm, RubyMine, etc ... ===

http://www.jetbrains.com/

Windows, Mac OS X, Linux

JetBrains has a dedicated SQL IDE — DataGrip which can connect to PostgreSQL as well. It provides code completion, multi cursors, local query history, navigation, refactorings and language injection support.
https://www.jetbrains.com/datagrip/

Other JetBrains Products, for example, PHPStorm, have built-in database plugin, and it has the same functionality as DataGrip.

After you configured the data sources of your project, you can easily create tables, foreign keys, indexes much easier than usual, because the IDE is very smart; for example by foreign keys it automatically sets the name of the key and the related columns. For me, it is so far the best experience by creating a basic database schema. Even with editable EER models was it slower...
By the settings of [http://goo.gl/TuqiPRpantun romantis terbaru] your data source you can configure the SQL dialect of your database. After that, if you want to add stored procedures or triggers, you will have code completion which is favorable too. So I think JetBrains products speed up your work if you exactly know what you want, and how can you make it.

For any JetBrains IDE, there is a free license for open source projects. For enterprise usage there is a 30 days trial, after that, you can buy a personal or proprietary license which is very cheap compared to other products.

For PyCharm (even the Community Edition) you can install the free third-party plugin [http://confluence.jetbrains.com/display/CONTEST/Database+Navigator Database Navigator] (Settings -> IDE Settings -> Plugins). It appears to deliver the same functionality described above for PHPStorm. You will get a new menu DB Navigator, left to the Help menu.

=== TablePlus ===

https://tableplus.io/

macOS

A modern, native tool with an elegant UI that allows you to simultaneously manage multiple databases, including PostgreSQL.

* True native built.

* Workspace supports multiple tabs, multiple windows

* Powerful SQL editor with full features: auto syntax highlight, auto-suggestion, split pane, favorite and history.

* Data Filter & Sorting, import & export

* Full-dark theme & modern shortcut

With plugin system, you can be able to write your own new features to work with database per your needs (export charts, pretty json…).

=== SQLPro for Postgres ===

http://www.hankinsoft.com/SQLProPostgres

Mac OS X 10.8 and above

Features:
* 100% native OS X app with a clean and simple to use interface.
* Query editor with syntax highlighting and autocomplete.
* Support for multiple result set execution.
* History feature, displaying your last ten executed queries.
* Primary key detection for inline result set modifications.
* Custom theme support allowing developers to work with style.

=== Postico ===

https://eggerapps.at/postico/

Mac OS X

Postico is a fully native Mac app for connecting to your PostgreSQL server. It supports encrypted connections via SSL and SSH to PostgreSQL 8.0 and later, including Amazon Redshift.

Postico has a powerful table content editor with in-cell editing and form-based row editing in a sidebar. You can quickly filter tables by keywords or even complex SQL expressions.

There's also a table structure editor for editing columns, types, default values, foreign keys, check constraints etc.

Finally, there's a convenient SQL Query Editor with support for query history and syntax highlighting. It also has convenience features like auto-indent and shortcuts for comment line etc.

=== SEQUEL for PostgreSQL ===

http://www.sequel.tech

macOS

SEQUEL for PostgreSQL is a professional DB administration and management tool, with extremely intuitive and feature-rich GUI that makes it the best assistant tool for developers and admins. SEQUEL is lightweight, fast and powerful that it can significantly simplify the DB management process. For those who cannot live without a CLI, SEQUEL offers a powerful Query Editor with syntax highlight, autocomplete and a Console log view that is always visible, so you can monitor the communication with your databases. It includes:

* Database management forms for Schema, Table, Index, Foreign key, Trigger, Rule, Sequence, Collation, Domain, Enum type, Tablespace and Language objects with full parameters support
* Assistant info views for Object information, Actions, Help, and Documentation
* Jump bar for quick objects selection and navigation
* Taskbar with multi-task monitoring support
* Console log view
* Syntax highlight, autocomplete, current and selection query execution and explain, line numbering and working statement detection
* Direct editing in the results view, query results explanation
* Powerful Field editor
* Transaction based database updates
* Code preview and Content editing

=== dbForge Data Compare for PostgreSQL ===

http://www.devart.com/dbforge/postgresql/datacompare/

Microsoft Windows 2000/XP/2003/Vista and Windows 7, 8, 10

'''dbForge Data Compare for PostgreSQL''' by '''Devart''' is a tool for table data comparison and synchronization. When using PostgreSQL data compare tool developer can detect data differences in compared PostgreSQL tables; generate data synchronization script and execute it to eliminate all these differences.

'''Key features:'''

* Identify the differences between two databases
* Compare separate tables or table groups by table name mask
* Compare tables with different structure
* Generate a report embodying data diff and save it for further analysis
* Sync data in tables and views in full or in part
* Generate SQL script for database synchronization
* Organize database synchronization according to the schedule

=== Full Convert ===

https://www.spectralcore.com/fullconvert

Database conversion and synchronization between PostgreSQL and Microsoft Access, dBase, FoxPro, Microsoft Excel, Firebird, Interbase, MySQL, Oracle, Paradox, Microsoft SQL Server, SQL Server, SQL Server Azure, SQL Server Compact(SQLCE), SQLite, Delimited text files (CSV), XML and many more via ODBC.

=== Replicator Pro ===

https://www.spectralcore.com/replicator

Replicator allows table data comparison and sync - even with heterogeneous databases. It is unique in the fact it can replicate changes only even if source is non-relational (CSV, DBF, Excel documents, Paradox...). Replicator has a built-in scheduler for easy periodic change replication.

=== Nucleon Database Master for PostgreSQL and Others ===

Nucleon Database Master is a modern, powerful, intuitive, easy to use and all in one PostgreSQL MongoDB, Oracle, DB2, Informix, Ingres, SQL Server, SQL Azure, MySQL, FireBird, SQLite client application with a consistent interface that simplifies managing, querying, editing, visualizing, designing and [http://mitraharga.blogspot.co.uk/2014/09/harga-tablet-pc-axioo.htmlharga tablet axioo] reporting relational and schema-free (NoSQL) database systems. You can connect any database system via ODBC and OleDB connections.Using Database Master, you can execute SQL, LINQ, JSON queries or you can create, edit and delete all database objects such as tables, views, procedures, columns, indexes, collections, and triggers. You can execute SQL queries and scripts, view and edit table data including BLOBs (Image, Text or any file), represent tables and its relations as an ER(Entity Relationship) diagram.

Info:
http://www.nucleonsoftware.com/
Windows, other platforms via WINE
Admin

=== DBTools Manager ===

http://www.dbtools.com.br

Windows

Admin

Freeware, available for PostgreSQL and MySQL, allows managing all aspects of the database: db, table, triggers, functions, etc. Includes import/export wizards to migrate data and structure to/from other database engines. Developed by DBTools Software.

=== PgManager ===

http://www.ems-hitech.com/pgmanager

Windows, Linux version just released

Admin

Basically a proprietary, more powerful version of PGAdmin II or PGAccess. Adds support for trigger and constraint editing, metadata logging, and query monitoring. Also includes multiple-format data import/export tools, which are also available on their own for Linux. Developed by EMS Hitech. (JMB 4.2003).

=== DeZign for Databases ===

http://www.datanamic.com

Windows

ERD

DeZign is a database development tool using an entity relationship diagram. It visually supports the layout of the entities and relations and automatically generates SQL schemas for most leading databases including PostgreSQL.

=== Case Studio 2 / Toad Data Modeler ===

http://www.casestudio.com/enu/index.aspx

Windows

ERD

Commenter 1: I just downloaded the trial version, so far it looks really promising and claims to support PostgreSQL. Handles reverse engineering of existing databases, and has a really nice interface for setting up tables, relationships etc. You can get a lite or full version. The description from the website... Professional database modeling tool for various databases. CASE Studio 2 includes following key features:

LITE version features + Reverse Engineering from various database systems Version Manager Data Flow Diagrams Definition of user-defined variables Large COM interface Users, User groups and User permission support and many more.

Case Studio was acquired, and renamed 'Toad Data Modeler'.

Commenter 2: I've used the licensed version before and after the name change. PostgreSQL support is excellent.

=== PostgreSQL PHP Generator ===

http://www.sqlmaestro.com/products/postgresql/phpgenerator/

Windows

PostgreSQL PHP Generator is a freeware but powerful PostgreSQL GUI frontend that allows you to generate high-quality PHP scripts for the selected tables, views and queries for the further working with these objects through the web.

=== pgEdit ===

http://pgedit.com

Macintosh
pgEdit is a high-performance SQL editor and development environment designed specifically for PostgreSQL relational databases. pgEdit features include SQL syntax coloring, direct source code execution, PHP support, integrated documentation, and extensive customizable editing facilities.

pgEdit uses psql, the interactive terminal application included with every PostgreSQL installation. This makes it easy to develop with pgEdit and then transfer your work to any PostgreSQL installation for maintenance and production tasks.

pgEdit is a native application for both Macintosh and Windows. It does not use Java or require installation of external libraries. You have the option of using the version of psql included with pgEdit or a different version installed anywhere on your hard drive.

=== RazorSQL ===

http://www.razorsql.com/

Macintosh/Windows/Linux/Solaris

RazorSQL is an SQL query tool, database browser, SQL editor, and database administration tool that supports PostgreSQL and any other JDBC or ODBC compliant database. Some of the major features are tools for creating, dropping, and altering objects such as tables, views, indexes, triggers, functions, users, and databases; a programming editor that supports 20 different programming languages; import and export tools; auto column and table lookup; and a query builder, query scheduler, and SQL formatter.

=== MicroOLAP Database Designer ===

http://www.microolap.com/products/database/postgresql-designer/

Windows ODBC

Database Designer for PostgreSQL is an easy CASE tool with an intuitive graphical interface allowing you to build a clear and effective database structure visually, see the complete picture (diagram) representing all the tables, references between them, views, stored procedures and other objects. Then you can easily generate a physical database on a server, modify it according to any changes you made to the diagram using fast ALTER statements.

=== Import / Export and synchronization tools for PostgreSQL ===

http://convertdb.com/postgresql

Microsoft Windows 8 / 7 / Vista / XP / 2000 / NT.
The software is able to connect to remote PostgreSQL 9.x/7.4 located on Linux, Solaris, Mac OS X, and Windows.

ConvertDB cross-database migration tools assist in data conversion and synchronization among PostgreSQL, MySQL, MS SQL Server, MS Windows SQL Azure, and MS Access databases

* 1 Million of records can be transferred in 5-10 minutes.
* Bi-directional synchronization between PostgreSQL, MS SQL, MySQL and Oracle
* Scheduling migration and synchronization jobs.

=== dbForge Studio for PostgreSQL ===

https://www.devart.com/dbforge/postgresql/studio/

Microsoft Windows 7, 8, 10

'''dbForge Studio for PostgreSQL''' is a brand new tool for PostgreSQL databases development, management, and editing process enjoyable and easy by Devart. The PostgreSQL IDE allows users to create, develop, and execute queries, edit and adjust the code to the requirements in a convenient and UI. The tool provides the PostgreSQL data editor functionality for queries customization and property window for the viewing all the required information of PostgreSQL database objects.

'''Key features:'''

* Code Completion helps to improve code quality when creating and editing queries with List Members, Parameter Info, Quick Info, Complete Word.
* Object Explorer for easy navigation through the object tree. You can retrieve data from the database on a single SQL document, truncate a table, select Properties to view some information on the object.
* Data Editor for management settings of tables, such as adjust column width, set either paginal or auto-search mode by default. Color and format rows and cells using a rich set of fonts and size. The tool has predefined data type formats to meet your own needs.

=== dotConnect for PostgreSQL ===

https://www.devart.com/dotconnect/postgresql/

Windows

'''dotConnect for PostgreSQL''', formerly known as PostgreSQLDirect .NET, is an enhanced ORM enabled data provider for PostgreSQL that builds on ADO.NET technology to present a complete solution for developing PostgreSQL-based database applications. It introduces new approaches for designing application architecture, boosts productivity, and leverages database applications.

'''Key features:'''

* Direct Mode
* Database Application Development Extension
* PostgreSQL Advanced Features Support
* Optimized Code
* ORM Support
* BIS Support

=== PostgreSQL Data Access Components ===

Windows

https://www.devart.com/pgdac/

PostgreSQL Data Access Components (PgDAC) is a library of components that provides native connectivity to PostgreSQL from Delphi, C++Builder, Lazarus (and Free Pascal) on Windows, Mac OS X, iOS, Android, Linux, and FreeBSD for both 32-bit and 64-bit platforms. PgDAC is designed to help programmers develop really lightweight, faster and cleaner PostgreSQL database applications without deploying any additional libraries.

Native Connectivity to PostgreSQL
PgDAC is a complete replacement for standard PostgreSQL connectivity solutions and presents an efficient alternative to the Borland Database Engine (BDE) and standard dbExpress driver for access to PostgreSQL. It provides direct access to PostgreSQL without PostgreSQL Client.

=== ODBC Driver for PostgreSQL ===

https://www.devart.com/odbc/postgresql/

Windows

Devart ODBC Driver for PostgreSQL provides high-performance and feature-rich connectivity solution for ODBC-based applications to access PostgreSQL databases from Windows, both 32-bit and 64-bit. Full support for standard ODBC API functions and data types implemented in our driver makes the interaction of your database applications with PostgreSQL fast, easy and extremely handy.

=== Excel Add-in for PostgreSQL ===

https://www.devart.com/excel-addins/postgresql.html

Windows

Devart Excel Add-in for PostgreSQL allows you to quickly and easily connect Microsoft Excel to PostgreSQL, load data from PostgreSQL to Excel, instantly refresh data in an Excel workbook from the database, edit these data, and save them back to PostgreSQL. It enables you to work with PostgreSQL data like with usual Excel worksheets, easily perform data cleansing and de-duplication, and apply all the Excel's powerful data processing and analysis capabilities to these data.

=== EMS Database Management Tools for PostgreSQL ===

http://www.sqlmanager.net/en/products/postgresql

Windows

PostgreSQL Tools Products Family:

* [http://www.sqlmanager.net/en/products/studio/postgresql SQL Management Studio for PostgreSQL] - a single workbench for administering PostgreSQL databases, managing database schema and objects as well as for database design, migration, extraction, query building, data import, export, and database comparison.

* [http://www.sqlmanager.net/en/products/postgresql/manager SQL Manager for PostgreSQL] - high performance graphical tool for PostgreSQL database administration and development. It makes creating and editing PostgreSQL database objects easy and fast, and allows you to run SQL scripts, visually design databases, build SQL queries, extract, print and search metadata, import and export PostgreSQL database data and much more.

* [http://www.sqlmanager.net/en/products/postgresql/dataexport Data Export for PostgreSQL] - tool to export PostgreSQL database data quickly to any of 19 available formats, including MS Access, MS Excel, MS Word, RTF, HTML, TXT, ODF and more. Data Export for PostgreSQL has a [http://aurora-ndut.blogspot.fr/2013/10/kata-kata-lucu.htmlkata kata lucu] friendly wizard, which allows you to set various options of PostgreSQL export process visually and a command-line utility to automate your PostgreSQL export jobs using the configuration file.

* [http://www.sqlmanager.net/en/products/postgresql/dataimport Data Import for PostgreSQL] - tool to import data to PostgreSQL tables from MS Excel 97-2007, MS Access, DBF, TXT, CSV, MS Word 2007, RTF, ODF and HTML files. This utility allows you to quickly import data to one or several PostgreSQL tables or views at once, save all PostgreSQL import parameters set on current wizard session, use special batch insert mode to import PostgreSQL data at the maximum possible speed and much more.

* [http://www.sqlmanager.net/en/products/postgresql/datapump Data Pump for PostgreSQL] - migration tool for converting databases and importing table data from an ADO-compatible source (e.g. MS Access, MS SQL database or any other database with ADO support) to PostgreSQL databases.

* [http://www.sqlmanager.net/en/products/postgresql/datagenerator Data Generator for PostgreSQL] - tool for generating test data to PostgreSQL database tables. The utility can help you to simulate the database production environment and allows you to populate several PostgreSQL database tables with test data simultaneously, define tables for generating data, set value ranges, control a wide variety of generation parameters for each field type and much more.

* [http://www.sqlmanager.net/en/products/postgresql/dbcomparer DB Comparer for PostgreSQL] - a tool for comparing PostgreSQL database schemas and discovering differences in their structures. You can view all the differences in compared database objects and execute an automatically generated script to synchronize structure of PostgreSQL databases and eliminate these differences.

* [http://www.sqlmanager.net/en/products/postgresql/extract DB Extract for PostgreSQL] - easy-to-use tool for creating PostgreSQL database backups in a form of SQL scripts. This database script utility allows you to save metadata of all PostgreSQL database objects as well as PostgreSQL table data as database snapshots.

* [http://www.sqlmanager.net/en/products/postgresql/query SQL Query for PostgreSQL] - a useful tool that lets you quickly and simply build SQL queries to PostgreSQL databases. Visual PostgreSQL query building, as well as direct editing of a query text, is available.

* [http://www.sqlmanager.net/en/products/postgresql/datacomparer Data Comparer for PostgreSQL] - tool for PostgreSQL data comparison and synchronization. Using this utility you can view all the differences in compared PostgreSQL tables and execute an automatically generated script to eliminate these differences.

=== SQL Maestro Group products for PostgreSQL ===

http://www.sqlmaestro.com/products/postgresql/

Windows

[http://www.sqlmaestro.com SQL Maestro Group] offers a number of tools for PostgreSQL.

* [http://www.sqlmaestro.com/products/postgresql/maestro/ PostgreSQL Maestro] allows you to create, edit, copy, drop and dump database objects easy and fast. You can also design your database as ER diagram, build queries visually, execute SQL queries and scripts, debug PL/pgSQL functions, view and edit data including BLOBs, represent data as diagrams, export and import data to/from most popular file formats, analyze your data summarized into multidimensional views and hierarchies (OLAP cubes), manage PostgreSQL roles, users, groups and privileges, and use a lot of other admin tools designed for making your work with PostgreSQL database server comfortable and efficient.

* [http://www.sqlmaestro.com/products/postgresql/datawizard/ PostgreSQL Data Wizard] provides you with a number of easy-to-use wizards to transfer any database to PostgreSQL, export data from PostgreSQL tables, views and queries to most popular formats, and import data from various sources into PostgreSQL tables.

* [http://www.sqlmaestro.com/products/postgresql/codefactory/ PostgreSQL Code Factory] is a GUI tool aimed at the SQL queries and scripts development.

* [http://www.sqlmaestro.com/products/postgresql/datasync/ PostgreSQL Data Sync] is a powerful and easy-to-use tool for database contents comparison and synchronization.

* [http://www.sqlmaestro.com/products/postgresql/phpgenerator/ PostgreSQL PHP Generator Professional] is a frontend that allows you to generate high-quality PHP applications for your database in a few mouse clicks.

SQL Maestro Group also produces similar tools for MySQL, Oracle, MS SQL Server, SQLite, Firebird, DB2, SQL Anywhere, and MaxDB.

=== Datanamic DataDiff for PostgreSQL ===

http://www.datanamic.com/datadiff-for-postgresql/

Windows

Datanamic DataDiff for PostgreSQL is a utility for data comparison and synchronization. Compare data for selected tables in two databases, view differences and publish changes quickly and safely. Flexible comparison and synchronization settings will enable you to set up a customized comparison key and to select tables and fields for comparison and for synchronization.
DB Data Difftective can be used for data migrations, verification of (corrupt) data, data auditing etc.

=== Datanamic SchemaDiff for PostgreSQL ===

http://www.datanamic.com/schemadiff-for-postgresql/index.html

Windows

Datanamic SchemaDiff for PostgreSQL is a tool for comparison and synchronization of database schemas. It allows you to compare and synchronize tables, views, functions, sequences (generators), stored procedures, triggers and constraints between two databases.

=== DB MultiRun PostgreSQL Edition ===

http://www.datanamic.com/multirun/index.html

Windows

DB MultiRun is a simple tool to execute multiple SQL scripts on multiple databases quickly.
Define a list of databases, add SQL scripts to execute on these databases and click "execute" to run those scripts on the databases in the list. The multi-threaded execution of the SQL scripts makes it complete the task fast. After execution of the scripts, you can examine the results of the executed scripts on each database.

=== SQLPro ===

http://www.vive.net/products/sqlpro.htm

Windows

SqlPro is an easy to use database GUI tool for six popular databases (Oracle, MySQL, PostgreSQL, SQL Server, SQLite, and Access). One IDE makes database administration and development faster and error free.
SQLPro Key Features: color-coding of the SQL, drag-and-drop of objects into the editor pane to save you from typing their names, retrieval of SQL code for things like stored procedures and triggers from the underlying database, and one-click creation of SELECT and INSERT statements. You can open, save and print SQL scripts.
SQLPro uses native drivers to connect to the databases (no ODBS or third party engines to install).

=== DB Doc ===

http://www.yohz.com/dbdoc_details.htm

Windows/Linux(Wine)

DB Doc helps you document your database structure and objects. Documents can be generated as PDF reports, HTML pages, Microsoft Word (docx) file, or a single compiled HTML file. The layout is fully customizable, and you can quickly view inter-object dependencies using hyperlinks.

DB Doc supports PostgreSQL 8.3 to 9.4.

=== SQL Blob Export ===

http://www.yohz.com/sbe_details.htm

Windows

SQL Blob Export exports unlimited images and files from your tables or queries in 5 simple steps.

=== SQL File Import ===

http://www.yohz.com/sfi_overview.htm

Windows

SQL File Import allows you to upload files, images, and other data into your database, without having to write any SQL statements. SQL File Import supports PostgreSQL, Firebird, MySQL, Oracle, SQLite, SQL Server, and various ODBC-supported databases (e.g. DB2 and PostgreSQL).

A scripting engine allows you to transform data before importing them into your database. A command line version is also included to allow you to perform unattended upload/import tasks.

=== SQL Image Viewer ===

http://www.yohz.com/siv_details.htm

Windows

SQL Image Viewer allows you to retrieve, view, convert and export images stored in Firebird, MySQL, Oracle, SQLite, SQL Server, and various ODBC-supported databases (e.g. DB2 and PostgreSQL). It supports the following image formats: BMP, GIF, JPG, PNG, PSD, and TIFF.

It also allows you to export binary data and recognises the following binary file types: PDF, MP3, WAV, 7Z, BZ2, GZ, RAR, ZIP, and has experimental support for DOC, PPT and XLS file types.

A command line version is also included to allow you to perform unattended scheduled exports of binary data.

=== SQL Multi Select ===

http://www.yohz.com/sms_details.htm

Windows

SQL Multi Select is a query tool that allows you to run multiple scripts on multiple servers with a single click. Result sets from different servers are consolidated into a single view, allowing for easy comparison and analysis.

=== SQLTool Pro Database Editor ===

http://www.sqltoolpro.com

Android

SQLTool Pro is a professional Android SQL editor for MySQL, SQL Server, PostgreSQL, Sybase, and Oracle Databases.

=== SSIS Data Flow Components for PostgreSQL ===

https://www.devart.com/ssis/

Windows

'''Devart SSIS Data Flow Components for PostgreSQL''' allow you to integrate database and cloud data via SQL Server Integration Services (SSIS).

Devart SSIS Data Flow Components provide easy to set up cost-effective data integration using SSIS ETL engine. They provide high performance data loading, convenient component editors, SQL support for cloud data sources and lots of data source specific features.

=== DbVisualizer ===

http://www.dbvis.com/

Windows/OS X/Linux/UNIX

DbVisualizer is a feature rich, intuitive multi-database tool for developers, database administrators, and increasingly for advanced analysts providing a single powerful interface across a wide variety of operating systems. With its easy-to-use and clean interface, DbVisualizer has proven to be one of the most cost effective database tools available, yet to mention that it runs on all major operating systems and supports all major RDBMS that are available. Users only need to learn and master one application. DbVisualizer integrates transparently with the operating system being used.

[[Category:Tool]]
[[Category:General articles and guides]]

=== Valentina Studio (Free) ===

http://www.valentina-db.com/valentina-studio-overview

Windows/OS X/Linux/

Valentina Studio is a powerful PostgreSQL Database Server administration and development tool. It offers for free many advanced editors:
* Schema Editor with Tree and Column views
* Diagram Editor with reverse engineering
* SQL Editor with auto-completion, syntax-highlighting, recent and favorite queries, templates of commands, many result tab-panels, ...
* Data Editor with easy sorting and filtering of records without SQL, in-cell editing.
* Related Data Editor that allow s you to learn related records in different modes.
* Import/Export
* SQL dumps
* and so on ...

Valentina Studio PRO - adds additional advanced features as:
* Report Editor to developer reports based on Valentina Report Engine with datasources from PostgreSQL and other databases.
* Diagrams forward engineering
* SQL DIFF
* Data Transfer

[[Category:Tool]]

=== JackDB ===

http://www.jackdb.com/

Html5 Web Browser (Linux/Mac OS X/Windows)

JackDB is a database client that runs entirely in your web browser. There's no software to install locally so you can use it on Mac OS X, Linux, and Windows and it works on all major modern browsers (eg. Chrome, Firefox, IE, Safari, and Opera). It supports connecting to PostgreSQL, as well as MySQL, Oracle, and SQL Server databases.

Features:
* Html5 interface with no client installation
* Query editor with syntax highlighting
* Scrolling result sets
* Schema/Object browser
* SSL connections with certificate pinning
* Eliminates password sharing
* Two-factor authentication
* BLOB display (images and Html5 audio/video)

=== Tadpole DB Hub ===

https://github.com/hangum/TadpoleForDBTools/wiki

Tadpole DB Hub is Unified infrastructure tool, a various environment based interface for managing Apache Hive, Amazon RDS, CUBRID, MariaDB, MySQL, Oracle, SQLite, MSSQL, PostgreSQL and MongoDB databases. It enables you to handle typical DB over the World Wide Web.

Features:
* Intuitive web interface (Safari, Chrome, IE 10, Firefox)
* User Management (Admin, Manager, User)
* Select, Insert, Update, Delete
* Download query result
* SQL Syntax Highlighting
* SQL Formatting
* SQL Statement <-> Java, PHP String Literal Each Convert
* SQL Assist
* Execute SQL Statement
* SQL Result Set to CSV
* SQL History And Export text
* Generate SQL Statement (Select, Insert, Update, Delete, Table, View, Index, Procedure, Function, Trigger)
* Generate ER Diagram (Auto Layout)

=== Vertabelo ===

http://www.vertabelo.com

Vertabelo is an online database designer working under Chrome. It free to use for smaller projects and have a proprietary version for larger database projects.

Features:
* Intuitive HTML5 web interface (Chrome)
* OS independent
* Sharing DB model with team members
* Support for PostgreSQL, MySQL, Oracle, MS SQL Server, DB2, SQLite, HSQLDB,
* Model versioning
* Dynamic/Visual search
* Live model validation
* Reverse engineering

=== pgModeler ===

PostgreSQL Database Modeler

http://pgmodeler.com.br

PostgreSQL Database Modeler, or simply, pgModeler is an open source tool for modeling databases that merges the classical concepts of entity-relationship diagrams with specific features that only PostgreSQL implements. The pgModeler translates the models created by the user to SQL code and apply them onto database clusters from version 8.0 to 9.1. $3.50 per copy as of 2014/04/09.

=== GenMyModel ===

https://www.genmymodel.com

GenMyModel is an online modeling tool supporting [http://www.genmymodel.com/database-diagram-online database modeling]. It is free to use for smaller projects and have a proprietary version for larger database projects.

Features:
* Intuitive HTML5 web interface (Chrome, Firefox, Safari, Internet Explorer)
* OS independent
* Instant sharing and collaboration
* Customizable SQL generators
* Model versioning
* Live model validation

=== DBHawk ===

http://www.datasparc.com/

Web Browser (Linux/Mac OS X/Windows)

DBHawk is a web based SQL tool and reporting software designed for PostgreSQL, Oracle, SQL Server and other databases. Its easy to deploy and use.

Features:
* Web based interface with no client installation
* Advanced Query editor with syntax highlighting and multi tabs results
* Online visual query builder
* Online SQL Report Builder
* Online SQL Job Scheduler
* Export results to html, csv, pdf, google docs, amazon s3
* SQL Auditing and Security
* Schema/Object browser
* SQL and data snippet sharing
* Blob data viewer and editor

=== Datazenit ===

https://datazenit.com/

Windows, Mac OS X, Linux

Datazenit is a cross-platform PostgreSQL and MySQL GUI with data grid, schema builder and interactive charts.
It also has query builder, raw query editor with auto-complete, team collaboration features like connection, query and chart sharing among team members.

=== EDB Postgres Enterprise Manager ===

http://www.enterprisedb.com/products/postgres-enterprise-manager

Windows, Mac OS X, Linux

Postgres Enterprise Manager is the only solution available today that allows you to intelligently manage, monitor, and tune large scale Postgres installations from a single GUI console.

Monitoring features include: server auto-discovery, over 225 pre-configured ready to run probes, custom probes, alert management, personalized alerts, remote monitoring, versatile charting, custom dashboards and web client.

DBA tools include: database objects management, Postgres Expert (best practice configuration settings), Audit Manager, Log Manager, Log Analysis Expert, Capacity Manager and Team Support.

Developer tools include: Query Tool, Data Grid, SQL Profiler, SQL Debugger and Import tools.

Tuning tools include: At-A-Glance performance dashboards, Tuning Wizard, Performance Diagnostics and Index Advisor.

=== ClusterControl by Severalnines ===

https://severalnines.com/product/clustercontrol/for_postgresql

ClusterControl is an all-inclusive open source database management system that allows you to deplore, monitor, manage and scale your database environments. ClusterControl provides the basic functionality you need to get PostgreSQL up-and-running using our deployment wizard, monitoring and basic management abilities like automatic failover, backups, and restores.

* Point and Click Replication Deployments - ClusterControl allows you to easily deploy and configure master/slave replication PostgreSQL instances.
* Advanced Performance Monitoring - ClusterControl monitors queries and detects anomalies with built-in alerts.
* Automated Failover Handling - ClusterControl detects master failures and automatically promotes a new master
* Database Automation - ClusterControl lets you manage configurations, schedule, and restore backups.

=== Database Tour Pro ===

https://www.databasetour.net

Database Tour Pro is a database tool with built-in report builder for Windows. It works with different types of relational databases including PostgreSQL.

Key features:

* Creating tables.
* Viewing and editing data.
* Several ways to print data.
* Built-in report engine and visual report designer with templates, expressions, preview etc.
* Expression builder for report and export expressions.
* Building and executing SQL queries. Support for execution of multi statement SQL scripts. Syntax highlighting in SQL editor. Support for parameterized SQL queries.
* Enhanced database grids, which allow to view and manipulate the data in the most convenient way, including sorting by clicking column header, changing row heights, resizing columns etc.
* Command line support for executing queries, opening tables, export-import operations, loading reports etc. with logging the performed operations.
* Searching and replacing text in database with ability to choose fields, record range etc.
* Importing data to table from another table or a query.
* Exporting data from open table or query to file(s) like text, CSV, HTML, XLSX, XML, RTF, DBF or to another relational database.
* Copying data to clipboard.
* Viewing and editing Blob data, such as large text and graphics.
* Tools for editing text fields (trimming, changing case of symbols, replacing text).
* Customized data view (font, background).
* Conditional formatting data in database grids and reports.
* Ability to control transactions.

=== Reportizer ===

https://www.reportizer.net

Reportizer is a database reporting tool, which allows easy creating, modifying, and printing database reports from different types of databases, including PostgreSQL. Reports can be edited in convenient visual report builder or in text mode. It supports calculating fields, multi-column reports, expressions, grouping, displaying images etc. Reportizer can export reports to HTML, XLSX, image, or internal format. There is an ability to load and print reports from command line. Reportizer allows to manage report collections, which can be held either in files or in database tables.

=== Exportizer Pro ===

https://www.vlsoftware.net/exportizer-pro/

Exportizer Pro is a database export tool, which can work with PostgreSQL database either as source or destination. It allows to export data to database, file, clipboard, or printer.
* Possible sources: ODBC data sources, files of DB (Paradox), DBF (dBase, FoxPro), MDB, ACCDB, XLS, XLSX, GDB, IB, FDB, HTML, UDL, DBC, TXT, CSV types, databases specified by ADO connection strings, and databases like Oracle, SQL Server, Postgresql, DB2, Informix, SQLite, Interbase etc.
* Possible destinations: file formats like text, CSV, XLS, XLSX, RTF, XML, HTML, PDF, DBF, SLK, SQL script, and relational database of any supported type.
* It is possible to export all or selected tables from an open database at once.
* Exportizer Pro can automatically detect the most known image types (JPEG, PNG, GIF, BMP, ICO) in BLOB fields and export them, for example, to HTML or XLSX.
* There is an ability to specify the source-to-target field mappings.
* Export operations can be performed either via the program interface or via command line.

=== TiCodeX SQL Schema Compare ===

https://www.ticodex.com/

TiCodeX SQL Schema Compare is a tools that allows database administrators to compare multiple database schema in order to manage versioning. 
The software runs on Windows, Linux and Mac and supports Microsoft SQL (MS-SQL), MySQL, PostgreSQL, Azure SQL and MS-SQL on Amazon RDS.

'''Key Features:'''
* Runs on Windows, Linux and MacOS
* Localized in English, German and Italian
* Compare changes between two SQL Database schemas (as example from development to test to production)
* View database differences and explore schema changes to see what's going on
* Automatically create full database migration scripts
* Securely save database and server login details

=== pgMustard ===

https://www.pgmustard.com/

pgMustard is a performance tool for PostgreSQL that provides a user interface for your EXPLAIN ANALYSE output, as well as tips on what to do to speed up your query.

Features:
* Quickly see the slowest operations
* Code snippets to tie operations back to the query
* Tips to speed up your query💡
* Does the arithmetic for you (including wall clock times)
* Explanations of operation types and key concepts
* Links to relevant documentation and blog posts

Requirements:
* JSON format plans
* Any supported version of PostgreSQL
* English language only
* Web application, no installation required

== No longer Supported/Developed ==

* OpenOffice postgresql SDBC Driver. no work on the project since 2010; last version was a beta. http://www.openoffice.org/dba/drivers/postgresql/index.html
* RedHat: hasn't been refreshed since Pg 8.4. http://sources.redhat.com/rhdb

Don't Do This

2019-04-03T18:38:29Z

Dfetter: /* Tool usage */

A short list of common mistakes.

= Database Encoding =

== Don't use SQL_ASCII ==

=== Why not? ===

While the name suggests that this encoding is in some meaningful way related to ASCII, it is not. Instead, it simply forbids the use of NUL bytes.

=== When should you? ===

Never.

= Tool usage =

== Don't use psql -W or --password ==

Don't use <tt>psql -W</tt> or <tt>psql --password</tt>.

=== Why not? ===

Using the --password or -W flags will tell [https://www.postgresql.org/docs/current/static/reference-client.html psql] to prompt you for a password, before trying to connect to the server - so you'll be prompted for a password even if the server doesn't require one.

It's never required, as if the server does require a password psql will prompt you for one, and it can be very confusing when setting up permissions. If you're connecting with -W to a server configured to allow you access via <tt>peer</tt> authentication you may think that it's requiring a password when it really isn't. And if the user you're logging in as doesn't have a password set or you enter the wrong password at the prompt you'll still be logged in and think you have the right password - but you won't be able to log in from other clients (that connect via localhost) or when logged in as other users.

=== When should you? ===

Never, pretty much. It will save a round trip to the server but that's about it.

 
== Don't use rules ==

Don't use [https://www.postgresql.org/docs/current/static/sql-createrule.html rules]. If you think you want to, use a [https://www.postgresql.org/docs/current/static/plpgsql-trigger.html trigger] instead.

=== Why not? ===

Rules are incredibly powerful, but they don't do what they look like they do. They look like they're some conditional logic, but they actually rewrite a query to modify it or add additional queries to it.

That means that [http://blog.rhodiumtoad.org.uk/2010/06/21/the-rule-challenge/ all non-trivial rules are incorrect].

Depesz has [https://www.depesz.com/2010/06/15/to-rule-or-not-to-rule-that-is-the-question/ more to say] about them.

=== When should you? ===

Never. While the rewriter is an implementation detail of VIEWs, there is no reason to pry up this cover plate directly.

 
== Don't use table inheritance ==

Don't use [https://www.postgresql.org/docs/current/tutorial-inheritance.html table inheritance]. If you think you want to, use foreign keys instead.

=== Why not? ===

Table inheritance was part of a fad wherein the database was closely coupled to object-oriented code. It turned out that coupling things that closely didn't actually produce the desired results.

=== When should you? ===

Never. Now that table partitioning is done natively, the only plausible use case for table inheritance has been replaced by a native feature that handles tuple routing, etc., without bespoke code.


= SQL constructs =

== Don't use NOT IN ==

Don't use <code>NOT IN</code>, or any combination of <code>NOT</code> and <code>IN</code> such as <code>NOT (x IN (select…))</code>.

(If you think you wanted <code>NOT IN (select …)</code> then you should rewrite to use <code>NOT EXISTS</code> instead.)

=== Why not? ===

Two reasons:

1. <code>NOT IN</code> behaves in unexpected ways if there is a null present:

<code>select * from foo where col not in (1,null); -- always returns 0 rows</code>

<code>select * from foo where col not in (select x from bar);
-- returns 0 rows if any value of bar.x is null</code>

This happens because <code>col IN (1,null)</code> returns <code>TRUE</code> if col=1, and <code>NULL</code> otherwise (i.e. it can never return <code>FALSE</code>). Since <code>NOT (TRUE)</code> is <code>FALSE</code>, but <code>NOT (NULL)</code> is still <code>NULL</code>, there is no way that <code>NOT (col IN (1,null))</code> (which is the same thing as <code>col NOT IN (1,null)</code>) can return <code>TRUE</code> under any circumstances.

2. Because of point 1 above, <code>NOT IN (SELECT ...)</code> does not optimize very well. In particular, the planner can't transform it into an anti-join, and so it becomes either a hashed Subplan or a plain Subplan. The hashed subplan is fast, but the planner only allows that plan for small result sets; the plain subplan is '''horrifically''' slow (in fact O(N²)). This means that the performance can look good in small-scale tests but then slow down by 5 or more orders of magnitude once a size threshold is crossed; you '''do not''' want this to happen.

=== When should you? ===

<code>NOT IN (list,of,values,...)</code> is mostly safe ''unless'' you might have a null in the list (via a parameter or otherwise). So it's sometimes natural and even advisable to use it when excluding specific constant values from a query result.

 
== Don't use upper case table or column names ==

Don't use NamesLikeThis, use names_like_this.

=== Why not? ===

PostgreSQL folds all names - of tables, columns, functions and everything else - to lower case unless they're "double quoted".

So <tt>create table Foo()</tt> will create a table called <tt>foo</tt>, while <tt>create table "Bar"()</tt> will create a table called <tt>Bar</tt>.

These select commands will work: <tt>select * from Foo</tt>, <tt>select * from foo</tt>, <tt>select * from "Bar"</tt>.

These will fail with "no such table": <tt>select * from "Foo"</tt>, <tt>select * from Bar</tt>, <tt>select * from bar</tt>.

This means that if you use uppercase characters in your table or column names you have to either ''always'' double quote them or ''never'' double quote them. That's annoying enough by hand, but when you start using other tools to access the database, some of which always quote all names and some don't, it gets very confusing.

Stick to using a-z, 0-9 and underscore for names and you never have to worry about quoting them.

=== When should you? ===

If it's important that "pretty" names are displaying in report output then you might want to use them. But you can also use column aliases to use lower case names in a table and still get pretty names in the output of a query: <tt>select character_name as "Character Name" from foo</tt>.

 
== Don't use BETWEEN (especially with timestamps) ==

=== Why not? ===

<code>BETWEEN</code> uses a closed-interval comparison: the values of both ends of the specified range are included in the result.

This is a particular problem with queries of the form

<code>SELECT * FROM blah WHERE timestampcol BETWEEN '2018-06-01' AND '2018-06-08'</code>

This will include results where the timestamp is ''exactly'' 2018-06-08 00:00:00.000000, but not timestamps later in that same day. So the query might seem to work, but as soon as you get an entry exactly on midnight, you'll end up double-counting it.

Instead, do:

<code>SELECT * FROM blah WHERE timestampcol >= '2018-06-01' AND timestampcol < '2018-06-08'</code>

=== When should you? ===

<code>BETWEEN</code> is safe for discrete quantities like integers or dates, as long as you remember that both ends of the range are included in the result. But it's a bad habit to get into.



= Date/Time storage =

== Don't use timestamp (without time zone) ==

Don't use the <tt>timestamp</tt> type to store timestamps, use <tt>timestamptz</tt> (also known as <tt>timestamp with time zone</tt>) instead.

=== Why not? ===

<tt>timestamptz</tt> records a single moment in time. Despite what the name says it doesn't store a timestamp, just a point in time described as the number of microseconds since January 1st, 2000 in UTC. You can insert values in any timezone and it'll store the point in time that value describes. By default it will display times in your current timezone, but you can use <tt>at time zone</tt> to display it in other time zones.

Because it stores a point in time it will do the right thing with arithmetic involving timestamps entered in different timezones - including between timestamps from the same location on different sides of a daylight savings time change.

<tt>timestamp</tt> (also known as <tt>timestamp without time zone</tt>) doesn't do any of that, it just stores a date and time you give it. You can think of it being a picture of a calendar and a clock rather than a point in time. Without additional information - the timezone - you don't know what time it records. Because of that, arithmetic between timestamps from different locations or between timestamps from summer and winter may give the wrong answer.

So if what you want to store is a point in time, rather than a picture of a clock, use timestamptz.

[https://it.toolbox.com/blogs/josh-berkus/zone-of-misunderstanding-092811 More about timestamptz].

=== When should you? ===

If you're dealing with timestamps in an abstract way, or just saving and retrieving them from an app, where you aren't going to be doing arithmetic with them then timestamp might be suitable.

 
== Don't use timestamp (without time zone) to store UTC times ==

Storing UTC values in a <code>timestamp without time zone</code> column is, unfortunately, a practice commonly inherited from other databases that lack usable timezone support.

Use <code>timestamp with time zone</code> instead.

=== Why not? ===

Because there is no way for the database to know that UTC is the intended timezone for the column values.

This complicates many otherwise useful time calculations. For example, "last midnight in the timezone given by u.timezone" becomes this:

<code>date_trunc('day', now() AT TIME ZONE u.timezone) AT TIME ZONE u.timezone AT TIME ZONE 'UTC'</code>

And "the midnight prior to <code>x.datecol</code> in u.timezone" becomes this:

<code>date_trunc('day', x.datecol AT TIME ZONE 'UTC' AT TIME ZONE u.timezone)
AT TIME ZONE u.timezone AT TIME ZONE 'UTC'</code>

=== When should you? ===

If compatibility with non-timezone-supporting databases trumps all other considerations.

 
== Don't use timetz ==

Don't use the <tt>timetz</tt> type. You probably want <tt>timestamptz</tt> instead.

=== Why not? ===

Even the manual tells you it's only implemented for SQL compliance.

<blockquote>The type time with time zone is defined by the SQL standard, but the definition exhibits properties which lead to questionable usefulness. In most cases, a combination of date, time, timestamp without time zone, and timestamp with time zone should provide a complete range of date/time functionality required by any application.</blockquote>

=== When should you? ===

Never.

 
== Don't use CURRENT_TIME ==

Don't use the <code>CURRENT_TIME</code> function. Use whichever of these is appropriate:

* <code>CURRENT_TIMESTAMP</code> or <code>now()</code> if you want a <code>timestamp with time zone</code>,
* <code>LOCALTIMESTAMP</code> if you want a <code>timestamp without time zone</code>,
* <code>CURRENT_DATE</code> if you want a <code>date</code>,
* <code>LOCALTIME</code> if you want a <code>time</code>

=== Why not? ===

It returns a value of type <code>timetz</code>, for which see the previous entry.

=== When should you? ===

Never.

 
== Don't use timestamp(0) or timestamptz(0) ==

Don't use a precision specification, especially not 0, for timestamp columns or casts to timestamp.

Use <code>date_trunc('second', blah)</code> instead.

=== Why not? ===

Because it rounds off the fractional part rather than truncating it as everyone would expect. This can cause unexpected issues; consider that when you store <code>now()</code> into such a column, you might be storing a value half a second in the future.

=== When should you? ===

Never.



= Text storage =

== Don't use char(n) ==

Don't use the type <tt>char(n)</tt>. You probably want <tt>text</tt>.

=== Why not? ===

Any string you insert into a <code>char(n)</code> field will be padded with spaces to the declared width. That's probably not what you actually want.

The manual says:

<blockquote>Values of type character are physically padded with spaces to the specified width n, and are stored and displayed that way. However, trailing spaces are treated as semantically insignificant and disregarded when comparing two values of type character. In collations where whitespace is significant, this behavior can produce unexpected results; for example <code>SELECT 'a '::CHAR(2) collate "C" < E'a\n'::CHAR(2)</code> returns true, even though C locale would consider a space to be greater than a newline. Trailing spaces are removed when converting a character value to one of the other string types. Note that trailing spaces are semantically significant in character varying and text values, and when using pattern matching, that is LIKE and regular expressions.</blockquote>

That should scare you off it.

The space-padding does waste space, but doesn't make operations on it any faster; in fact the reverse, thanks to the need to strip spaces in many contexts.

It's important to note that from a storage point of view <code>char(n)</code> '''is not a fixed-width type'''. The actual number of bytes varies since characters may take more than one byte, and the stored values are therefore treated as variable-length anyway (even though the space padding is included in the storage).

=== When should you? ===

When you're porting very, very old software that uses fixed width fields. Or when you read the snippet from the manual above and think "yes, that makes perfect sense and is a good match for my requirements" rather than gibbering and running away.

 
== Don't use char(n) even for fixed-length identifiers ==

Sometimes people respond to "don't use <code>char(n)</code>" with "but my values must always be exactly N characters long" (e.g. country codes, hashes, or identifiers from some other system). '''It is still a bad idea to use <code>char(n)</code> even in these cases.'''

Use <code>text</code>, or a domain over text, with <code>CHECK(length(VALUE)=3)</code> or <code><nowiki>CHECK(VALUE ~ '^[[:alpha:]]{3}$')</nowiki></code> or similar.

=== Why not? ===

Because <code>char(n)</code> doesn't reject values that are too short, it just silently pads them with spaces. So there's no actual benefit over using <code>text</code> with a constraint that checks for the exact length. As a bonus, such a check can also verify that the value is in the correct format.

Remember, '''there is no performance benefit whatsoever to using <code>char(n)</code> over <code>varchar(n)</code>.''' In fact the reverse is true. One particular problem that comes up is that if you try and compare a <code>char(n)</code> field against a parameter where the driver has explicitly specified a type of <code>text</code> or <code>varchar</code>, you may be unexpectedly unable to use an index for the comparison. This can be hard to debug since it doesn't show up on manual queries.

=== When should you? ===

Never.

 

== Don't use varchar(n) by default ==

Don't use the type <tt>varchar(n)</tt> by default. Consider <tt>varchar</tt> (without the length limit) or <tt>text</tt> instead.

=== Why not? ===

<tt>varchar(n)</tt> is a variable width text field that will throw an error if you try and insert a string longer than n characters (not bytes) into it.

<tt>varchar</tt> (without the <tt>(n)</tt>) or <tt>text</tt> are similar, but without the length limit. If you insert the same string into the three field types they will take up exactly the same amount of space, and you won't be able to measure any difference in performance.

If what you really need is a text field with an length limit then varchar(n) is great, but if you pick an arbitrary length and choose varchar(20) for a surname field you're risking production errors in the future when Hubert Blaine Wolfeschlegelsteinhausenbergerdorff signs up for your service.

Some databases don't have a type that can hold arbitrary long text, or if they do it's not as convenient or efficient or well-supported as varchar(n). Users from those databases will often use something like <tt>varchar(255)</tt> when what they really want is <tt>text</tt>.

If you need to constrain the value in a field you probably need something more specific than a maximum length - maybe a minimum length too, or a limited set of characters - and a [https://www.postgresql.org/docs/current/static/ddl-constraints.html#DDL-CONSTRAINTS-CHECK-CONSTRAINTS check constraint] can do all of those things as well as a maximum string length.

=== When should you? ===

When you want to, really. If what you want is a text field that will throw an error if you insert too long a string into it, and you don't want to use an explicit check constraint then varchar(n) is a perfectly good type. Just don't use it automatically without thinking about it.



= Other data types =

== Don't use money ==

The <tt>money</tt> data type isn't actually very good for storing monetary values. Numeric, or (rarely) integer may be better.

=== Why not? ===

[https://www.postgresql.org/message-id/flat/20130328092819.237c0106@imp#20130328092819.237c0106@imp lots of reasons.]

It's a fixed-point type, implemented as a machine int, so arithmetic with it is fast. But it doesn't handle fractions of a cent (or equivalents in other currencies), it's rounding behaviour is probably not what you want.

It doesn't store a currency with the value, rather assuming that all money columns contain the currency specified by the database's [https://www.postgresql.org/docs/current/static/runtime-config-client.html#GUC-LC-MONETARY lc_monetary] locale setting. If you change the lc_monetary setting for any reason, all money columns will contain the wrong value. That means that if you insert '$10.00' while lc_monetary is set to 'en_US.UTF-8' the value you retrieve may be '10,00 Lei' or '¥1,000' if lc_monetary is changed.

Storing a value as a numeric, possibly with the currency being used in an adjacent column, might be better.

=== When should you? ===

If you're only working in a single currency, aren't dealing with fractional cents and are only doing addition and subtraction then money might be the right thing.

Deleting duplicates

2019-03-22T19:56:35Z

Dfetter:

{{SnippetInfo|Deleting duplicates|version=8.4+|lang=SQL|category=Administrative}}

A frequent question in IRC is how to delete rows that are duplicates over a set of columns, keeping only the one with the lowest ID.

This query does that for all rows of tablename having the same column1, column2, and column3.

<source lang="sql">
DELETE FROM tablename
WHERE id IN (
SELECT
id
FROM (
SELECT
id,
row_number() OVER w as rnum
FROM tablename
WINDOW w AS (
PARTITION BY column1, column2, column3
ORDER BY id
)

) t
WHERE t.rnum > 1);
</source>

Sometimes a timestamptz field is used instead of an ID field.

Foreign data wrappers

2019-03-13T05:35:48Z

Dfetter:

= Foreign Data Wrappers =
In 2003, a new specification called [[SQL/MED]] ("SQL Management of External Data") was added to the SQL standard. It is a standardized way of handling access to remote objects from SQL databases. In 2011, PostgreSQL 9.1 was released with read-only support of this standard, and in 2013 write support was added with PostgreSQL 9.3.

There are now a variety of Foreign Data Wrappers (FDW) available which enable PostgreSQL Server to different remote data stores, ranging from other SQL databases through to flat file. This page list some of the wrappers currently available. Another [https://pgxn.org/tag/fdw/ fdw list] can be found at [https://pgxn.org/ the PGXN website].

Please keep in mind that most of these wrappers are '''not officially supported by the PostgreSQL Global Development Group''' (PGDG) and that some of these projects are '''still in Beta''' version. Use carefully!

== Generic SQL Database Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
|ODBC
|Native
|
|[https://github.com/CartoDB/odbc_fdw github]
|
|
|CartoDB took over active development of the ODBC FDW for PG 9.5+
|-
|JDBC
|Native
|
|[https://github.com/atris/JDBC_FDW github]
|
|
| Not maintained ?
|-
|JDBC2
|Native
|
|[https://github.com/heimir-sverrisson/jdbc2_fdw github]
|
|
|
|-
| [https://www.sqlalchemy.org/ SQL_Alchemy]
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/Kozea/Multicorn GitHub]
| [https://pgxn.org/dist/multicorn/ PGXN]
| [https://multicorn.org/foreign-data-wrappers/#sqlalchemy-foreign-data-wrapper documentation]
| Can be used to access data stored in any database supported by the sqlalchemy python toolkit.
|-
| VirtDB
| Native
| GPL
| [https://github.com/virtdb/virtdb-fdw GitHub]
|
|
| A generic FDW to access VirtDB data sources (SAP ERP, Oracle RDBMS)
|}

== Specific SQL Database Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
|[https://www.postgresql.org/ PostgreSQL]
|Native
|PostgreSQL
|[https://git.postgresql.org/gitweb/?p=postgresql.git;a=tree;f=contrib/postgres_fdw;hb=HEAD git.postgresql.org]
|
|[https://www.postgresql.org/docs/current/postgres-fdw.html documentation]
|
|-
|[https://www.oracle.com/index.html Oracle]
|Native
|PostgreSQL
|[https://github.com/laurenz/oracle_fdw github]
|[https://pgxn.org/dist/oracle_fdw/ PGXN]
|[http://laurenz.github.io/oracle_fdw/ website]
|
|-
|[https://www.mysql.com/ MySQL]
|Native
|
|[https://github.com/EnterpriseDB/mysql_fdw github]
|[https://pgxn.org/dist/mysql_fdw/ PGXN]
|[https://www.enterprisedb.com/blog/new-oss-tool-links-postgres-and-mysql example]
|FDW for MySQL
|-
|Informix
|Native
|PostgreSQL
|[https://github.com/credativ/informix_fdw github]
|
|
|
|-
|Firebird
|Native
|
|[https://github.com/ibarwick/firebird_fdw/ github]
|[https://pgxn.org/dist/firebird_fdw/ PGXN]
|
| currently work-in-progress.
|-
|SQLite
|Native
|
|[https://github.com/gleu/sqlite_fdw github]
|
|
|An FDW for SQLite3 (read-only)
|-
|[https://www.sqlite.org/index.html SQLite]
|Native
|PostgreSQL
|[https://github.com/pgspider/sqlite_fdw github]
|[https://pgxn.org/dist/sqlite_fdw PGXN]
|[https://github.com/pgspider/sqlite_fdw/blob/master/README.md README]
|An FDW for SQLite3 (write support and several pushdown optimization)
|-
|Sybase / MS SQL Server
|Native
|
|[https://github.com/tds-fdw/tds_fdw github]
|[https://pgxn.org/dist/tds_fdw/ PGXN]
|
|An FDW for Sybase and Microsoft SQL server
|-
|[https://www.monetdb.org/ MonetDB]
|Native
|
|[https://github.com/snaga/monetdb_fdw github]
|
|
|
|}

== NoSQL Database Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
|[https://cloud.google.com/bigtable/ BigTable or HBase]
|[https://github.com/posix4e/rpgffi Native Rust Binding (RPGFFI)]
|MIT
|[https://github.com/durch/google-bigtable-postgres-fdw Github]
|
|
|
|-
|[http://cassandra.apache.org/ Cassandra]
|[https://multicorn.org/ Multicorn]
|MIT
|[https://github.com/rankactive/cassandra-fdw Github]
|[https://rankactive.com/resources/postgresql-cassandra-fdw Rankactive]
|
|
|-
| Cassandra2
| Native
| MIT
|[https://github.com/jaiminpan/cassandra2_fdw Github]
|
|
|
|-
|-
| [http://cassandra.apache.org Cassandra]
| [https://multicorn.org/ Multicorn]
| PostgreSQL
|[https://github.com/wjch-krl/pgCassandra Github]
|
|
|
|-
|[https://clickhouse.yandex/ ClickHouse]
|[https://multicorn.org/ Multicorn]
|BSD
|[https://github.com/Infinidat/infi.clickhouse_fdw/ Github]
|
|[https://github.com/Infinidat/infi.clickhouse_fdw/blob/master/README.md README]
|
|-
|[http://couchdb.apache.org/ CouchDB]
|Native
|PostgreSQL
|[https://github.com/ZhengYang/couchdb_fdw Github]
|[https://pgxn.org/dist/couchdb_fdw/ PGXN]
|
| Original version
|-
|[http://couchdb.apache.org/ CouchDB]
|Native
|PostgreSQL
|[https://github.com/golgauth/couchdb_fdw Github]
|
|
| golgauth version (9.1 - 9.2+ compatible)
|-
| [https://github.com/griddb/griddb_nosql GridDB]
| Native
| PostgreSQL
| [https://github.com/pgspider/griddb_fdw Github]
|
| [https://github.com/pgspider/griddb_fdw/blob/master/README.md README]
|
|-
| InfluxDB
| Native
| PostgreSQL
| [https://github.com/pgspider/influxdb_fdw Github]
|
| [https://github.com/pgspider/influxdb_fdw/blob/master/README.md README]
|
|-
|[https://fallabs.com/kyototycoon/ Kyoto Tycoon ]
|Native
|MIT
|[https://github.com/cloudflare/kt_fdw Github]
|
|
|
|-
|[https://www.mongodb.com/ MongoDB]
|Native
|GPL3+
|[https://github.com/EnterpriseDB/mongo_fdw Github]
|[https://pgxn.org/dist/mongo_fdw/ PGXN]
|[https://github.com/EnterpriseDB/mongo_fdw/blob/master/README.md README]
|EDB version
|-
|[https://www.mongodb.com/ MongoDB]
| [https://multicorn.org/ Multicorn]
| MIT
| [https://github.com/dwa/mongoose_fdw Github]
|
|
|
|-
| [https://www.mongodb.com/ MongoDB]
| [https://multicorn.org/ Multicorn]
|
| [https://github.com/asya999/yam_fdw Github]
|
|
| Yet Another Postgres FDW for MongoDB
|-
|[https://neo4j.com/ Neo4j]
|[https://multicorn.org/ Multicorn]
|GPLv3
|[https://github.com/sim51/neo4j-fdw Github]
|
|[https://github.com/sim51/neo4j-fdw/blob/master/README.adoc README]
|FWD for Neo4j and also add a Cypher function to Pg
|-
|[https://neo4j.com/ Neo4j]
|Native
|?
|[https://github.com/nuko-yokohama/neo4j_fdw Github]
|
|
|
|-
|[http://quasar-analytics.org/ Quasar]
|Native
|Apache
|[https://github.com/slamdata/quasar-fdw Github]
|
|
|
|-
|[https://redis.io/ Redis]
|Native
|PostgreSQL
|[https://github.com/pg-redis-fdw/redis_fdw Github]
|
|
|
|-
| [https://redis.io/ Redis]
| Native
| BSD
| [https://github.com/nahanni/rw_redis_fdw Github]
|
|
|
|-
| [https://rethinkdb.com/ RethinkDB]
| [https://multicorn.org/ Multicorn]
| MIT
| [https://github.com/rotten/rethinkdb-multicorn-postgresql-fdw Github]
|
| [https://rethinkdb.com/blog/postgres-foreign-data-wrapper/ blog]
|
|-
| [https://github.com/basho/riak Riak]
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/kiskovacs/riak-multicorn-pg-fdw Github]
|
|
|
|-
|[http://whitedb.org/ WhiteDB]
| Native
| MIT
| [https://github.com/Kentik/wdb_fdw Github]
|
|
|
|}

== File Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
| CSV
| Native
| PostgreSQL
|[https://git.postgresql.org/gitweb/?p=postgresql.git;a=tree;f=contrib/file_fdw;hb=HEAD git.postgresql.org]
|
| [https://www.postgresql.org/docs/current/file-fdw.html documentation]
| Delivered as an official extension of PostgreSQL 9.1 / [https://www.depesz.com/2011/03/14/waiting-for-9-1-foreign-data-wrapper/ example] / [http://www.postgresonline.com/journal/archives/250-File-FDW-Family-Part-1-file_fdw.html Another example]
|-
| CSV
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/Kozea/Multicorn GitHub]
| [https://pgxn.org/dist/multicorn/ PGXN]
| [https://multicorn.org/foreign-data-wrappers/#csv-foreign-data-wrapper documentation]
| Each column defined in the table will be mapped, in order, against columns in the CSV file.
|-
| CSV / Text Array
| Native
|
| [https://github.com/adunstan/file_text_array_fdw GitHub]
|
| [http://www.postgresonline.com/journal/archives/251-File-FDW-Family-Part-2-file_textarray_fdw-Foreign-Data-Wrapper.html How to]
| Another CSV wrapper
|-
| CSV / Fixed-length
| Native
|
| [https://github.com/adunstan/file_fixed_length_record_fdw GitHub]
|
|
|
|-
| CSV / gzipped
| [https://multicorn.org/ Multicorn]
|
| [https://github.com/dialogbox/py_csvgz_fdw GitHub]
|
|
| PostgreSQL Foreign Data Wrapper for gzipped cvs file
|-
| Compressed File
| Native
|
| [https://github.com/gokhankici/compressedfile_fdw GitHub]
|
|
|
|-
| Document Collection
| Native
| PostgreSQL
| [https://github.com/ZhengYang/dc_fdw GitHub]
|
| [https://github.com/ZhengYang/dc_fdw/wiki wiki]
|
|-
| JSON
| Native
| GPL3
| [https://github.com/nkhorman/json_fdw GitHub]
|
| [https://www.citusdata.com/blog/2013/05/30/run-sql-on-json-files-without-any-data-loads/ Example]
|
|-
| Multi-File
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/Kozea/Multicorn GitHub]
| [https://pgxn.org/dist/multicorn/ PGXN]
| [https://multicorn.org/foreign-data-wrappers/#filesystem-foreign-data-wrapper doc]
| Access data stored in various files in a filesystem. The files are looked up based on a pattern, and parts of the file's path are mapped to various columns, as well as the file's content itself.
|-
| Multi CDR
| Native
| PostgreSQL
| [https://github.com/theirix/multicdr_fdw GitHub]
| [https://pgxn.org/dist/multicdr_fdw/ PGXN]
|
|
|-
| pg_dump
| Native
| New BSD
| [https://github.com/MeetMe/dump_fdw GitHub]
|
|
| Allows querying of data directly against Postgres custom format files created by pg_dump
|-
| TAR Files
| Native
|
| [https://github.com/beargiles/tarfile-fdw GitHub]
|
|
|
|-
| XML
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/Kozea/Multicorn GitHub]
| [https://pgxn.org/dist/multicorn/ PGXN]
|
|
|-
| ZIP Files
| Native
|
| [https://github.com/beargiles/zipfile-fdw GitHub]
|
|
|
|}

== Geo Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
|[https://www.gdal.org GDAL/OGR]
|Native
|MIT
|[https://github.com/pramsey/pgsql-ogr-fdw GitHub]
|
|
|A wrapper for data sources with a [https://www.gdal.org GDAL/OGR] driver, including databases like Oracle, Informix, SQLite, SQL Server, ODBC as well as file formats like Shape, FGDB, MapInfo, CSV, Excel, OpenOffice, OpenStreetMap PBF and XML, OGC WebServices, [https://www.gdal.org/ogr_formats.html and more] Spatial columns are linked in as PostGIS geometry if PostGIS is installed.
|-
| Geocode / GeoJSON
| [https://multicorn.org/ Multicorn]
| GPL
| [https://github.com/bosth/geofdw GitHub]
|
|
| a collection of PostGIS-related foreign data wrappers
|-
| [https://wiki.openstreetmap.org/wiki/PBF_Format Open Street Map PBF]
| Native
| PostgreSQL
| [https://github.com/vpikulik/postgres_osm_pbf_fdw GitHub]
|
|
|
|}

== LDAP Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
| LDAP
| Native
|
| [https://github.com/guedes/ldap_fdw GitHub]
| [https://pgxn.org/dist/ldap_fdw/ PGXN]
|
| Allows to query an LDAP server and retrieve data from some pre-configured Organizational Unit
|-
| LDAP
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/Kozea/Multicorn GitHub]
| [https://pgxn.org/dist/multicorn/ PGXN]
| [https://multicorn.org/foreign-data-wrappers/#idldap-foreign-data-wrapper documentation]
|
|}

== Generic Web Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
| Git
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/Kozea/Multicorn GitHub]
| [https://pgxn.org/dist/multicorn/ PGXN]
|
|
|-
| Git
| Native
| MIT
| [https://github.com/franckverrot/git_fdw GitHub]
|
|
|
|-
| ICAL
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/daamien/Multicorn/blob/master/python/multicorn/icalfdw.py GitHub]
|
| [https://wiki.postgresql.org/images/7/7e/Conferences-write_a_foreign_data_wrapper_in_15_minutes-presentation.pdf pdf]
|
|-
| IMAP
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/Kozea/Multicorn GitHub]
| [https://pgxn.org/dist/multicorn/ PGXN]
| [https://multicorn.org/foreign-data-wrappers/#idimap-foreign-data-wrapper documentation]
|
|-
| RSS
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/Kozea/Multicorn GitHub]
| [https://pgxn.org/dist/multicorn/ PGXN]
| [https://multicorn.org/foreign-data-wrappers/#idrss-foreign-data-wrapper documentation]
| This fdw can be used to access items from an rss feed.
|-
| www
| Native
| PostgreSQL
| [https://github.com/cyga/www_fdw/ GitHub]
| [https://pgxn.org/dist/www_fdw/ PGXN]
| [https://github.com/cyga/www_fdw/wiki wiki]
| Allows to query different web services
|}

== Specific Web Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
| Database.com
| [https://multicorn.org/ Multicorn]
| BSD
| [https://github.com/metadaddy/Database.com-FDW-for-PostgreSQL GitHub]
|
|
|
|-
| Dun & Badstreet
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/dpmorel/dnb_fdw GitHub]
|
|
| Access to the [https://fr.wikipedia.org/wiki/Data_Universal_Numbering_System Data Universal Numbering System] (DUNS)
|-
| DynamoDB
| [https://multicorn.org/ Multicorn]
| GPL
| [https://github.com/avances123/dynamodb_fdw GitHub]
|
|
|
|-
| Facebook
| [https://multicorn.org/ Multicorn]
|
| [https://github.com/mrwilson/fb-psql GitHub]
|
|
|
|-
| Fixer.io
| based on www_fdw
|
| [https://github.com/hakanensari/frankfurter GitHub]
|
|
|
|-
| Google
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/Kozea/Multicorn GitHub]
| [https://pgxn.org/dist/multicorn/ PGXN]
|
|
|-
| Heroku dataclips
| Native
| PostgreSQL
| [https://github.com/petergeoghegan/dataclips_fdw GitHub]
|
|
|
|-
| Keycloak
| [https://multicorn.org/ Multicorn]
| MIT
| [https://github.com/schne324/foreign-keycloak-wrapper GitHub]
| [https://pgxn.org/dist/foreign-keycloak-wrapper/ PGXN]
| [https://github.com/schne324/foreign-keycloak-wrapper/blob/master/README.md README]
| Direct database integration with the [https://www.keycloak.org Keycloak] open-source Identity/Access Management solution.
|-
| Mailchimp
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/daamien/mailchimp_fdw GitHub]
|
|
| Beta
|-
| [http://parseplatform.org/ Parse]
| [https://multicorn.org/ Multicorn]
| MIT
| [https://github.com/spacialdb/parse_fdw GitHub]
|
|
|
|-
| S3
| Native
| PostgreSQL
| [https://github.com/umitanuki/s3_fdw GitHub]
| [https://pgxn.org/dist/s3_fdw/ PGXN]
|
|
|-
| S3CSV
| [https://multicorn.org/ Multicorn]
| GPL 3
| [https://github.com/eligoenergy/s3csv_fdw GitHub]
|
|
| This is meant to replace s3_fdw that does is not supported on PostgreSQL version 9.2+
|-
| Telegram
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/guedes/telegram_fdw GitHub]
|
|
| telegram_fdw is a Telegram BOT implemented using the PostgreSQL foreign data wrapper interface.
|-
| Twitter
| Native
| PostgreSQL
| [https://github.com/umitanuki/twitter_fdw GitHub]
| [https://pgxn.org/dist/twitter_fdw/ PGXN]
|
| A wrapper fetching text messages from Twitter over the Internet and returning a table
|-
| [https://www.treasuredata.com/ Treasure Data]
| Native
| Apache
| [https://github.com/komamitsu/treasuredata_fdw GitHub]
| [https://pgxn.org/dist/treasuredata_fdw PGXN]
|
| A FDW for Treasure Data internally using a Rust library
|-
| [https://www.treasuredata.com/ Treasure Data]
| [https://multicorn.org/ Multicorn]
| Apache
| [https://github.com/komamitsu/td-fdw GitHub]
|
|
|
|-
| Google Spreadsheets
| [https://multicorn.org/ Multicorn]
| MIT
| [https://github.com/lincolnturner/gspreadsheet_fdw GitHub]
|
|
|
|}

== Big Data Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
|Elastic Search
| [https://multicorn.org/ Multicorn]
| PostgreSQL
|[https://github.com/Mikulas/pg-es-fdw GitHub]
|
|
|
|-
| Google BigQuery
| [https://multicorn.org/ Multicorn]
| MIT
|[https://github.com/gabfl/bigquery_fdw GitHub]
|
|[https://github.com/gabfl/bigquery_fdw/blob/master/docs/README.md Documentation]
|bigquery_fdw is a BigQuery FDW compatible with PostgreSQL >= 9.5
|-
| file_fdw-gds (Hadoop)
| Native
|
| [https://github.com/wat4dog/pg-file-fdw-gds GitHub]
|
|
| Hadoop file_fdw is a slightly modified version of PostgreSQL 9.3's file_fdw module.
|-
| Hadoop
| Native
| PostgreSQL
| [https://www.openscg.com/bigsql/hadoopfdw/ Bitbucket]
|
|
| Allows read and write access to HBase as well as to HDFS via Hive.
|-
| HDFS
| Native
| Apache
| [https://github.com/EnterpriseDB/hdfs_fdw GitHub]
|
|
|
|-
| Hive
| [https://multicorn.org/ Multicorn]
|
| [https://github.com/youngwookim/hive-fdw-for-postgresql GitHub]
|
|
| Used to access Apache Hive tables.
|-
| Hive / ORC File
| Native
|
| [https://github.com/gokhankici/orc_fdw GitHub]
|
|
|
|-
| [http://impala.apache.org/ Impala]
| Native
| BSD
| [https://github.com/lapug/impala_fdw GitHub]
|
|
|
|}

== Column-Oriented Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
|Columnar Store
|Native
|
|[https://github.com/citusdata/cstore_fdw github]
|[https://www.citusdata.com/blog/2014/04/03/columnar-store-for-analytics/ example]
|
|A Columnar Store for PostgreSQL.
|-
|[https://www.monetdb.org/ MonetDB]
|Native
|
|[https://github.com/snaga/monetdb_fdw github]
|
|
|
|-
|GPU Memory Store
|Native
|GPL v2
|[https://github.com/heterodb/pg-strom github]
|
|
|FDW to GPU device memory; a part of PG-Strom feature for PL/CUDA
|}

== Scientific Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
| Ambry
| [https://multicorn.org/ Multicorn]
|
| [https://github.com/nmb10/ambryfdw GitHub]
|
|
|
|-
| ROOT files
| Native
|
| [https://github.com/miguel-branco/root_fdw GitHub]
|
|
| https://root.cern.ch
|-
| VCF files (Genotype)
| [https://multicorn.org/ Multicorn]
|
| [https://github.com/smithijk/vcf_fdw_postgresql GitHub]
|
|
| https://en.wikipedia.org/wiki/Variant_Call_Format
|}

== Operating System Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
| Docker
| [https://multicorn.org/ Multicorn]
| Expat
| [https://github.com/paultag/dockerfdw GitHub]
|
|
|
|-
| Log files
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/rdunklau/logfdw GitHub]
|
|
|
|-
| OpenStack / Telemetry
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/CSCfi/telemetry-fdw GitHub]
|
|
|
|-
| OS Query
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/shish/pgosquery GitHub]
|
|
| Like Facebook's OSQuery, but for Postgres
|-
| Passwd
| Native
| PostgreSQL
| [https://github.com/beargiles/passwd-fdw GitHub]
|
|
| reads linux/unix password and group files.
|-
| Process
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/Kozea/Multicorn/blob/master/python/multicorn/processfdw.py GitHub]
|
|
| A foreign datawrapper for querying system stats based on [https://libstatgrab.org/ statgrab]
|}

== Exotic Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
| faker_fdw
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/guedes/faker_fdw GitHub]
|
|
| faker_fdw is a foreign data wrapper for PostgreSQL that generates fake data.
|-
| fdw_fdw
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/daamien/fdw_fdw GitHub]
|
|
| the Meta FDW ! reads this page and returns the list of all the FDW
|-
| PGStrom
| Native
| GPL 2
| [https://github.com/heterodb/pg-strom GitHub]
|
| [http://wiki.postgresql.org/wiki/PGStrom wiki]
| uses GPU devices to accelarate sequential scan on massive amount of records with complex qualifiers. Now it moved to CustomScan based implementation, so its core logic no longer uses FDW.
|-
| PPG
| Native
|
| [https://github.com/scarbrofair/ppg_fdw GitHub]
|
|
| distributed parallel query engine, based on fdw and hooks of PG
|-
| Open Civic Data
| [https://multicorn.org/ Multicorn]
| Expat
| [https://github.com/paultag/sunlightfdw GitHub]
|
|
|
|-
| [https://www2.meethue.com/en-us/philips-hue-benefits Phillips Hue Lighting Systems]
| [https://multicorn.org/ Multicorn]
| MIT
| [https://github.com/rotten/hue-multicorn-postgresql-fdw GitHub]
|
|
|
|-
| Random Number
| [https://multicorn.org/ Multicorn]
| PostgreSQL
| [https://github.com/yieldsfalsehood/rng_fdw GitHub]
|
|
| A random number generator foreign data wrapper for postgres
|-
| Rotfang
| [https://multicorn.org/ Multicorn]
| Native
| [https://bitbucket.org/adunstan/rotfang-fdw BitBucket]
| PostgreSQL
| [https://drive.google.com/file/d/0B3XVAFFWEFN0aURac0dzSFQyZzA/view slides]
| Advanced random number generator
|-
| Template Tables
| Native
| BSD
| [https://github.com/okbob/template_fdw GitHub]
|
|
| PostgreSQL data wrapper for template tables - any DML and SELECT operations are disallowed
|}

== Example Wrappers ==

{| align="center" border="1" cellspacing="0" {{Prettytable}}
|-
!{{Hl2}} |Data Source
!{{Hl2}} |Type
!{{Hl2}} |License
!{{Hl2}} |Code
!{{Hl2}} |Install
!{{Hl2}} |Doc
!{{Hl2}} |Notes
|-
| Dummy
| Native
| BSD
| [https://github.com/slaught/dummy_fdw GitHub]
|
|
| Readable null FDW for testing
|-
| Hello World
|
|
| [https://github.com/wikrsh/hello_fdw GitHub]
|
|
|
|-
| Black Hole
|
|
| [https://bitbucket.org/adunstan/blackhole_fdw bitbucket]
|
|
| a skeleton FDW pre-populated with relevant excerpts from the documentation
|}

=Writing Foreign Database Wrappers=

* [https://multicorn.org/ Multicorn] is an extension that allows you to write FDWs in Python
* [https://github.com/franckverrot/holycorn Holycorn] is an extension that allows you to write FDWs in Ruby
* [https://www.postgresql.org/docs/current/fdwhandler.html Documentation: Writing a Foreign Data Wrapper]
* [https://bitbucket.org/adunstan/blackhole_fdw Black Hole FDW] - a skeleton FDW pre-populated with relevant excerpts from the documentation
* [http://blog.guillaume.lelarge.info/index.php/post/2013/06/25/The-handler-and-the-validator-functions-of-a-FDW FDW tutorial by Guillaume Lelarge]
* [https://github.com/nautilebleu/django-fdw django-fdw] A sample project to test django and Postgres Foreign Data Wrapper

[[Category:Foreign-data wrapper|!]]

Don't Do This

2019-02-20T17:38:48Z

Dfetter:

A short list of common mistakes.

= Database Encoding =

== Don't use SQL_ASCII ==

=== Why not? ===

While the name suggests that this encoding is in some meaningful way related to ASCII, it is not. Instead, it simply forbids the use of NUL bytes.

=== When should you? ===

Never.

= Tool usage =

== Don't use psql -W or --password ==

Don't use <tt>psql -W</tt> or <tt>psql --password</tt>.

=== Why not? ===

Using the --password or -W flags will tell [https://www.postgresql.org/docs/current/static/reference-client.html psql] to prompt you for a password, before trying to connect to the server - so you'll be prompted for a password even if the server doesn't require one.

It's never required, as if the server does require a password psql will prompt you for one, and it can be very confusing when setting up permissions. If you're connecting with -W to a server configured to allow you access via <tt>peer</tt> authentication you may think that it's requiring a password when it really isn't. And if the user you're logging in as doesn't have a password set or you enter the wrong password at the prompt you'll still be logged in and think you have the right password - but you won't be able to log in from other clients (that connect via localhost) or when logged in as other users.

=== When should you? ===

Never, pretty much. It will save a round trip to the server but that's about it.

 
== Don't use rules ==

Don't use [https://www.postgresql.org/docs/current/static/sql-createrule.html rules]. If you think you want to, use a [https://www.postgresql.org/docs/current/static/plpgsql-trigger.html trigger] instead.

=== Why not? ===

Rules are incredibly powerful, but they don't do what they look like they do. They look like they're some conditional logic, but they actually rewrite a query to modify it or add additional queries to it.

That means that [http://blog.rhodiumtoad.org.uk/2010/06/21/the-rule-challenge/ all non-trivial rules are incorrect].

Depesz has [https://www.depesz.com/2010/06/15/to-rule-or-not-to-rule-that-is-the-question/ more to say] about them.

=== When should you? ===

Never. While the rewriter is an implementation detail of VIEWs, there is no reason to pry up this cover plate directly.



= SQL constructs =

== Don't use NOT IN ==

Don't use <code>NOT IN</code>, or any combination of <code>NOT</code> and <code>IN</code> such as <code>NOT (x IN (select…))</code>.

(If you think you wanted <code>NOT IN (select …)</code> then you should rewrite to use <code>NOT EXISTS</code> instead.)

=== Why not? ===

Two reasons:

1. <code>NOT IN</code> behaves in unexpected ways if there is a null present:

<code>select * from foo where col not in (1,null); -- always returns 0 rows</code>

<code>select * from foo where col not in (select x from bar);
-- returns 0 rows if any value of bar.x is null</code>

This happens because <code>col IN (1,null)</code> returns <code>TRUE</code> if col=1, and <code>NULL</code> otherwise (i.e. it can never return <code>FALSE</code>). Since <code>NOT (TRUE)</code> is <code>FALSE</code>, but <code>NOT (NULL)</code> is still <code>NULL</code>, there is no way that <code>NOT (col IN (1,null))</code> (which is the same thing as <code>col NOT IN (1,null)</code>) can return <code>TRUE</code> under any circumstances.

2. Because of point 1 above, <code>NOT IN (SELECT ...)</code> does not optimize very well. In particular, the planner can't transform it into an anti-join, and so it becomes either a hashed Subplan or a plain Subplan. The hashed subplan is fast, but the planner only allows that plan for small result sets; the plain subplan is '''horrifically''' slow (in fact O(N²)). This means that the performance can look good in small-scale tests but then slow down by 5 or more orders of magnitude once a size threshold is crossed; you '''do not''' want this to happen.

=== When should you? ===

<code>NOT IN (list,of,values,...)</code> is mostly safe ''unless'' you might have a null in the list (via a parameter or otherwise). So it's sometimes natural and even advisable to use it when excluding specific constant values from a query result.

 
== Don't use upper case table or column names ==

Don't use NamesLikeThis, use names_like_this.

=== Why not? ===

PostgreSQL folds all names - of tables, columns, functions and everything else - to lower case unless they're "double quoted".

So <tt>create table Foo()</tt> will create a table called <tt>foo</tt>, while <tt>create table "Bar"()</tt> will create a table called <tt>Bar</tt>.

These select commands will work: <tt>select * from Foo</tt>, <tt>select * from foo</tt>, <tt>select * from "Bar"</tt>.

These will fail with "no such table": <tt>select * from "Foo"</tt>, <tt>select * from Bar</tt>, <tt>select * from bar</tt>.

This means that if you use uppercase characters in your table or column names you have to either ''always'' double quote them or ''never'' double quote them. That's annoying enough by hand, but when you start using other tools to access the database, some of which always quote all names and some don't, it gets very confusing.

Stick to using a-z, 0-9 and underscore for names and you never have to worry about quoting them.

=== When should you? ===

If it's important that "pretty" names are displaying in report output then you might want to use them. But you can also use column aliases to use lower case names in a table and still get pretty names in the output of a query: <tt>select character_name as "Character Name" from foo</tt>.

 
== Don't use BETWEEN (especially with timestamps) ==

=== Why not? ===

<code>BETWEEN</code> uses a closed-interval comparison: the values of both ends of the specified range are included in the result.

This is a particular problem with queries of the form

<code>SELECT * FROM blah WHERE timestampcol BETWEEN '2018-06-01' AND '2018-06-08'</code>

This will include results where the timestamp is ''exactly'' 2018-06-08 00:00:00.000000, but not timestamps later in that same day. So the query might seem to work, but as soon as you get an entry exactly on midnight, you'll end up double-counting it.

Instead, do:

<code>SELECT * FROM blah WHERE timestampcol >= '2018-06-01' AND timestampcol < '2018-06-08'</code>

=== When should you? ===

<code>BETWEEN</code> is safe for discrete quantities like integers or dates, as long as you remember that both ends of the range are included in the result. But it's a bad habit to get into.



= Date/Time storage =

== Don't use timestamp (without time zone) ==

Don't use the <tt>timestamp</tt> type to store timestamps, use <tt>timestamptz</tt> (also known as <tt>timestamp with time zone</tt>) instead.

=== Why not? ===

<tt>timestamptz</tt> records a single moment in time. Despite what the name says it doesn't store a timestamp, just a point in time described as the number of microseconds since January 1st, 2000 in UTC. You can insert values in any timezone and it'll store the point in time that value describes. By default it will display times in your current timezone, but you can use <tt>at time zone</tt> to display it in other time zones.

Because it stores a point in time it will do the right thing with arithmetic involving timestamps entered in different timezones - including between timestamps from the same location on different sides of a daylight savings time change.

<tt>timestamp</tt> (also known as <tt>timestamp without time zone</tt>) doesn't do any of that, it just stores a date and time you give it. You can think of it being a picture of a calendar and a clock rather than a point in time. Without additional information - the timezone - you don't know what time it records. Because of that, arithmetic between timestamps from different locations or between timestamps from summer and winter may give the wrong answer.

So if what you want to store is a point in time, rather than a picture of a clock, use timestamptz.

[https://it.toolbox.com/blogs/josh-berkus/zone-of-misunderstanding-092811 More about timestamptz].

=== When should you? ===

If you're dealing with timestamps in an abstract way, or just saving and retrieving them from an app, where you aren't going to be doing arithmetic with them then timestamp might be suitable.

 
== Don't use timestamp (without time zone) to store UTC times ==

Storing UTC values in a <code>timestamp without time zone</code> column is, unfortunately, a practice commonly inherited from other databases that lack usable timezone support.

Use <code>timestamp with time zone</code> instead.

=== Why not? ===

Because there is no way for the database to know that UTC is the intended timezone for the column values.

This complicates many otherwise useful time calculations. For example, "last midnight in the timezone given by u.timezone" becomes this:

<code>date_trunc('day', now() AT TIME ZONE u.timezone) AT TIME ZONE u.timezone AT TIME ZONE 'UTC'</code>

And "the midnight prior to <code>x.datecol</code> in u.timezone" becomes this:

<code>date_trunc('day', x.datecol AT TIME ZONE 'UTC' AT TIME ZONE u.timezone)
AT TIME ZONE u.timezone AT TIME ZONE 'UTC'</code>

=== When should you? ===

If compatibility with non-timezone-supporting databases trumps all other considerations.

 
== Don't use timetz ==

Don't use the <tt>timetz</tt> type. You probably want <tt>timestamptz</tt> instead.

=== Why not? ===

Even the manual tells you it's only implemented for SQL compliance.

<blockquote>The type time with time zone is defined by the SQL standard, but the definition exhibits properties which lead to questionable usefulness. In most cases, a combination of date, time, timestamp without time zone, and timestamp with time zone should provide a complete range of date/time functionality required by any application.</blockquote>

=== When should you? ===

Never.

 
== Don't use CURRENT_TIME ==

Don't use the <code>CURRENT_TIME</code> function. Use whichever of these is appropriate:

* <code>CURRENT_TIMESTAMP</code> or <code>now()</code> if you want a <code>timestamp with time zone</code>,
* <code>LOCALTIMESTAMP</code> if you want a <code>timestamp without time zone</code>,
* <code>CURRENT_DATE</code> if you want a <code>date</code>,
* <code>LOCALTIME</code> if you want a <code>time</code>

=== Why not? ===

It returns a value of type <code>timetz</code>, for which see the previous entry.

=== When should you? ===

Never.

 
== Don't use timestamp(0) or timestamptz(0) ==

Don't use a precision specification, especially not 0, for timestamp columns or casts to timestamp.

Use <code>date_trunc('second', blah)</code> instead.

=== Why not? ===

Because it rounds off the fractional part rather than truncating it as everyone would expect. This can cause unexpected issues; consider that when you store <code>now()</code> into such a column, you might be storing a value half a second in the future.

=== When should you? ===

Never.



= Text storage =

== Don't use char(n) ==

Don't use the type <tt>char(n)</tt>. You probably want <tt>text</tt>.

=== Why not? ===

Any string you insert into a <code>char(n)</code> field will be padded with spaces to the declared width. That's probably not what you actually want.

The manual says:

<blockquote>Values of type character are physically padded with spaces to the specified width n, and are stored and displayed that way. However, trailing spaces are treated as semantically insignificant and disregarded when comparing two values of type character. In collations where whitespace is significant, this behavior can produce unexpected results; for example <code>SELECT 'a '::CHAR(2) collate "C" < E'a\n'::CHAR(2)</code> returns true, even though C locale would consider a space to be greater than a newline. Trailing spaces are removed when converting a character value to one of the other string types. Note that trailing spaces are semantically significant in character varying and text values, and when using pattern matching, that is LIKE and regular expressions.</blockquote>

That should scare you off it.

The space-padding does waste space, but doesn't make operations on it any faster; in fact the reverse, thanks to the need to strip spaces in many contexts.

It's important to note that from a storage point of view <code>char(n)</code> '''is not a fixed-width type'''. The actual number of bytes varies since characters may take more than one byte, and the stored values are therefore treated as variable-length anyway (even though the space padding is included in the storage).

=== When should you? ===

When you're porting very, very old software that uses fixed width fields. Or when you read the snippet from the manual above and think "yes, that makes perfect sense and is a good match for my requirements" rather than gibbering and running away.

 
== Don't use char(n) even for fixed-length identifiers ==

Sometimes people respond to "don't use <code>char(n)</code>" with "but my values must always be exactly N characters long" (e.g. country codes, hashes, or identifiers from some other system). '''It is still a bad idea to use <code>char(n)</code> even in these cases.'''

Use <code>text</code>, or a domain over text, with <code>CHECK(length(VALUE)=3)</code> or <code><nowiki>CHECK(VALUE ~ '^[[:alpha:]]{3}$')</nowiki></code> or similar.

=== Why not? ===

Because <code>char(n)</code> doesn't reject values that are too short, it just silently pads them with spaces. So there's no actual benefit over using <code>text</code> with a constraint that checks for the exact length. As a bonus, such a check can also verify that the value is in the correct format.

Remember, '''there is no performance benefit whatsoever to using <code>char(n)</code> over <code>varchar(n)</code>.''' In fact the reverse is true. One particular problem that comes up is that if you try and compare a <code>char(n)</code> field against a parameter where the driver has explicitly specified a type of <code>text</code> or <code>varchar</code>, you may be unexpectedly unable to use an index for the comparison. This can be hard to debug since it doesn't show up on manual queries.

=== When should you? ===

Never.

 

== Don't use varchar(n) by default ==

Don't use the type <tt>varchar(n)</tt> by default. Consider <tt>varchar</tt> (without the length limit) or <tt>text</tt> instead.

=== Why not? ===

<tt>varchar(n)</tt> is a variable width text field that will throw an error if you try and insert a string longer than n characters (not bytes) into it.

<tt>varchar</tt> (without the <tt>(n)</tt>) or <tt>text</tt> are similar, but without the length limit. If you insert the same string into the three field types they will take up exactly the same amount of space, and you won't be able to measure any difference in performance.

If what you really need is a text field with an length limit then varchar(n) is great, but if you pick an arbitrary length and choose varchar(20) for a surname field you're risking production errors in the future when Hubert Blaine Wolfeschlegelsteinhausenbergerdorff signs up for your service.

Some databases don't have a type that can hold arbitrary long text, or if they do it's not as convenient or efficient or well-supported as varchar(n). Users from those databases will often use something like <tt>varchar(255)</tt> when what they really want is <tt>text</tt>.

If you need to constrain the value in a field you probably need something more specific than a maximum length - maybe a minimum length too, or a limited set of characters - and a [https://www.postgresql.org/docs/current/static/ddl-constraints.html#DDL-CONSTRAINTS-CHECK-CONSTRAINTS check constraint] can do all of those things as well as a maximum string length.

=== When should you? ===

When you want to, really. If what you want is a text field that will throw an error if you insert too long a string into it, and you don't want to use an explicit check constraint then varchar(n) is a perfectly good type. Just don't use it automatically without thinking about it.



= Other data types =

== Don't use money ==

The <tt>money</tt> data type isn't actually very good for storing monetary values. Numeric, or (rarely) integer may be better.

=== Why not? ===

[https://www.postgresql.org/message-id/flat/20130328092819.237c0106@imp#20130328092819.237c0106@imp lots of reasons.]

It's a fixed-point type, implemented as a machine int, so arithmetic with it is fast. But it doesn't handle fractions of a cent (or equivalents in other currencies), it's rounding behaviour is probably not what you want.

It doesn't store a currency with the value, rather assuming that all money columns contain the currency specified by the database's [https://www.postgresql.org/docs/current/static/runtime-config-client.html#GUC-LC-MONETARY lc_monetary] locale setting. If you change the lc_monetary setting for any reason, all money columns will contain the wrong value. That means that if you insert '$10.00' while lc_monetary is set to 'en_US.UTF-8' the value you retrieve may be '10,00 Lei' or '¥1,000' if lc_monetary is changed.

Storing a value as a numeric, possibly with the currency being used in an adjacent column, might be better.

=== When should you? ===

If you're only working in a single currency, aren't dealing with fractional cents and are only doing addition and subtraction then money might be the right thing.

Index Maintenance

2019-01-15T21:36:48Z

Dfetter: /* Index summary */

{{Languages}}

One day, you will probably need to cope with [http://www.postgresql.org/docs/current/static/routine-reindex.html routine reindexing] on your database, particularly if you don't use VACUUM aggressively enough. A particularly handy command in this area is [http://www.postgresql.org/docs/8.3/static/sql-cluster.html CLUSTER], which can help with other types of cleanup.

Avoid using [[VACUUM FULL]] in versions 8.4 and earlier.

== Index summary ==

Here's a sample query to pull the number of rows, indexes, and some info about those indexes for each table. Ditch the pg_size_pretty if you’re on an ancient (<= 8.2) version)

{{SnippetInfo|Index summary|lang=SQL|version=>=8.1|category=Performance}}
<source lang="sql">
SELECT
pg_class.relname,
pg_size_pretty(pg_class.reltuples::bigint) AS rows_in_bytes,
pg_class.reltuples AS num_rows,
count(indexname) AS number_of_indexes,
CASE WHEN x.is_unique = 1 THEN 'Y'
ELSE 'N'
END AS UNIQUE,
SUM(case WHEN number_of_columns = 1 THEN 1
ELSE 0
END) AS single_column,
SUM(case WHEN number_of_columns IS NULL THEN 0
WHEN number_of_columns = 1 THEN 0
ELSE 1
END) AS multi_column
FROM pg_namespace
LEFT OUTER JOIN pg_class ON pg_namespace.oid = pg_class.relnamespace
LEFT OUTER JOIN
(SELECT indrelid,
max(CAST(indisunique AS integer)) AS is_unique
FROM pg_index
GROUP BY indrelid) x
ON pg_class.oid = x.indrelid
LEFT OUTER JOIN
( SELECT c.relname AS ctablename, ipg.relname AS indexname, x.indnatts AS number_of_columns FROM pg_index x
JOIN pg_class c ON c.oid = x.indrelid
JOIN pg_class ipg ON ipg.oid = x.indexrelid )
AS foo
ON pg_class.relname = foo.ctablename
WHERE
pg_namespace.nspname='public'
AND pg_class.relkind = 'r'
GROUP BY pg_class.relname, pg_class.reltuples, x.is_unique
ORDER BY 2;
</source>

== Index size/usage statistics ==

Table & index sizes along which indexes are being scanned and how many tuples are fetched. See [[Disk Usage]] for another view that includes both table and index sizes.

{{SnippetInfo|Index statistics|lang=SQL|version=>=8.1|category=Performance}}
<source lang="sql">
SELECT
t.tablename,
indexname,
c.reltuples AS num_rows,
pg_size_pretty(pg_relation_size(quote_ident(t.tablename)::text)) AS table_size,
pg_size_pretty(pg_relation_size(quote_ident(indexrelname)::text)) AS index_size,
CASE WHEN indisunique THEN 'Y'
ELSE 'N'
END AS unique,
idx_scan AS number_of_scans,
idx_tup_read AS tuples_read,
idx_tup_fetch AS tuples_fetched
FROM pg_tables t
LEFT OUTER JOIN pg_class c ON t.tablename=c.relname
LEFT OUTER JOIN
( SELECT c.relname as ctablename, ipg.relname as indexname, x.indnatts as number_of_columns, idx_scan, idx_tup_read, idx_tup_fetch, indexrelname, indisunique FROM pg_index x
JOIN pg_class c ON c.oid = x.indrelid
JOIN pg_class ipg ON ipg.oid = x.indexrelid
JOIN pg_stat_all_indexes psai ON x.indexrelid = psai.indexrelid AND psai.schemaname = 'public' )
as foo
ON t.tablename = foo.ctablename
WHERE t.schemaname='public'
order by 1,2;
</source>

== Duplicate indexes ==
Finds multiple indexes that have the same set of columns, same opclass, expression and predicate -- which make them equivalent. '''Usually''' it's safe to drop one of them, but I give no guarantees. :)

<source lang="sql">
SELECT pg_size_pretty(sum(pg_relation_size(idx))::bigint) as size,
(array_agg(idx))[1] as idx1, (array_agg(idx))[2] as idx2,
(array_agg(idx))[3] as idx3, (array_agg(idx))[4] as idx4
FROM (
SELECT indexrelid::regclass as idx, (indrelid::text ||E'\n'|| indclass::text ||E'\n'|| indkey::text ||E'\n'||
coalesce(indexprs::text,'')||E'\n' || coalesce(indpred::text,'')) as key
FROM pg_index) sub
GROUP BY key HAVING count(*)>1
ORDER BY sum(pg_relation_size(idx)) DESC;
</source>

== Index Bloat ==

=== Based on check_postgres ===

One of the common needs for a REINDEX is when indexes become bloated due to either sparse deletions or use of VACUUM FULL (with pre 9.0 versions). An estimator for the amount of bloat in a table has been included in the [http://bucardo.org/wiki/Check_postgres check_postgres] script, which you can call directly or incorporate into a larger monitoring system. Scripts based on this code and/or its concepts from other sources include:
* [https://web.archive.org/web/20080603000756/http://pgsql.tapoueh.org/site/html/news/20080131.bloat.html bloat view] (Dimitri Fontaine) - extracted from check_postgres
* [http://www.pgcon.org/2009/schedule/events/153.en.html Visualizing Postgres] - index_byte_sizes view (Michael Glaesemann, myYearbook)
* [http://labs.omniti.com/trac/pgtreats/browser/trunk/tools OmniTI Tasty Treats for PostgreSQL] - shell and Perl pg_bloat_report scripts

=== New query ===

A new query has been created to have a better bloat estimate for Btree indexes. Unlike the query from check_postgres, this one focus only on BTree index its disk layout.

See [http://blog.ioguix.net/tag/bloat/ articles] about it.

The monitoring script [https://github.com/OPMDG/check_pgactivity check_pgactivity] is including a check based on this work.

=== Summarize keyspace of a B-Tree index ===

{{SnippetInfo|Show database bloat|version=>=9.3|lang=SQL|depends=contrib/pageinspect|category=Performance}}

The following query uses contrib/pageinspect to summarize the keyspace of a B-Tree quickly. This can be useful to experts that wish to determine exactly how an index may have become unbalanced over time. It visualizes the keyspace of the index.

The query outputs the highkey for every page, starting from the root and working down, in logical/keyspace order.

If the query takes too long to execute, consider uncommenting "/* and level > 0 */" to make it only include internal pages.

See also: [https://pgeoghegan.blogspot.com/2017/07/postgresql-index-bloat-microscope.html "PostgreSQL index bloat under a microscope" blogpost]

Note: You are expected to change "pgbench_accounts_pkey" to the name of the index that is to be summarized.

<source lang="sql">
WITH RECURSIVE index_details AS (
SELECT
'pgbench_accounts_pkey'::text idx
),
size_in_pages_index AS (
SELECT
(pg_relation_size(idx::regclass) / (2^13))::int4 size_pages
FROM
index_details
),
page_stats AS (
SELECT
index_details.*,
stats.*
FROM
index_details,
size_in_pages_index,
lateral (SELECT i FROM generate_series(1, size_pages - 1) i) series,
lateral (SELECT * FROM bt_page_stats(idx, i)) stats
),
meta_stats AS (
SELECT
*
FROM
index_details s,
lateral (SELECT * FROM bt_metap(s.idx)) meta
),
pages_raw AS (
SELECT
*
FROM
page_stats
ORDER BY
btpo DESC
),
/* XXX: Note ordering dependency within this CTE */
pages_walk(item, blk, level) AS (
SELECT
1,
blkno,
btpo
FROM
pages_raw
WHERE
btpo_prev = 0
AND btpo = (SELECT level FROM meta_stats)
UNION
SELECT
CASE WHEN level = btpo THEN w.item + 1 ELSE 1 END,
blkno,
btpo
FROM
pages_raw i,
pages_walk w
WHERE
i.btpo_prev = w.blk OR (btpo_prev = 0 AND btpo = w.level - 1)
)
SELECT
/* Uncomment if these details interesting */
/*
idx,
btpo_prev,
btpo_next,
*/

/*
* "level" is level of tree -- 0 is leaf. First tuple returned is root.
*/
btpo AS level,

/*
* Ordinal number of item on this level
*/
item AS l_item,

/*
* Block number, and details of page
*/
blkno,
btpo_flags,
TYPE,
live_items,
dead_items,
avg_item_size,
page_size,
free_size,

/*
* distinct_real_item_keys is how many distinct "data" fields on page
* (excludes highkey).
*
* If this is less than distinct_block_pointers on an internal page, that
* means that there are so many duplicates in its children that there are
* duplicate high keys in children, so the index is probably pretty bloated.
*
* Even unique indexes can have duplicates. It's sometimes interesting to
* watch out for how many distinct real items there are within leaf pages,
* compared to the number of live items, or total number of items. Ideally,
* these will all be exactly the same for unique indexes.
*/
distinct_real_item_keys,

/*
* Per pageinspect docs, first item on non-rightmost page on level is "high
* key" item, which represents an upper bound on items on the page.
* (Rightmost pages are sometimes considered to have a conceptual "positive
* infinity" item, and are shown to have a high key that's NULL by this query)
*
* This can be used to visualize how finely or coarsely separated the
* keyspace is.
*
* Note that below int4_from_page_data() function could produce more useful
* visualization of split points.
*/
CASE WHEN btpo_next != 0 THEN first_item END AS highkey,

/*
* distinct_block_pointers is table blocks that are pointed to by items on
* the page (not including high key, which doesn't point anywhere).
*
* This is interesting on leaf pages, because it indicates how fragmented the
* index is with respect to table accesses, which is important for range
* queries.
*
* This should be redundant on internal levels, because all downlinks in internal
* pages point to distinct blocks in level below.
*/
distinct_block_pointers

FROM
pages_walk w,
pages_raw i,
lateral (
SELECT
count(distinct (case when btpo_next = 0 or itemoffset > 1 then (data collate "C") end)) as distinct_real_item_keys,
count(distinct (case when btpo_next = 0 or itemoffset > 1 then (ctid::text::point)[0]::bigint end)) as distinct_block_pointers,
(array_agg(data))[1] as first_item
FROM bt_page_items(idx, blkno)
) items
where w.blk = i.blkno
/* Uncomment to avoid showing leaf level (faster): */
/* and level > 0*/
ORDER BY btpo DESC, item;
</source>

=== Interpreting bt_page_items() "data" field as a little-endian int4 attribute ===

{{SnippetInfo|Show database bloat|version=>=9.2|lang=SQL|depends=contrib/pageinspect|category=Performance}}

The following convenience functions can be used to display the "data" field in bt_page_items() as their native type, at least for indexes whose pg_attribute entries consist of a single int4/integer attribute. This includes SERIAL primary key indexes. It can be used to make the above "Summarize keyspace of a B-Tree index" query display the keyspace split points using native type representation.

Note: The byteswap is only necessary on little-endian (Intel) CPUs.

<source lang="sql">
--
-- Sources:
--
-- https://stackoverflow.com/questions/17208945/whats-the-easiest-way-to-represent-a-bytea-as-a-single-integer-in-postgresql
-- https://stackoverflow.com/questions/11142235/convert-bigint-to-bytea-but-swap-the-byte-order
--
create or replace function reverse_bytes_iter(bytes bytea, length int, midpoint int, index int)
returns bytea as
$$
select case when index >= midpoint then bytes else
reverse_bytes_iter(
set_byte(
set_byte(bytes, index, get_byte(bytes, length-index)),
length-index, get_byte(bytes, index)
),
length, midpoint, index + 1
)
end;
$$ language sql immutable strict;

create or replace function reverse_bytes(bytes bytea) returns bytea as
$$
select reverse_bytes_iter(bytes, octet_length(bytes)-1, octet_length(bytes)/2, 0)
$$
language sql immutable strict;

create or replace function int4_from_bytea(bytea) returns int4
as $$
select ('x' || right($1::text, 6))::bit(24)::int;
$$
language sql immutable strict;

create or replace function int4_from_page_data(text) returns int4
as $$
select int4_from_bytea(reverse_bytes(decode($1, 'hex')));
$$
language sql immutable strict;

--
-- Use:
--
-- postgres=# select *, int4_from_page_data(data) from bt_page_items('f', 1) limit 15;
-- itemoffset │ ctid │ itemlen │ nulls │ vars │ data │ int4_from_page_data
-- ────────────┼────────────┼─────────┼───────┼──────┼─────────────────────────┼─────────────────────
-- 1 │ (17698,69) │ 16 │ f │ f │ 5c 00 00 00 00 00 00 00 │ 92
-- 2 │ (0,1) │ 16 │ f │ f │ 01 00 00 00 00 00 00 00 │ 1
-- 3 │ (8849,126) │ 16 │ f │ f │ 01 00 00 00 00 00 00 00 │ 1
-- 4 │ (17699,25) │ 16 │ f │ f │ 01 00 00 00 00 00 00 00 │ 1
-- 5 │ (17699,26) │ 16 │ f │ f │ 01 00 00 00 00 00 00 00 │ 1
-- 6 │ (0,2) │ 16 │ f │ f │ 02 00 00 00 00 00 00 00 │ 2
-- 7 │ (8849,125) │ 16 │ f │ f │ 02 00 00 00 00 00 00 00 │ 2
-- 8 │ (17699,23) │ 16 │ f │ f │ 02 00 00 00 00 00 00 00 │ 2
-- 9 │ (17699,24) │ 16 │ f │ f │ 02 00 00 00 00 00 00 00 │ 2
-- 10 │ (0,3) │ 16 │ f │ f │ 03 00 00 00 00 00 00 00 │ 3
-- 11 │ (8849,124) │ 16 │ f │ f │ 03 00 00 00 00 00 00 00 │ 3
-- 12 │ (17699,21) │ 16 │ f │ f │ 03 00 00 00 00 00 00 00 │ 3
-- 13 │ (17699,22) │ 16 │ f │ f │ 03 00 00 00 00 00 00 00 │ 3
-- 14 │ (0,4) │ 16 │ f │ f │ 04 00 00 00 00 00 00 00 │ 4
-- 15 │ (8849,123) │ 16 │ f │ f │ 04 00 00 00 00 00 00 00 │ 4
-- (15 rows)
</source>

== Unused Indexes ==

Since indexes add significant overhead to any table change operation, they should be removed if they are not being used for either queries or constraint enforcement (such as making sure a value is unique). How to find such indexes:

* [http://www.xzilla.net/blog/2008/Jul/Index-pruning-techniques.html Index pruning techniques]
* [http://hype-free.blogspot.com/2008/09/finding-unused-indexes-in-postgresql.html Finding unused indexes]
* [http://it.toolbox.com/blogs/database-soup/finding-useless-indexes-28796 Finding useless indexes]
* [http://jmorano.moretrix.com/2014/02/postgresql-monitor-unused-indexes/ 'Monitor unused indexes' by Johnny Morano]

== References ==

* Index statistics queries from [http://www.baconandtech.com/2009/06/06/book-review-part-i-refactoring-sql-applications-with-bonus-queries/ "Refactoring SQL Applications" review]

[[Category:Administration]][[Category:Performance]]

Change management tools and techniques

2019-01-15T21:32:08Z

Dfetter: /* Schema management tools */

This page describes various tools and methodologies for conducting database changes and deploying them. It includes tools to manage schema changes (via patches, or by adding complete SQL files), sproc changes and data migrations.

== Schema management tools ==
* [https://gitlab.com/depesz/Versioning Versioning ] by Hubert "depesz" Lubaczewski [http://www.depesz.com/2010/08/22/versioning/ blog post]
* [https://github.com/theory/sqitch Sqitch] by David Wheeler [http://sqitch.org official website]
* [https://github.com/gilt/schema-evolution-manager Schema evolution manager (sem) ] by Gilt Groupe [https://speakerdeck.com/mbryzek/schema-evolutions-at-gilt-groupe PGDay NYC 2013 presentation]
* [https://github.com/perseas/Pyrseas Pyrseas]
* [https://dbsteward.io/ DBSteward]
* [https://github.com/yandex/pgmigrate PGmigrate]
* [https://github.com/djrobstep/migra migra: like diff but for PostgreSQL schemas] by djrobstep [https://migra.djrobstep.com docs]

== Functions deployment ==
* [https://github.com/trustly/fdiff fdiff] by Joel Jacobson [http://joelonsql.com/2013/04/24/secure-deployment-of-postgresql-functions/ blog post]
* [http://tech.valgog.com/2012/01/schema-based-versioning-and-deployment.html Schema-based API versioning] by Valentine Gogichashvili

== Presentations ==
* [https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ/edit?usp=sharing ALTER DATABASE ADD SANITY] by Alexey Klyukin
* [https://migra.djrobstep.com/your-migrations-are-bad-by-djrobstep-postgresopen2017.pdf Your database migrations are bad and you should feel bad] by djrobstep

IRC2RWNames

2019-01-10T01:34:09Z

Dfetter: /* List of IRC nicks with their respective real world names */

=== List of IRC nicks with their respective real world names ===

You can find many PostgreSQL users and developers chatting in [irc://irc.freenode.net/postgresql #postgresql on freenode]. Here's more information about some of the regulars there. '''Note:''' people are on the list below only when they want to be. Do not (re-)add anyone without their express permission.

{| border="1"
|-
!Nickname || Real Name
|-
|ads || Andreas Scherbaum
|-
|agliodbs, aglio2 (freenode), jberkus (oftc) || Josh Berkus
|-
|ahammond || Andrew Hammond
|-
|akretschmer || Andreas Kretschmer
|-
|alvherre || Alvaro Herrera
|-
|andres || Andres Freund
|-
|Assid || Satish Alwani
|-
|aurynn || Aurynn Shaw
|-
|beaud76 || Philippe Beaudoin
|-
|BlueAidan/BlueAidan_work || [[user:davidblewett | David Blewett]]
|-
|bmomjian || Bruce Momjian
|-
|cbbrowne || Christopher Browne
|-
|cce || Clark C. Evans
|-
|cclavadetscher || Charles Clavadetscher
|-
|chicagoben || Benjamin Johnson
|-
|crab || Abhijit Menon-Sen
|-
|Crad || Gavin M. Roy
|-
|daamien || Damien Clochard
|-
|DarcyB || Darcy Buskermolen
|-
|darkixion || Thom Brown
|-
|davidfetter || David Fetter
|-
|dbb || Brian M Hamlin / darkblue_b
|-
|dcolish || [http://www.unencrypted.org Dan Colish]
|-
|dcramer || Dave Cramer
|-
|DeciBull, TheCougar || Jim C. Nasby
|-
|dennisb || Dennis Björklund
|-
|depesz || Hubert Lubaczewski
|-
|devrimgunduz || Devrim Gündüz
|-
|digicon || [http://digicondev.blogspot.com Zach Conrad]
|-
|digitalknight || Atri Sharma
|-
|dim || [http://tapoueh.org Dimitri Fontaine]
|-
|direvus || Brendan Jurd
|-
|drbair || Ryan Bair
|-
|DrLou || Lou Picciano
|-
|duck_tape || Adi Alurkar
|-
|dvl || [http://langille.org/ Dan Langille]
|-
|eggyknap || Joshua Tolley
|-
|endpoint_david || David Christensen
|-
|eulerto || Euler Taveira
|-
|f3ew/devdas || Devdas Vasu Bhagat
|-
|feivel || Michael Meskes
|-
|frost242 || Thomas Reiss
|-
|elein || Elein Mustain
|-
|Gibheer || Stefan Radomski
|-
|gleu || Guillaume Lelarge
|-
|gorthx || [[User:Gabrielle|Gabrielle Roth]]
|-
|grzm || Michael Glaesemann
|-
|gsmet || Guillaume Smet
|-
|gregs1104 || Greg Smith
|-
|gurjeet || [[User:singh.gurjeet|Gurjeet Singh]]
|-
|G_SabinoMullane || Greg Sabino Mullane
|-
|HarrisonF || Harrison Fisk
|-
|ioguix || Jehan-Guillaume de Rorthais
|-
|indigo || Phil Frost
|-
|intgr || Marti Raudsepp
|-
|iwantchips || [https://payalsingh.me Payal Singh]
|-
|JanniCash || Jan Wieck
|-
|jconway || Joe Conway
|-
|jdavis, jdavis_ || Jeff Davis
|-
|jkatz05 || Jonathan S. Katz
|-
|johto || Marko Tiikkaja
|-
|jurka || Kris Jurka
|-
|justatheory || David Wheeler
|-
|jpa || Jean-Paul Argudo
|-
|jwp || James Pye
|-
|j_williams || Josh Williams
|-
|kandreas || Andreas Karlson
|-
|keithf4 || [http://www.keithf4.com Keith Fiske]
|-
|kgrittn || Kevin Grittner
|-
|klando || [[User:c2main|Cédric Villemain]]
|-
|larryrtx || Larry Rosenman
|-
|linuxpoet, postgresman || Joshua D. Drake
|-
|lluad || Steve Atkins
|-
|lsmith || Lukas Smith
|-
|macdice || Thomas Munro
|-
|mage_ || Julien Cigar
|-
|magnush || Magnus Hagander
|-
|maiku41 || Mike Blackwell
|-
|marco44 || Marc Cousin
|-
|markwkm || Mark Wong
|-
|mastermind || [[user:mastermind | Stefan Kaltenbrunner]]
|-
|mbalmer || [[user:mbalmer | Marc Balmer]]
|-
|merlin83 || Chua Khee Chin
|-
|merlinm || Merlin Moncure
|-
|metatrontech || Chris Travers
|-
|miracee || Susanne Ebrecht
|-
|Moosbert || Peter Eisentraut
|-
|Myon || [[user:Myon | Christoph Berg]]
|-
|neilc || Neil Conway
|-
|oicu || Andrew Dunstan
|-
|okbobcz || Pavel Stehule
|-
|patryk || Patryk Kordylewski
|-
|pasha_golub || [http://pgolub.wordpress.com/ Pavel Golub]
|-
|pg_docbot || [[IRCBotSyntax]]
|-
|pgSnake || Dave Page
|-
|PJMODOS || Petr Jelínek
|-
|Possible || Robert Ivens
|-
|postwait || Theo Schlossnagle
|-
|prothid || R Brenton Strickler
|-
|psoo || Bernd Helmle
|-
|PSUdaemon || Phil Sorber
|-
|pyarra || Philip Yarra
|-
|raptelan || [[user:Cshobe|Casey Allen Shobe]]
|-
|RhodiumToad (formerly AndrewSN) || Andrew Gierth
|-
|rjuju || Julien Rouhaud
|-
|Robe || [[user:Robe | Michael Renner]]
|-
|rotellaro || Federico Campoli
|-
|russ960 || [[user:russ960|Russ Johnson]]
|-
|rz || Kirill Simonov
|-
|saper || Marcin Cieślak
|-
|SAS || Stéphane Schildknecht
|-
|schmiddy || Josh Kupershmidt
|-
|scrappy || Marc G. Fournier
|-
|sehrope || Sehrope Sarkuni
|-
|selenamarie || Selena Deckelmann
|-
|SkippyDigits || Sherri Kalm
|-
|Snow-Man || Stephen Frost
|-
|Spritz || Matteo Beccati
|-
|sternocera || Peter Geoghegan
|-
|StuckMojo, MojoWork || Jon Erdman
|-
|swm || Gavin Sherry
|-
|vy || Volkan YAZICI
|-
|wulczer || Jan Urbański
|-
|xaprb || Baron Schwartz
|-
|xocolatl, ififbetween || Vik Fearing
|-
|xzilla, xzi11a || [[User:Xzilla|Robert Treat]]
|}

[[Category:Community]]

Apt/FAQ

2018-09-07T22:47:40Z

Dfetter: /* Development snapshots */

==apt.postgresql.org FAQ==

==General Questions==

===What's the difference between the PostgreSQL packages provided by Debian/Ubuntu and by the PGDG apt repository?===

Pretty little, actually. The PGDG packages are built from the same source as the Debian packages (Ubuntu is using the same source for the PostgreSQL server packages as well).
We try to follow Debian unstable's versions as close as possible, i.e. the packages available here are the same, just rebuilt with a ".pgdg" appended to the version number.
We are also using the same postgresql-common infrastructure packages.

===Should I use Debian/Ubuntu's packages, or the PGDG packages?===

Debian and Ubuntu only ship one PostgreSQL server version per release. For example, there is only PostgreSQL 8.4 in Debian Squeeze/6.0. If that is the version you want, use it. There is no real difference.
If you want a different PostgreSQL server version, use the PGDG packages.

Same goes for extension module packages, except that we are updating to new upstream versions earlier (following Debian unstable), while Debian/Ubuntu will only accept patches for critical problems in a released distribution.

===What about Debian backports?===

[[http://backports.debian.org Debian backports]] provide newer package versions for released distributions, similar to what the PGDG apt repository does.
The scope of the backports archive is strictly limited to testing -> stable, and stable -> oldstable backports, though.
The PGDG apt repository provides a broader range of available packages, and Debian version/PostgreSQL version combinations than what would be possible to provide on backports.

Similar to the previous FAQ question, if the package you want is available on backports, there is nothing wrong with using it.

===Are these packages ready for production?===

As said above, these packages are identical to what Debian/Ubuntu are releasing. So yes, these packages are recommended for production use.

===What's pgapt.debian.net?===

pgapt.debian.net was the old location of this repository, which was shut down in January 2013.

==Technical Questions==

===How do I dist-upgrade?===

Just update your sources.list entries, and use your favorite package tool.

When compiling packages for several distributions, we append different suffixes to the package version numbers to make sure, upgrades work. Debian Squeeze packages have ".pgdg60+1" appended, Wheezy packages ".pgdg70+1" and so on; likewise ".pgdg12.4+1" for Ubuntu Precise. (Sid packages have ".pgdg+1", which sorts after all the others in Debian's version number scheme.) This makes sure packages from the old distribution you used will be properly replaced by packages from the new distribution when you do a dist-upgrade.

===Where is the "stable" distribution?===

We prefer to only use codenames (squeeze, precise, ...) for distribution names. We run a different repository from Debian, so we would never be able to update the stable/oldstable/testing symlinks at the very same time when a new Debian release comes out, and there would be a time window where users would be seeing an inconsistencies. (Also, it is usually better to use codenames in sources.list even for Debian distributions, because then the user decides when it is time for upgrade.)

===I am using a non-LTS release of Ubuntu===

Non-LTS releases of Ubuntu are only added to the repository if the packages from the latest LTS release are incompatible with the release in question.
Using the latest LTS release instead generally works, unless library dependencies cannot be fulfilled, in which case we will provide updated packages for the non-LTS release.

===I want only specific packages from this repository===

Per default, the PGDG repository will have the same "pinning" priority as your Debian/Ubuntu repositories. This means your existing PostgreSQL packages will be replaced with versions from this repository, because they have greater version numbers. If you do not want this, you need to configure pinning (see apt_preferences(5) for details).

Create the file '''/etc/apt/preferences.d/pgdg.pref''':

Package: *
Pin: release o=apt.postgresql.org
Pin-Priority: 200

The default priority for repositories is 500, so 200 will lower the PGDG repository priority enough such you don't get packages automatically installed from there, but once you have packages installed, they will keep getting upgraded to newer versions from the PGDG repository.

You can check your setup using the '''apt-cache policy''' command to see if "200" shows up in the output:

$ apt-cache policy postgresql-9.1
postgresql-9.1:
Installed: 9.1.8-1.pgdg70+1
Candidate: 9.1.8-1.pgdg70+1
Version table:
*** 9.1.8-1.pgdg70+1 0
'''200''' <nowiki>http://apt.postgresql.org/pub/repos/apt/</nowiki> wheezy-pgdg/main amd64 Packages
100 /var/lib/dpkg/status
9.1.8-1 0
500 <nowiki>http://ftp.debian.org/debian/</nowiki> wheezy/main amd64 Packages

===I want libpq5 for version X, but there is only version Y in the repository===

libpq5 is compatible with older versions, so there is usually little reason to use a specific version. (psql requires at least the version corresponding to its own version, most other software does not really care.) For that reason, we ship the libpq5 package built from the latest stable PostgreSQL server version in the ''main'' archive component.

If you really want to use a different version, the packages are available in separate archive components named after the PostgreSQL major version. Append that version after "main" in your sources.list. For example, if you wanted 9.0's libpq5 on Debian Squeeze, use this:

deb <nowiki>http://apt.postgresql.org/pub/repos/apt/</nowiki> squeeze-pgdg main '''9.0'''

Note that the other libpq5 package will still be visible in the "main" component, so you will need to configure pinning or set that package on hold to prevent apt from trying to upgrade to the newer version.

===I want to try the beta version of the next PostgreSQL release===

'''WARNING''': The data format may change between beta releases. Be prepared to ''pg_dump'' the database contents before you upgrade the package to a newer beta or to a final release. Check the release notes before upgrading.

We ship packages for beta and RC releases, but like in the previous FAQ entry, you need to add the '''11''' component to your <code>/etc/apt/sources.list.d/pgdg.list</code> entry, so the version 11 packages will be available for installation:

deb <nowiki>http://apt.postgresql.org/pub/repos/apt/</nowiki> stretch-pgdg main '''11'''

===Development snapshots===

'''WARNING''': Development snapshots are meant for testing purposes only, and the catalog version will change frequently. Don't store any data you cannot afford to lose.

Development snapshots of '''postgresql-11''' are being built every 6 hours, directly from git. The packages are available for '''amd64 only''', for the following distributions:
'''sid-pgdg-testing''', '''stretch-pgdg-testing''', '''jessie-pgdg-testing''', '''xenial-pgdg-testing''', and '''trusty-pgdg-testing'''. You need to add a sources.list entry including the '''11''' component, e.g. for xenial:

deb <nowiki>http://apt.postgresql.org/pub/repos/apt/</nowiki> '''xenial-pgdg-testing''' main '''11'''

or, slightly more generally:

sudo add-apt-repository "deb <nowiki>https://apt.postgresql.org/pub/repos/apt/</nowiki> $(lsb_release -s -c)-pgdg-testing main 11"

===After updating from an alpha or beta release I get an error about CATALOG_VERSION===

After upgrading from an alpha or beta package, I get an error like:

The database cluster was initialized with CATALOG_VERSION_NO X, but the server was compiled with CATALOG_VERSION_NO Y.

This is because the PostgreSQL data format can change between alpha releases - and occasionally even between beta releases if there's a really pressing need.

If you need to access the old data, you will need to use the package version you were running before, and use ''pg_dump'' or ''pg_upgrade''.
The necessary binaries should have been saved in /var/tmp/postgresql*.
Alternatively, look for the old packages in your ''/var/cache/apt/archives''.

===What are the testing distributions?===

We have distributions squeeze-pgdg-testing, precise-pgdg-testing, sid-pgdg-testing, ... which receive all updates before they are promoted to the "live" distributions. These are not meant for production use, but you are welcome to use them and help debugging and testing the packages. Please join the mailing list or the IRC channel. The distributions have a lower apt priority by default, you will have to set up pinning (e.g. with priority 500) if you want them to be used automatically.

===Can I mirror the repository?===

For a full mirror of some or all distributions, we suggest to use ''debmirror''. For mirroring just a subset of packages, ''reprepro'' offers the ability to "pull" packages from remote repositories.

===Where are older versions of the packages?===

The *-pgdg distributions only contain the most recent version of each package. Older versions are available in the morgue at
http://atalia.postgresql.org/morgue/.

(There is no dists/ structure, and the provided Packages.xz and Sources.xz files contain all packages for all distributions, users will need to choose the correct files manually.)

===GPG error: invalid signatures===

If you are getting errors from ''apt-get update'' like:

W: A error occurred during the signature verification. The repository is not
updated and the previous index files will be used. GPG error:
http://apt.postgresql.org squeeze-pgdg Release: The following signatures were invalid: KEYEXPIRED 1381654177

... you have an outdated copy of the repository key. In most cases '''rm /etc/apt/trusted.gpg.d/apt.postgresql.org.gpg''' will fix it by removing the ''second'' copy of the key.
Use '''apt-key list''' to check.

===systemd integration===

The postgresql-common package contains systemd service files that handle starting/stopping/reloading the installed clusters.

Unfortunately, the systemd version shipped with wheezy is incompatible with the "reload" part of the service files.
Upgrade to the systemd version in wheezy-backports to fix.
(Users of jessie and newer Debian and Ubuntu versions are not affected, the systemd version there is recent enough.)

Apt/FAQ

2018-09-07T22:00:19Z

Dfetter: /* Development snapshots */

==apt.postgresql.org FAQ==

==General Questions==

===What's the difference between the PostgreSQL packages provided by Debian/Ubuntu and by the PGDG apt repository?===

Pretty little, actually. The PGDG packages are built from the same source as the Debian packages (Ubuntu is using the same source for the PostgreSQL server packages as well).
We try to follow Debian unstable's versions as close as possible, i.e. the packages available here are the same, just rebuilt with a ".pgdg" appended to the version number.
We are also using the same postgresql-common infrastructure packages.

===Should I use Debian/Ubuntu's packages, or the PGDG packages?===

Debian and Ubuntu only ship one PostgreSQL server version per release. For example, there is only PostgreSQL 8.4 in Debian Squeeze/6.0. If that is the version you want, use it. There is no real difference.
If you want a different PostgreSQL server version, use the PGDG packages.

Same goes for extension module packages, except that we are updating to new upstream versions earlier (following Debian unstable), while Debian/Ubuntu will only accept patches for critical problems in a released distribution.

===What about Debian backports?===

[[http://backports.debian.org Debian backports]] provide newer package versions for released distributions, similar to what the PGDG apt repository does.
The scope of the backports archive is strictly limited to testing -> stable, and stable -> oldstable backports, though.
The PGDG apt repository provides a broader range of available packages, and Debian version/PostgreSQL version combinations than what would be possible to provide on backports.

Similar to the previous FAQ question, if the package you want is available on backports, there is nothing wrong with using it.

===Are these packages ready for production?===

As said above, these packages are identical to what Debian/Ubuntu are releasing. So yes, these packages are recommended for production use.

===What's pgapt.debian.net?===

pgapt.debian.net was the old location of this repository, which was shut down in January 2013.

==Technical Questions==

===How do I dist-upgrade?===

Just update your sources.list entries, and use your favorite package tool.

When compiling packages for several distributions, we append different suffixes to the package version numbers to make sure, upgrades work. Debian Squeeze packages have ".pgdg60+1" appended, Wheezy packages ".pgdg70+1" and so on; likewise ".pgdg12.4+1" for Ubuntu Precise. (Sid packages have ".pgdg+1", which sorts after all the others in Debian's version number scheme.) This makes sure packages from the old distribution you used will be properly replaced by packages from the new distribution when you do a dist-upgrade.

===Where is the "stable" distribution?===

We prefer to only use codenames (squeeze, precise, ...) for distribution names. We run a different repository from Debian, so we would never be able to update the stable/oldstable/testing symlinks at the very same time when a new Debian release comes out, and there would be a time window where users would be seeing an inconsistencies. (Also, it is usually better to use codenames in sources.list even for Debian distributions, because then the user decides when it is time for upgrade.)

===I am using a non-LTS release of Ubuntu===

Non-LTS releases of Ubuntu are only added to the repository if the packages from the latest LTS release are incompatible with the release in question.
Using the latest LTS release instead generally works, unless library dependencies cannot be fulfilled, in which case we will provide updated packages for the non-LTS release.

===I want only specific packages from this repository===

Per default, the PGDG repository will have the same "pinning" priority as your Debian/Ubuntu repositories. This means your existing PostgreSQL packages will be replaced with versions from this repository, because they have greater version numbers. If you do not want this, you need to configure pinning (see apt_preferences(5) for details).

Create the file '''/etc/apt/preferences.d/pgdg.pref''':

Package: *
Pin: release o=apt.postgresql.org
Pin-Priority: 200

The default priority for repositories is 500, so 200 will lower the PGDG repository priority enough such you don't get packages automatically installed from there, but once you have packages installed, they will keep getting upgraded to newer versions from the PGDG repository.

You can check your setup using the '''apt-cache policy''' command to see if "200" shows up in the output:

$ apt-cache policy postgresql-9.1
postgresql-9.1:
Installed: 9.1.8-1.pgdg70+1
Candidate: 9.1.8-1.pgdg70+1
Version table:
*** 9.1.8-1.pgdg70+1 0
'''200''' <nowiki>http://apt.postgresql.org/pub/repos/apt/</nowiki> wheezy-pgdg/main amd64 Packages
100 /var/lib/dpkg/status
9.1.8-1 0
500 <nowiki>http://ftp.debian.org/debian/</nowiki> wheezy/main amd64 Packages

===I want libpq5 for version X, but there is only version Y in the repository===

libpq5 is compatible with older versions, so there is usually little reason to use a specific version. (psql requires at least the version corresponding to its own version, most other software does not really care.) For that reason, we ship the libpq5 package built from the latest stable PostgreSQL server version in the ''main'' archive component.

If you really want to use a different version, the packages are available in separate archive components named after the PostgreSQL major version. Append that version after "main" in your sources.list. For example, if you wanted 9.0's libpq5 on Debian Squeeze, use this:

deb <nowiki>http://apt.postgresql.org/pub/repos/apt/</nowiki> squeeze-pgdg main '''9.0'''

Note that the other libpq5 package will still be visible in the "main" component, so you will need to configure pinning or set that package on hold to prevent apt from trying to upgrade to the newer version.

===I want to try the beta version of the next PostgreSQL release===

'''WARNING''': The data format may change between beta releases. Be prepared to ''pg_dump'' the database contents before you upgrade the package to a newer beta or to a final release. Check the release notes before upgrading.

We ship packages for beta and RC releases, but like in the previous FAQ entry, you need to add the '''11''' component to your <code>/etc/apt/sources.list.d/pgdg.list</code> entry, so the version 11 packages will be available for installation:

deb <nowiki>http://apt.postgresql.org/pub/repos/apt/</nowiki> stretch-pgdg main '''11'''

===Development snapshots===

'''WARNING''': Development snapshots are meant for testing purposes only, and the catalog version will change frequently. Don't store any data you cannot afford to lose.

Development snapshots of '''postgresql-11''' are being built every 6 hours, directly from git. The packages are available for '''amd64 only''', for the following distributions:
'''sid-pgdg-testing''', '''stretch-pgdg-testing''', '''jessie-pgdg-testing''', '''xenial-pgdg-testing''', and '''trusty-pgdg-testing'''. You need to add a sources.list entry including the '''11''' component, e.g. for xenial:

deb <nowiki>http://apt.postgresql.org/pub/repos/apt/</nowiki> '''xenial-pgdg-testing''' main '''11'''

or, slightly more generally:

sudo add-apt-repository "deb <nowiki>https://apt.postgresql.org/repos/apt/</nowiki> $(lsb_release -s -c)-pgdg-testing main 11"

===After updating from an alpha or beta release I get an error about CATALOG_VERSION===

After upgrading from an alpha or beta package, I get an error like:

The database cluster was initialized with CATALOG_VERSION_NO X, but the server was compiled with CATALOG_VERSION_NO Y.

This is because the PostgreSQL data format can change between alpha releases - and occasionally even between beta releases if there's a really pressing need.

If you need to access the old data, you will need to use the package version you were running before, and use ''pg_dump'' or ''pg_upgrade''.
The necessary binaries should have been saved in /var/tmp/postgresql*.
Alternatively, look for the old packages in your ''/var/cache/apt/archives''.

===What are the testing distributions?===

We have distributions squeeze-pgdg-testing, precise-pgdg-testing, sid-pgdg-testing, ... which receive all updates before they are promoted to the "live" distributions. These are not meant for production use, but you are welcome to use them and help debugging and testing the packages. Please join the mailing list or the IRC channel. The distributions have a lower apt priority by default, you will have to set up pinning (e.g. with priority 500) if you want them to be used automatically.

===Can I mirror the repository?===

For a full mirror of some or all distributions, we suggest to use ''debmirror''. For mirroring just a subset of packages, ''reprepro'' offers the ability to "pull" packages from remote repositories.

===Where are older versions of the packages?===

The *-pgdg distributions only contain the most recent version of each package. Older versions are available in the morgue at
http://atalia.postgresql.org/morgue/.

(There is no dists/ structure, and the provided Packages.xz and Sources.xz files contain all packages for all distributions, users will need to choose the correct files manually.)

===GPG error: invalid signatures===

If you are getting errors from ''apt-get update'' like:

W: A error occurred during the signature verification. The repository is not
updated and the previous index files will be used. GPG error:
http://apt.postgresql.org squeeze-pgdg Release: The following signatures were invalid: KEYEXPIRED 1381654177

... you have an outdated copy of the repository key. In most cases '''rm /etc/apt/trusted.gpg.d/apt.postgresql.org.gpg''' will fix it by removing the ''second'' copy of the key.
Use '''apt-key list''' to check.

===systemd integration===

The postgresql-common package contains systemd service files that handle starting/stopping/reloading the installed clusters.

Unfortunately, the systemd version shipped with wheezy is incompatible with the "reload" part of the service files.
Upgrade to the systemd version in wheezy-backports to fix.
(Users of jessie and newer Debian and Ubuntu versions are not affected, the systemd version there is recent enough.)

Binary Replication Tools

2018-08-22T20:26:12Z

Dfetter:

= Disclaimer =

This is a Work-In-Progress, started Dec 28, 2012.

Additions welcome, and [[User:Selena|Selena]] reserves the right to edit. :)

= Purpose =

Compare binary replication tools for PostgreSQL for features and ease of use. This document should classify and differentiate binary replication tools for easier selection and fit to purpose.

== Comparison Matrix ==

{|border=1
!Tool!!Documentation!!License!!Makes base backups!!Makes base backups from replicas!!Manages backups!!Creates replicas!!Monitors replication delay!!Supports automated failover!!Transport used!!Source includes replication tests
|- style="background-color:#ffffcc;"
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html pg_basebackup]*
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html Postgres docs]
| PostgreSQL
| Yes
| Yes
| No
| Manual
| No
| No
| PostgreSQL connection
|
|-
| [http://www.pgbackrest.org/ pgBackRest]
| [http://www.pgbackrest.org/user-guide.html Documentation]
| MIT
| Yes
| Yes
| Yes
| Manual
| No
| No
| ssh
| Yes
|-
| [http://www.pgbarman.org/ pgbarman]
| [http://docs.pgbarman.org/ Documentation]
| GPLv3
| Yes
| Yes
| Yes
| Manual
| Yes
| No
| rsync/ssh, pg_basebackup
|
|-
| [https://github.com/omniti-labs/omnipitr OmniPITR]
| [https://github.com/omniti-labs/omnipitr/blob/master/doc/intro.pod Intro]
| PostgreSQL
| Yes
| Yes
| No
| Manual
| WAL archive delay
| No
| rsync / ssh
|
|-
| [https://github.com/ohmu/pghoard pghoard]
| [https://github.com/ohmu/pghoard/blob/master/README.rst Readme]
| Apache
| Yes
| Yes
| Yes
| Yes
| No
| No
| AWS S3, Azure, Ceph, Google Cloud Storage
| Yes
|-
| [http://code.google.com/p/pg-rman/ pg-rman]
| [http://code.google.com/p/pg-rman/wiki/readme Readme]
| BSD
| Yes
| Yes
| Yes
| Manual
| No
| No
| local / NFS mount
|
|-
| [http://www.repmgr.org/ repmgr]
| [https://github.com/2ndQuadrant/repmgr#readme Readme]
| GPLv3
| No
| No
| No
| Yes
| Yes
| Yes
| rsync / ssh
|
|-
| [https://github.com/markokr/skytools Skytools]
| [https://github.com/markokr/skytools/blob/master/doc/walmgr3.txt walmgr3]
| BSD-ish
| ?
| ?
| ?
| Manual
| Yes
| Yes
| ?
| ?
|-
| [https://github.com/wal-e/WAL-E WAL-E]
| [https://github.com/wal-e/WAL-E#readme Readme]
| BSD
| Yes
| No
| Yes
| Manual
| No
| No
| HTTPS/SSL
|
|-
| [https://github.com/wal-g/wal-g WAL-G]
| [https://github.com/wal-g/wal-g/blob/master/README.md README]
| Apache 2.0
| Yes
| Yes
| No
| Manual
| Yes
| No
| HTTPS/SSL
| Yes
|}

* pg_basebackup is included with a standard PostgreSQL installation.

'''Tool''': name of the project that manages binary replication or WAL archiving

'''Documentation''': Link to canonical documentation for the project. Several projects have broken links that show up as top results in Google.

'''License''': License software is released under. So far, we only have open/free software projects listed. We could add commercial projects.

'''Makes base backups''': Yes if the project supports creating binary archives, including the necessary WAL to restore a backed-up instance.

'''Makes base backups from replicas''': Yes if the project supports creating binary archives and WAL using the PGDATA directory from a replica rather than the master database.

'''Manages backups''': Yes if the project adds, removes and lists binary archives.

'''Creates replicas''': Yes if the project automatically adds a recovery.conf (sets up replication) as part of restoring a base backup.

'''Monitors replication delay''': Yes if the project supports monitoring of replication delay (WAL shipping or streaming replication).

'''Supports automated failover''': Yes if the project has an option for detecting master failure and promoting a replica to master.

'''Transport used''': Supported methods for file transfer for making backups or replicas

= Barman =

[http://www.pgbarman.org/ pgbarman] [https://github.com/selenamarie/pg_replication_demo/tree/master/barman Demo setup for pgbarman]

Summary of features:
* Creates base backups
* Uses SSH as transport for backup
* Configuration stored in file or command-line
* Restore is automatable for creating replicas, although not explictly supported
* GPLv3

Install notes:
* Had a dependency problem with 9.1 on Ubuntu Precise, so installed from source
* Missing dep for argcomplete, noted in README in demo repo
* written in Python

= OmniPITR =

[https://github.com/omniti-labs/omnipitr OmniPITR]
[https://github.com/selenamarie/pg_replication_demo/tree/master/omnipitr Demo of a simple replication setup with OmniPITR]

Summary of Features:
* Creating PITR backups from Master or Slave
* Restoring a PITR backup for DR
* Creating replicas (by untarring backups)
* Monitoring of replicas
* Supports 'pause removal' of WAL during a backup (nice!)
* PostgreSQL license

Install notes:
* No packaging, perl
* No documented support for streaming replication
* Uses '^' instead of '%' in custom logfile naming
* No configuration file option (instead of using long command-line options)
* Supported on all Linux, Solaris variants

= pgBackRest =

[http://www.pgbackrest.org/ pgBackRest]

Summary of features:
* Parallel Backup & Restore
* Local or Remote Operation
* Full, Incremental, & Differential Backups
* Backup & Archive Expiration
* Backup Resume
* Streaming Compression & Checksums
* Delta Restore
* Parallel WAL Archiving
* Tablespace & Link Support
* Compatibility with PostgreSQL >= 8.3
* S3 Support

= pghoard =

https://github.com/ohmu/pghoard

Summary of features:
* Stores basebackups and WAL to cloud object stores (AWS S3, Azure, Ceph, Google Cloud)
* Restore existing basebackups and setup a new cluster with a recovery.conf pointing to another master database
* Create scheduled basebackups
* Can be used as archive_command to archive WALs in the object store
* Can be used as restore_command to restore WALs from the object store
* Basebackup and WAL compression using LZMA
* Optionally encrypts backups
* Supports PITR using timestamps, names and xids

Install notes:
* Written in Python, includes Debian and Fedora packaging scripts
* 'pghoard' daemon manages basebackups and cleans up WALs
* 'pghoard_archive_command' and 'pghoard_restore' access the locally running 'pghoard' daemon to store and restore files

= pg-rman =

[http://code.google.com/p/pg-rman/ pg-rman] [https://github.com/selenamarie/pg_replication_demo/tree/master/pgrman Simple demo for pg_rman setup]

Summary of features:
* Online backup and recovery, including backup from a replica
* Archive management and restore
* .ini configuration file
* Simple command-line options

Install notes:
* Written in C, install with 'make USE_PGXS=1'
* On Ubuntu/Debian, installs in non-default bin directory
* Commands are simple, manages WAL archive as well as backups

= repmgr =

[http://www.repmgr.org/ repmgr]
[https://github.com/2ndQuadrant/repmgr GitHub repository]
[https://github.com/selenamarie/pg_replication_demo/tree/master/repmgr Demo of a simple setup with repmgr]

Supported features:
* Setting up new replicas/hot_standby with streaming replication (makes recovery.conf itself)
* Making base backups
* Failover (automated, or not, including redirecting replicas to connect to a new master after failover)
* Lag monitoring (repmgrd)
* A "witness" DB server for monitoring (typically on a replica)
* License: GPLv3

Install notes:
* Written in C
* Developed on Debian systems, so support for package is present. [https://launchpad.net/repmgr Ubuntu packages] are available since Trusty (14.04).
* Otherwise, installs like a typical UNIX utility out of postgresql/contrib source tree (make USE_PGXS=1; make USE_PGXS=1 install)
* Detailed docs are in [https://github.com/2ndQuadrant/repmgr the README] for installing on many Linux platforms
* Doesn't appear to be supported on Mac OS X

= Skytools / walmgr =

[https://github.com/markokr/skytools Skytools]

= WAL-E =

[https://github.com/wal-e/wal-e WAL-E]

= WAL-G =

[https://github.com/wal-g/wal-g WAL-G]

Summary of features:
* Archive management and restore
* Inspired by WAL-E
* High performance
* Parallelized operation

Installation notes:
* Written in Go, install with the usual Go tools.

Binary Replication Tools

2018-08-21T19:40:36Z

Dfetter: /* Comparison Matrix */

= Disclaimer =

This is a Work-In-Progress, started Dec 28, 2012.

Additions welcome, and [[User:Selena|Selena]] reserves the right to edit. :)

= Purpose =

Compare binary replication tools for PostgreSQL for features and ease of use. This document should classify and differentiate binary replication tools for easier selection and fit to purpose.

== Comparison Matrix ==

{|border=1
!Tool!!Documentation!!License!!Makes base backups!!Makes base backups from replicas!!Manages backups!!Creates replicas!!Monitors replication delay!!Supports automated failover!!Transport used!!Source includes replication tests
|- style="background-color:#ffffcc;"
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html pg_basebackup]*
| [http://www.postgresql.org/docs/current/static/app-pgbasebackup.html Postgres docs]
| PostgreSQL
| Yes
| Yes
| No
| Manual
| No
| No
| PostgreSQL connection
|
|-
| [http://www.pgbackrest.org/ pgBackRest]
| [http://www.pgbackrest.org/user-guide.html Documentation]
| MIT
| Yes
| Yes
| Yes
| Manual
| No
| No
| ssh
| Yes

|-
| [http://www.pgbarman.org/ pgbarman]
| [http://docs.pgbarman.org/ Documentation]
| GPLv3
| Yes
| Yes
| Yes
| Manual
| Yes
| No
| rsync/ssh, pg_basebackup
|
|-
| [https://github.com/omniti-labs/omnipitr OmniPITR]
| [https://github.com/omniti-labs/omnipitr/blob/master/doc/intro.pod Intro]
| PostgreSQL
| Yes
| Yes
| No
| Manual
| WAL archive delay
| No
| rsync / ssh
|
|-
| [https://github.com/ohmu/pghoard pghoard]
| [https://github.com/ohmu/pghoard/blob/master/README.rst Readme]
| Apache
| Yes
| Yes
| Yes
| Yes
| No
| No
| AWS S3, Azure, Ceph, Google Cloud Storage
| Yes
|-
| [http://code.google.com/p/pg-rman/ pg-rman]
| [http://code.google.com/p/pg-rman/wiki/readme Readme]
| BSD
| Yes
| Yes
| Yes
| Manual
| No
| No
| local / NFS mount
|
|-
| [http://www.repmgr.org/ repmgr]
| [https://github.com/2ndQuadrant/repmgr#readme Readme]
| GPLv3
| No
| No
| No
| Yes
| Yes
| Yes
| rsync / ssh
|
|-
| [https://github.com/markokr/skytools Skytools]
| [https://github.com/markokr/skytools/blob/master/doc/walmgr3.txt walmgr3]
| BSD-ish
| ?
| ?
| ?
| Manual
| Yes
| Yes
| ?
| ?
|-
| [https://github.com/wal-e/WAL-E WAL-E]
| [https://github.com/wal-e/WAL-E#readme Readme]
| BSD
| Yes
| No
| Yes
| Manual
| No
| No
| HTTPS/SSL
|
|-
| [https://github.com/wal-g/wal-g WAL-G]
| [https://github.com/wal-g/wal-g/blob/master/README.md README]
| Apache 2.0
| Yes
| Yes
| No
| Manual
| Yes
| No
| HTTPS/SSL
| Yes
|}

* pg_basebackup is included with a standard PostgreSQL installation.

'''Tool''': name of the project that manages binary replication or WAL archiving

'''Documentation''': Link to canonical documentation for the project. Several projects have broken links that show up as top results in Google.

'''License''': License software is released under. So far, we only have open/free software projects listed. We could add commercial projects.

'''Makes base backups''': Yes if the project supports creating binary archives, including the necessary WAL to restore a backed-up instance.

'''Makes base backups from replicas''': Yes if the project supports creating binary archives and WAL using the PGDATA directory from a replica rather than the master database.

'''Manages backups''': Yes if the project adds, removes and lists binary archives.

'''Creates replicas''': Yes if the project automatically adds a recovery.conf (sets up replication) as part of restoring a base backup.

'''Monitors replication delay''': Yes if the project supports monitoring of replication delay (WAL shipping or streaming replication).

'''Supports automated failover''': Yes if the project has an option for detecting master failure and promoting a replica to master.

'''Transport used''': Supported methods for file transfer for making backups or replicas

= Barman =

[http://www.pgbarman.org/ pgbarman] [https://github.com/selenamarie/pg_replication_demo/tree/master/barman Demo setup for pgbarman]

Summary of features:
* Creates base backups
* Uses SSH as transport for backup
* Configuration stored in file or command-line
* Restore is automatable for creating replicas, although not explictly supported
* GPLv3

Install notes:
* Had a dependency problem with 9.1 on Ubuntu Precise, so installed from source
* Missing dep for argcomplete, noted in README in demo repo
* written in Python

= OmniPITR =

[https://github.com/omniti-labs/omnipitr OmniPITR]
[https://github.com/selenamarie/pg_replication_demo/tree/master/omnipitr Demo of a simple replication setup with OmniPITR]

Summary of Features:
* Creating PITR backups from Master or Slave
* Restoring a PITR backup for DR
* Creating replicas (by untarring backups)
* Monitoring of replicas
* Supports 'pause removal' of WAL during a backup (nice!)
* PostgreSQL license

Install notes:
* No packaging, perl
* No documented support for streaming replication
* Uses '^' instead of '%' in custom logfile naming
* No configuration file option (instead of using long command-line options)
* Supported on all Linux, Solaris variants

= pgBackRest =

[http://www.pgbackrest.org/ pgBackRest]

Summary of features:
* Parallel Backup & Restore
* Local or Remote Operation
* Full, Incremental, & Differential Backups
* Backup & Archive Expiration
* Backup Resume
* Streaming Compression & Checksums
* Delta Restore
* Parallel WAL Archiving
* Tablespace & Link Support
* Compatibility with PostgreSQL >= 8.3
* S3 Support

= pghoard =

https://github.com/ohmu/pghoard

Summary of features:
* Stores basebackups and WAL to cloud object stores (AWS S3, Azure, Ceph, Google Cloud)
* Restore existing basebackups and setup a new cluster with a recovery.conf pointing to another master database
* Create scheduled basebackups
* Can be used as archive_command to archive WALs in the object store
* Can be used as restore_command to restore WALs from the object store
* Basebackup and WAL compression using LZMA
* Optionally encrypts backups
* Supports PITR using timestamps, names and xids

Install notes:
* Written in Python, includes Debian and Fedora packaging scripts
* 'pghoard' daemon manages basebackups and cleans up WALs
* 'pghoard_archive_command' and 'pghoard_restore' access the locally running 'pghoard' daemon to store and restore files

= pg-rman =

[http://code.google.com/p/pg-rman/ pg-rman] [https://github.com/selenamarie/pg_replication_demo/tree/master/pgrman Simple demo for pg_rman setup]

Summary of features:
* Online backup and recovery, including backup from a replica
* Archive management and restore
* .ini configuration file
* Simple command-line options

Install notes:
* Written in C, install with 'make USE_PGXS=1'
* On Ubuntu/Debian, installs in non-default bin directory
* Commands are simple, manages WAL archive as well as backups

= repmgr =

[http://www.repmgr.org/ repmgr]
[https://github.com/2ndQuadrant/repmgr GitHub repository]
[https://github.com/selenamarie/pg_replication_demo/tree/master/repmgr Demo of a simple setup with repmgr]

Supported features:
* Setting up new replicas/hot_standby with streaming replication (makes recovery.conf itself)
* Making base backups
* Failover (automated, or not, including redirecting replicas to connect to a new master after failover)
* Lag monitoring (repmgrd)
* A "witness" DB server for monitoring (typically on a replica)
* License: GPLv3

Install notes:
* Written in C
* Developed on Debian systems, so support for package is present. [https://launchpad.net/repmgr Ubuntu packages] are available since Trusty (14.04).
* Otherwise, installs like a typical UNIX utility out of postgresql/contrib source tree (make USE_PGXS=1; make USE_PGXS=1 install)
* Detailed docs are in [https://github.com/2ndQuadrant/repmgr the README] for installing on many Linux platforms
* Doesn't appear to be supported on Mac OS X

= Skytools / walmgr =

[https://github.com/markokr/skytools Skytools]

= WAL-E =

[https://github.com/wal-e/wal-e WAL-E]

Community Guide to PostgreSQL GUI Tools

2018-08-20T01:36:26Z

Dfetter:

{{Languages}}

== Alternate Guides ==

Another detailed summary from 2009 is available at
[http://www.postgresonline.com/journal/index.php?/archives/133-Database-Administration,-Reporting,-and-Light-application-development.html Database Administration, Reporting, and Light application development]

== Open Source / Free Software ==

=== pgAdmin 4 ===

http://www.pgadmin.org/

MS Windows, GNU/Linux, FreeBSD, Mac OS X, OpenBSD, Solaris

Admin

pgAdmin III is THE Open Source management tool for your PostgreSQL databases. Features full Unicode support, fast, multithreaded query and data editting tools and support for all PostgreSQL object types.

pgAdmin III is bundled with the Windows installer, and you can use that such a client to administer a remote server on another OS. Note that binary packages for platforms like RPM don't show up in every point release, you currently have to go back to v1.8.0 to get the last full set of packages.

Free Administration Centre for the PostgreSQL database. Includes a graphical administration interface, an SQL query tool, a procedural code editor and much more. pgAdmin III is designed to answer the needs of most users, from writing simple SQL queries to developing complex databases. The graphical interface supports all PostgreSQL features and makes administration easy. Available in more than 30 languages and for several operating systems.

=== phpPgAdmin ===

http://sourceforge.net/projects/phppgadmin

browser-based, requires webserver

Admin

Similar to the ever-popular phpMyAdmin, enhanced for PostgreSQL, supports browsing and modification of most types of PostgreSQL database objects, plus execution of ad-hoc queries. Maintained by (who else?) the phpPgAdmin team. (JMB 11.2002).

phpPgAdmin (and the required Apache and PHP packages) may be easily installed using Stack Builder if you are running a one-click-installer PostgreSQL distribution.

=== Adminer ===

http://www.adminer.org

browser-based, requires webserver

Adminer (formerly phpMinAdmin) is a full-featured database management tool written in PHP. Conversely to phpMyAdmin, it consist of a single file ready to deploy to the target server. Adminer is available for MySQL, PostgreSQL, SQLite, MS SQL and Oracle.

=== Libre Office ===

http://www.libreoffice.org/download/3-5-new-features-and-fixes/

New native driver for PostgreSQL databases (for versions > 8.4 - support for version 8.4 will be included in LibreOffice 3.5.1).

=== GNOME-DB ===

http://www.gnome-db.org

Linux, Unix

Admin

Database administration/user tool for GNOME, based on libgda/libgnomedb, which are a complete database-independent access layer for UNIX systems, with support for PostgreSQL, MySQL, Sybase, MS SQL Server, Oracle, Interbase/Firebird, MS Access files, xBase.

=== TOra, an Oracle tool with some PostgreSQL support ===

http://tora.sf.net/

Linux & Windows

Admin

An Oracle database administration interface, with limited ability to browse PostgreSQL databases (tables, views, and functions only). I'm told that if you have the Oracle libraries, Tora's sophisticated function editor will work for PostgreSQL as well. Developed by Henrik Johnson as a Quest Toad clone. (JMB 11.2002)

=== Kexi ===

http://www.kexi-project.org/

Kexi is part of the Calligra Suite and is released under the GNU General Public License (GPL) and LGPL.

available for
FreeBSD & Linux, Apple, Windows, (Android)

=== SQL Workbench/J ===

http://www.sql-workbench.net

Java (multi-platform)

An OpenSource SQL GUI tool similar to Squirrel. Data can be edited directly in the result set. It has strong support for exporting and importing data between databases using its own SQL command extension. It can be used in GUI mode or as a console application. All SQL Workbench specific commands can also be run in batch mode to automate export and import task. It supports schema comparison ("diff") and copying data between databases.

=== Druid III ===

http://druid.sourceforge.net/

Java (multi-platform)

The druid is a tools that allows users to create databases in a graphical way. The user can add tables, fields, folders to group tables and can modify most of the database options that follow the SQL-92 standard. In addition to sql options, the user can document each table and each field with HTML information. Once the database is created, the druid can generate:

* HTML documentation: for all tables, with browsing facilities
* PDF documentation: for all tables
* Java classes: (one class for each table) that contain tables' constants (such as fields size) plus java code added by the user
* A data dictionarythat contains all tables and fields present in the database
* SQL script which contains all table definitions that can be piped to the DBMS
* And much more info...

=== Power*Architect ===

http://www.sqlpower.ca/page/architect

Java (multi-platform)

Power*Architect is an ERD modelling tool that is based on Java and JDBC. Support for forward and reverse engineering PostgreSQL databases is supported. It's OpenSource with a GPL license.

=== RISE PostgreSQL code generator ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1889

Windows

The RISE PostgreSQL code generator generates native PL/pgSQL scripts. Model your information in the free RISE Editor and generate your database script. The script incrementally updates the tables, columns, indexes and constraints in the database to match the RISE model. Once the database model is updated, the views defined in the RISE model are created in the database and possible default data, entered in the model, is inserted.

=== Open Source CMS ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=2017

Windows

The CMS is a free Visual Studio 2010 solution template with a set of projects providing a complete Content Management System (CMS) based on RISE Visual Modeling with model, full source, sample site and DB-scripts for PostgreSQL, MySQL and SQL Server.

It’s a complete ready-to-run Visual Studio solution with model, source code and web clients. It illustrates how to use RISE, how to implement a SOA backend and how to build RIA frontends.

=== DBeaver ===

http://dbeaver.jkiss.org/

Eclipse/Java (multi-platform)

Eclipse-based environment, supporting many SQL databases from different vendors, as well as few NoSQL ones (Cassandra, etc).
Good query editor with syntax highlighting, completion and autosave.
Editing of query results. SSH tunneling support. Tons of other cool features.
Quite good, but not 100% perfect PostgreSQL support (yet?). Regularly updated, as of 2018.

=== OmniDB ===

https://github.com/OmniDB/OmniDB

Django/Python (multi-platform), browser-based

Open source full-featured web tool for database management. Currently supports PostgreSQL only. More RDBMS support coming soon, including the ability of converting databases from any supported RDBMS to PostgreSQL and back.

=== Postbird ===

https://github.com/paxa/postbird

MacOs

Open source, desktop application to manage your local or remote PostgreSQL databases.

=== Sohag Developer ===
[http://sohag-developer.com/ Sohag Developer]

Gnu/Linux Windows (Other OS can compile from source code).

Build a powerful database applications following few steps using Sohag Developer .
Sohag Developer currently supports PostgreSQL database and has a set of generators that generates (Qt/C++ code and ui forms - PHP web applications uses web forms and bootstrap framework ) to manipulate the data in the database tables or views.

=== PASH-Viewer: PostgreSQL Active Session History Viewer ===
https://github.com/dbacvetkov/PASH-Viewer

Java (multi-platform).

Open-source software which provides graphical view of active session history and help you to answer questions like "What wait events were taking most time?", "Which sessions were taking most time?", "Which queries were taking most time and what were they doing?". It also supports Active Session History extension by pgsentinel.

== Proprietary ==

=== dbForge Studio for PostgreSQL ===

https://www.devart.com/dbforge/postgresql/studio/

Free GUI tool for managing and developing databases and objects. The IDE for PostgreSQL allows users to create, develop, and execute queries, edit and adjust the code to your requirements in a convenient and user-friendly interface.

=== PSequel ===

http://www.psequel.com/

OS X Yosemite only, free, "Sequel Pro" inspired.

=== EMS SQL Manager for PostgreSQL Freeware ===

http://www.sqlmanager.net/en/tools/free

Windows

EMS SQL Manager for PostgreSQL Freeware (EMS SQL Manager Lite for PostgreSQL) is an excellent and easy-to-use freeware graphical tool for PostgreSQL database administration. It has the minimal required set of tools for those users who are new to PostgreSQL server and need only its basic functionality.
EMS SQL Manager for PostgreSQL Freeware allows you to work with servers, databases and schemas, view, edit, search, group, sort and filter any data stored in a database, create and execute SQL queries with powerful SQL editor, handle multiple selected objects at a time and much more.

=== Marshal SQL Utility ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1756

Windows

The Marshal SQL Utility is a generic cross database utility with batch execution capabilities. It allows you to test ODBC connections, browse database schemas, discover tables, views and columns.

Key features of Marshal SQL Utility:

* Execute any query supported by your database server
* Execute batches of queries
* Discover tables and views in your database
* Discover columns for a selected table or view
* Supports BLOBS and CLOBS
* Save your results to file
* Use any ODBC compliant database such as PostgreSQL.

=== RISE PHP for PostgreSQL code generator ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1888

Windows

The RISE PHP for PostgreSQL code generator renders PHP source code for database access. Model your information and programming interfaces in the free RISE Editor and generate your code. The generated code implements the classes and methods corresponding to the information interfaces specified in the RISE model. This includes classes for database access and, optionally, classes implementing SOAP/JSON web services and proxy classes assisting the implementation of a PHP SOAP client.

=== RISE - Model Driven Development using ERD / UML ===

http://www.risetobloome.com

Windows

RISE is a free software suite for model driven information system development. Use a single source RISE model to generate your entire information solution including database, web services and documentation. Boost development throughput and improve quality and maintainability!

The RISE user experience is based on a project concept, similar to that of most integrated development environments. The user works with resources and drawings that are part of a single development project.

RISE supports a fully graphical approach to information modeling and system engineering, using ERD (Entity Relationship Diagram) as well as UML (Unified Modeling Language). This includes drag-and-drop of entities, their attributes and relations, as well as of views and entire web services.

RISE supports graphic editing of complex objects such as views and orchestrated methods. RISE automatically safeguards the combination process, thus, assuring a technically correct result.

RISE provides several ways to generate code from the model; directly to file, via the RISE Server or as an Internet service. RISE provides code generators for the database layer (SQL/DDL) as well as for the server side application layer (web services and persistent classes). All database scripts are incremental allowing you to install and maintain any number of databases from a single model.

Feature list
http://www.risetobloome.com/Page_1_S.aspx?ITEM=1355

=== WaveMaker Ajax GUI Design Tool ===

http://www.wavemaker.com/

Windows, Macintosh, Linux

WaveMaker is an Ajax-based GUI design tool for Postgres. WaveMaker is built using itself! WaveMaker generates a standard Java WAR file based on Spring, Hibernate and Dojo. WaveMaker supports Postgres schema creation and import and includes a visual query editor.

=== AnySQL Maestro ===

http://www.sqlmaestro.com/products/anysql/maestro/

Windows

AnySQL Maestro is a freeware tool for administering any database engine (PostgreSQL, SQL Server, Oracle, MySQL, MS Access, etc.), which is accessible via ODBC driver or OLE DB provider. Includes Database Designer, Visual Query Builder, BLOB Viewer/Editor, SQL Editor, Data export/import and other features.

=== TeamPostgreSQL ===

http://www.teampostgresql.com

browser-based, webserver included

AJAX/JavaScript-powered web interface for PostgreSQL administration. Browse, maintain and create data and database objects from anywhere, in the web browser. Supports SSH for both the web interface and the database connections. Rich interface with tabbed SQL editor with auto-completion, inline row-editing widgets, click-through foreign key navigation between rows and tables, 'favorites' management for commonly used scripts, and more.

Installers available for Windows, Mac and Linux, alternatively download a simple cross-platform archive that runs anywhere with simple script.

=== Postgres Compare ===

[[File:Postgres_compare.png|thumb|left|frameless]]

https://www.postgrescompare.com/

Windows, Mac & Linux

A comprehensive tool for identifying the differences between databases and generating an update script to synchronize them. Postgres Compare reads the system catalogs to determine the structure of the database and compares it to another to find the changes. Generate SQL and deploy the alterations, save snapshots for later. Automate the process via the command line.

Alpha build available now https://www.postgrescompare.com/downloads

<div style="clear:both;"></div>

=== JetBrains IDEs - DataGrip, IntelliJ IDEA, PHPStorm, PyCharm, RubyMine, etc ... ===

http://www.jetbrains.com/

Windows, Mac OS X, Linux

JetBrains has a dedicated SQL IDE — DataGrip which can connect to PostgreSQL as well. It provides code completion, multi cursors, local query history, navigation, refactorings and language injection support.
https://www.jetbrains.com/datagrip/

Other JetBrains Products, for example, PHPStorm, have built-in database plugin, and it has the same functionality as DataGrip.

After you configured the data sources of your project, you can easily create tables, foreign keys, indexes much easier than usual, because the IDE is very smart; for example by foreign keys it automatically sets the name of the key and the related columns. For me, it is so far the best experience by creating a basic database schema. Even with editable EER models was it slower...
By the settings of [http://goo.gl/TuqiPRpantun romantis terbaru] your data source you can configure the SQL dialect of your database. After that, if you want to add stored procedures or triggers, you will have code completion which is favorable too. So I think JetBrains products speed up your work if you exactly know what you want, and how can you make it.

For any JetBrains IDE, there is a free license for open source projects. For enterprise usage there is a 30 days trial, after that, you can buy a personal or proprietary license which is very cheap compared to other products.

For PyCharm (even the Community Edition) you can install the free third-party plugin [http://confluence.jetbrains.com/display/CONTEST/Database+Navigator Database Navigator] (Settings -> IDE Settings -> Plugins). It appears to deliver the same functionality described above for PHPStorm. You will get a new menu DB Navigator, left to the Help menu.

=== TablePlus ===

https://tableplus.io/

macOS

A modern, native tool with an elegant UI that allows you to simultaneously manage multiple databases, including PostgreSQL.

* True native built.

* Workspace supports multiple tabs, multiple windows

* Powerful SQL editor with full features: auto syntax highlight, auto-suggestion, split pane, favorite and history.

* Data Filter & Sorting, import & export

* Full-dark theme & modern shortcut

With plugin system, you can be able to write your own new features to work with database per your needs (export charts, pretty json…).

=== SQLPro for Postgres ===

http://www.hankinsoft.com/SQLProPostgres

Mac OS X 10.8 and above

Features:
* 100% native OS X app with a clean and simple to use interface.
* Query editor with syntax highlighting and autocomplete.
* Support for multiple result set execution.
* History feature, displaying your last ten executed queries.
* Primary key detection for inline result set modifications.
* Custom theme support allowing developers to work with style.

=== Postico ===

https://eggerapps.at/postico/

Mac OS X

Postico is a fully native Mac app for connecting to your PostgreSQL server. It supports encrypted connections via SSL and SSH to PostgreSQL 8.0 and later, including Amazon Redshift.

Postico has a powerful table content editor with in-cell editing and form-based row editing in a sidebar. You can quickly filter tables by keywords or even complex SQL expressions.

There's also a table structure editor for editing columns, types, default values, foreign keys, check constraints etc.

Finally, there's a convenient SQL Query Editor with support for query history and syntax highlighting. It also has convenience features like auto-indent and shortcuts for comment line etc.

=== SEQUEL for PostgreSQL ===

http://www.sequel.tech

macOS

SEQUEL for PostgreSQL is a professional DB administration and management tool, with extremely intuitive and feature-rich GUI that makes it the best assistant tool for developers and admins. SEQUEL is lightweight, fast and powerful that it can significantly simplify the DB management process. For those who cannot live without a CLI, SEQUEL offers a powerful Query Editor with syntax highlight, autocomplete and a Console log view that is always visible, so you can monitor the communication with your databases. It includes:

* Database management forms for Schema, Table, Index, Foreign key, Trigger, Rule, Sequence, Collation, Domain, Enum type, Tablespace and Language objects with full parameters support
* Assistant info views for Object information, Actions, Help, and Documentation
* Jump bar for quick objects selection and navigation
* Taskbar with multi-task monitoring support
* Console log view
* Syntax highlight, autocomplete, current and selection query execution and explain, line numbering and working statement detection
* Direct editing in the results view, query results explanation
* Powerful Field editor
* Transaction based database updates
* Code preview and Content editing

=== dbForge Data Compare for PostgreSQL ===

http://www.devart.com/dbforge/postgresql/datacompare/

Microsoft Windows 2000/XP/2003/Vista and Windows 7, 8, 10

'''dbForge Data Compare for PostgreSQL''' by '''Devart''' is a tool for table data comparison and synchronization. When using PostgreSQL data compare tool developer can detect data differences in compared PostgreSQL tables; generate data synchronization script and execute it to eliminate all these differences.

'''Key features:'''

* Identify the differences between two databases
* Compare separate tables or table groups by table name mask
* Compare tables with different structure
* Generate a report embodying data diff and save it for further analysis
* Sync data in tables and views in full or in part
* Generate SQL script for database synchronization
* Organize database synchronization according to the schedule

=== Full Convert ===

https://www.spectralcore.com/fullconvert

Database conversion and synchronization between PostgreSQL and Microsoft Access, dBase, FoxPro, Microsoft Excel, Firebird, Interbase, MySQL, Oracle, Paradox, Microsoft SQL Server, SQL Server, SQL Server Azure, SQL Server Compact(SQLCE), SQLite, Delimited text files (CSV), XML and many more via ODBC.

=== Nucleon Database Master for PostgreSQL and Others ===

Nucleon Database Master is a modern, powerful, intuitive, easy to use and all in one PostgreSQL MongoDB, Oracle, DB2, Informix, Ingres, SQL Server, SQL Azure, MySQL, FireBird, SQLite client application with a consistent interface that simplifies managing, querying, editing, visualizing, designing and [http://mitraharga.blogspot.co.uk/2014/09/harga-tablet-pc-axioo.htmlharga tablet axioo] reporting relational and schema-free (NoSQL) database systems. You can connect any database system via ODBC and OleDB connections.Using Database Master, you can execute SQL, LINQ, JSON queries or you can create, edit and delete all database objects such as tables, views, procedures, columns, indexes, collections, and triggers. You can execute SQL queries and scripts, view and edit table data including BLOBs (Image, Text or any file), represent tables and its relations as an ER(Entity Relationship) diagram.

Info:
http://www.nucleonsoftware.com/
Windows, other platforms via WINE
Admin

=== DBTools Manager ===

http://www.dbtools.com.br

Windows

Admin

Freeware, available for PostgreSQL and MySQL, allows managing all aspects of the database: db, table, triggers, functions, etc. Includes import/export wizards to migrate data and structure to/from other database engines. Developed by DBTools Software.

=== PgManager ===

http://www.ems-hitech.com/pgmanager

Windows, Linux version just released

Admin

Basically a proprietary, more powerful version of PGAdmin II or PGAccess. Adds support for trigger and constraint editing, metadata logging, and query monitoring. Also includes multiple-format data import/export tools, which are also available on their own for Linux. Developed by EMS Hitech. (JMB 4.2003).

=== DeZign for Databases ===

http://www.datanamic.com

Windows

ERD

DeZign is a database development tool using an entity relationship diagram. It visually supports the layout of the entities and relations and automatically generates SQL schemas for most leading databases including PostgreSQL.

=== Case Studio 2 / Toad Data Modeler ===

http://www.casestudio.com/enu/index.aspx

Windows

ERD

Commenter 1: I just downloaded the trial version, so far it looks really promising and claims to support PostgreSQL. Handles reverse engineering of existing databases, and has a really nice interface for setting up tables, relationships etc. You can get a lite or full version. The description from the website... Professional database modeling tool for various databases. CASE Studio 2 includes following key features:

LITE version features + Reverse Engineering from various database systems Version Manager Data Flow Diagrams Definition of user-defined variables Large COM interface Users, User groups and User permission support and many more.

Case Studio was acquired, and renamed 'Toad Data Modeler'.

Commenter 2: I've used the licensed version before and after the name change. PostgreSQL support is excellent.

=== PostgreSQL PHP Generator ===

http://www.sqlmaestro.com/products/postgresql/phpgenerator/

Windows

PostgreSQL PHP Generator is a freeware but powerful PostgreSQL GUI frontend that allows you to generate high-quality PHP scripts for the selected tables, views and queries for the further working with these objects through the web.

=== pgEdit ===

http://pgedit.com

Macintosh
pgEdit is a high-performance SQL editor and development environment designed specifically for PostgreSQL relational databases. pgEdit features include SQL syntax coloring, direct source code execution, PHP support, integrated documentation, and extensive customizable editing facilities.

pgEdit uses psql, the interactive terminal application included with every PostgreSQL installation. This makes it easy to develop with pgEdit and then transfer your work to any PostgreSQL installation for maintenance and production tasks.

pgEdit is a native application for both Macintosh and Windows. It does not use Java or require installation of external libraries. You have the option of using the version of psql included with pgEdit or a different version installed anywhere on your hard drive.

=== RazorSQL ===

http://www.razorsql.com/

Macintosh/Windows/Linux/Solaris

RazorSQL is an SQL query tool, database browser, SQL editor, and database administration tool that supports PostgreSQL and any other JDBC or ODBC compliant database. Some of the major features are tools for creating, dropping, and altering objects such as tables, views, indexes, triggers, functions, users, and databases; a programming editor that supports 20 different programming languages; import and export tools; auto column and table lookup; and a query builder, query scheduler, and SQL formatter.

=== MicroOLAP Database Designer ===

http://www.microolap.com/products/database/postgresql-designer/

Windows ODBC

Database Designer for PostgreSQL is an easy CASE tool with an intuitive graphical interface allowing you to build a clear and effective database structure visually, see the complete picture (diagram) representing all the tables, references between them, views, stored procedures and other objects. Then you can easily generate a physical database on a server, modify it according to any changes you made to the diagram using fast ALTER statements.

=== Import / Export and synchronization tools for PostgreSQL ===

http://convertdb.com/postgresql

Microsoft Windows 8 / 7 / Vista / XP / 2000 / NT.
The software is able to connect to remote PostgreSQL 9.x/7.4 located on Linux, Solaris, Mac OS X, and Windows.

ConvertDB cross-database migration tools assist in data conversion and synchronization among PostgreSQL, MySQL, MS SQL Server, MS Windows SQL Azure, and MS Access databases

* 1 Million of records can be transferred in 5-10 minutes.
* Bi-directional synchronization between PostgreSQL, MS SQL, MySQL and Oracle
* Scheduling migration and synchronization jobs.

=== dbForge Studio for PostgreSQL ===

https://www.devart.com/dbforge/postgresql/studio/

Microsoft Windows 7, 8, 10

'''dbForge Studio for PostgreSQL''' is a brand new tool for PostgreSQL databases development, management, and editing process enjoyable and easy by Devart. The PostgreSQL IDE allows users to create, develop, and execute queries, edit and adjust the code to the requirements in a convenient and UI. The tool provides the PostgreSQL data editor functionality for queries customization and property window for the viewing all the required information of PostgreSQL database objects.

'''Key features:'''

* Code Completion helps to improve code quality when creating and editing queries with List Members, Parameter Info, Quick Info, Complete Word.
* Object Explorer for easy navigation through the object tree. You can retrieve data from the database on a single SQL document, truncate a table, select Properties to view some information on the object.
* Data Editor for management settings of tables, such as adjust column width, set either paginal or auto-search mode by default. Color and format rows and cells using a rich set of fonts and size. The tool has predefined data type formats to meet your own needs.

=== dotConnect for PostgreSQL ===

https://www.devart.com/dotconnect/postgresql/

Windows

'''dotConnect for PostgreSQL''', formerly known as PostgreSQLDirect .NET, is an enhanced ORM enabled data provider for PostgreSQL that builds on ADO.NET technology to present a complete solution for developing PostgreSQL-based database applications. It introduces new approaches for designing application architecture, boosts productivity, and leverages database applications.

'''Key features:'''

* Direct Mode
* Database Application Development Extension
* PostgreSQL Advanced Features Support
* Optimized Code
* ORM Support
* BIS Support

=== PostgreSQL Data Access Components ===

Windows

https://www.devart.com/pgdac/

PostgreSQL Data Access Components (PgDAC) is a library of components that provides native connectivity to PostgreSQL from Delphi, C++Builder, Lazarus (and Free Pascal) on Windows, Mac OS X, iOS, Android, Linux, and FreeBSD for both 32-bit and 64-bit platforms. PgDAC is designed to help programmers develop really lightweight, faster and cleaner PostgreSQL database applications without deploying any additional libraries.

Native Connectivity to PostgreSQL
PgDAC is a complete replacement for standard PostgreSQL connectivity solutions and presents an efficient alternative to the Borland Database Engine (BDE) and standard dbExpress driver for access to PostgreSQL. It provides direct access to PostgreSQL without PostgreSQL Client.

=== ODBC Driver for PostgreSQL ===

https://www.devart.com/odbc/postgresql/

Windows

Devart ODBC Driver for PostgreSQL provides high-performance and feature-rich connectivity solution for ODBC-based applications to access PostgreSQL databases from Windows, both 32-bit and 64-bit. Full support for standard ODBC API functions and data types implemented in our driver makes the interaction of your database applications with PostgreSQL fast, easy and extremely handy.

=== Excel Add-in for PostgreSQL ===

https://www.devart.com/excel-addins/postgresql.html

Windows

Devart Excel Add-in for PostgreSQL allows you to quickly and easily connect Microsoft Excel to PostgreSQL, load data from PostgreSQL to Excel, instantly refresh data in an Excel workbook from the database, edit these data, and save them back to PostgreSQL. It enables you to work with PostgreSQL data like with usual Excel worksheets, easily perform data cleansing and de-duplication, and apply all the Excel's powerful data processing and analysis capabilities to these data.

=== EMS Database Management Tools for PostgreSQL ===

http://www.sqlmanager.net/en/products/postgresql

Windows

PostgreSQL Tools Products Family:

* [http://www.sqlmanager.net/en/products/studio/postgresql SQL Management Studio for PostgreSQL] - a single workbench for administering PostgreSQL databases, managing database schema and objects as well as for database design, migration, extraction, query building, data import, export, and database comparison.

* [http://www.sqlmanager.net/en/products/postgresql/manager SQL Manager for PostgreSQL] - high performance graphical tool for PostgreSQL database administration and development. It makes creating and editing PostgreSQL database objects easy and fast, and allows you to run SQL scripts, visually design databases, build SQL queries, extract, print and search metadata, import and export PostgreSQL database data and much more.

* [http://www.sqlmanager.net/en/products/postgresql/dataexport Data Export for PostgreSQL] - tool to export PostgreSQL database data quickly to any of 19 available formats, including MS Access, MS Excel, MS Word, RTF, HTML, TXT, ODF and more. Data Export for PostgreSQL has a [http://aurora-ndut.blogspot.fr/2013/10/kata-kata-lucu.htmlkata kata lucu] friendly wizard, which allows you to set various options of PostgreSQL export process visually and a command-line utility to automate your PostgreSQL export jobs using the configuration file.

* [http://www.sqlmanager.net/en/products/postgresql/dataimport Data Import for PostgreSQL] - tool to import data to PostgreSQL tables from MS Excel 97-2007, MS Access, DBF, TXT, CSV, MS Word 2007, RTF, ODF and HTML files. This utility allows you to quickly import data to one or several PostgreSQL tables or views at once, save all PostgreSQL import parameters set on current wizard session, use special batch insert mode to import PostgreSQL data at the maximum possible speed and much more.

* [http://www.sqlmanager.net/en/products/postgresql/datapump Data Pump for PostgreSQL] - migration tool for converting databases and importing table data from an ADO-compatible source (e.g. MS Access, MS SQL database or any other database with ADO support) to PostgreSQL databases.

* [http://www.sqlmanager.net/en/products/postgresql/datagenerator Data Generator for PostgreSQL] - tool for generating test data to PostgreSQL database tables. The utility can help you to simulate the database production environment and allows you to populate several PostgreSQL database tables with test data simultaneously, define tables for generating data, set value ranges, control a wide variety of generation parameters for each field type and much more.

* [http://www.sqlmanager.net/en/products/postgresql/dbcomparer DB Comparer for PostgreSQL] - a tool for comparing PostgreSQL database schemas and discovering differences in their structures. You can view all the differences in compared database objects and execute an automatically generated script to synchronize structure of PostgreSQL databases and eliminate these differences.

* [http://www.sqlmanager.net/en/products/postgresql/extract DB Extract for PostgreSQL] - easy-to-use tool for creating PostgreSQL database backups in a form of SQL scripts. This database script utility allows you to save metadata of all PostgreSQL database objects as well as PostgreSQL table data as database snapshots.

* [http://www.sqlmanager.net/en/products/postgresql/query SQL Query for PostgreSQL] - a useful tool that lets you quickly and simply build SQL queries to PostgreSQL databases. Visual PostgreSQL query building, as well as direct editing of a query text, is available.

* [http://www.sqlmanager.net/en/products/postgresql/datacomparer Data Comparer for PostgreSQL] - tool for PostgreSQL data comparison and synchronization. Using this utility you can view all the differences in compared PostgreSQL tables and execute an automatically generated script to eliminate these differences.

=== SQL Maestro Group products for PostgreSQL ===

http://www.sqlmaestro.com/products/postgresql/

Windows

[http://www.sqlmaestro.com SQL Maestro Group] offers a number of tools for PostgreSQL.

* [http://www.sqlmaestro.com/products/postgresql/maestro/ PostgreSQL Maestro] allows you to create, edit, copy, drop and dump database objects easy and fast. You can also design your database as ER diagram, build queries visually, execute SQL queries and scripts, debug PL/pgSQL functions, view and edit data including BLOBs, represent data as diagrams, export and import data to/from most popular file formats, analyze your data summarized into multidimensional views and hierarchies (OLAP cubes), manage PostgreSQL roles, users, groups and privileges, and use a lot of other admin tools designed for making your work with PostgreSQL database server comfortable and efficient.

* [http://www.sqlmaestro.com/products/postgresql/datawizard/ PostgreSQL Data Wizard] provides you with a number of easy-to-use wizards to transfer any database to PostgreSQL, export data from PostgreSQL tables, views and queries to most popular formats, and import data from various sources into PostgreSQL tables.

* [http://www.sqlmaestro.com/products/postgresql/codefactory/ PostgreSQL Code Factory] is a GUI tool aimed at the SQL queries and scripts development.

* [http://www.sqlmaestro.com/products/postgresql/datasync/ PostgreSQL Data Sync] is a powerful and easy-to-use tool for database contents comparison and synchronization.

* [http://www.sqlmaestro.com/products/postgresql/phpgenerator/ PostgreSQL PHP Generator Professional] is a frontend that allows you to generate high-quality PHP applications for your database in a few mouse clicks.

SQL Maestro Group also produces similar tools for MySQL, Oracle, MS SQL Server, SQLite, Firebird, DB2, SQL Anywhere, and MaxDB.

=== Datanamic DataDiff for PostgreSQL ===

http://www.datanamic.com/datadiff-for-postgresql/

Windows

Datanamic DataDiff for PostgreSQL is a utility for data comparison and synchronization. Compare data for selected tables in two databases, view differences and publish changes quickly and safely. Flexible comparison and synchronization settings will enable you to set up a customized comparison key and to select tables and fields for comparison and for synchronization.
DB Data Difftective can be used for data migrations, verification of (corrupt) data, data auditing etc.

=== Datanamic SchemaDiff for PostgreSQL ===

http://www.datanamic.com/schemadiff-for-postgresql/index.html

Windows

Datanamic SchemaDiff for PostgreSQL is a tool for comparison and synchronization of database schemas. It allows you to compare and synchronize tables, views, functions, sequences (generators), stored procedures, triggers and constraints between two databases.

=== DB MultiRun PostgreSQL Edition ===

http://www.datanamic.com/multirun/index.html

Windows

DB MultiRun is a simple tool to execute multiple SQL scripts on multiple databases quickly.
Define a list of databases, add SQL scripts to execute on these databases and click "execute" to run those scripts on the databases in the list. The multi-threaded execution of the SQL scripts makes it complete the task fast. After execution of the scripts, you can examine the results of the executed scripts on each database.

=== SQLPro ===

http://www.vive.net/products/sqlpro.htm

Windows

SqlPro is an easy to use database GUI tool for six popular databases (Oracle, MySQL, PostgreSQL, SQL Server, SQLite, and Access). One IDE makes database administration and development faster and error free.
SQLPro Key Features: color-coding of the SQL, drag-and-drop of objects into the editor pane to save you from typing their names, retrieval of SQL code for things like stored procedures and triggers from the underlying database, and one-click creation of SELECT and INSERT statements. You can open, save and print SQL scripts.
SQLPro uses native drivers to connect to the databases (no ODBS or third party engines to install).

=== DB Doc ===

http://www.yohz.com/dbdoc_details.htm

Windows/Linux(Wine)

DB Doc helps you document your database structure and objects. Documents can be generated as PDF reports, HTML pages, Microsoft Word (docx) file, or a single compiled HTML file. The layout is fully customizable, and you can quickly view inter-object dependencies using hyperlinks.

DB Doc supports PostgreSQL 8.3 to 9.4.

=== SQL Blob Export ===

http://www.yohz.com/sbe_details.htm

Windows

SQL Blob Export exports unlimited images and files from your tables or queries in 5 simple steps.

=== SQL File Import ===

http://www.yohz.com/sfi_overview.htm

Windows

SQL File Import allows you to upload files, images, and other data into your database, without having to write any SQL statements. SQL File Import supports PostgreSQL, Firebird, MySQL, Oracle, SQLite, SQL Server, and various ODBC-supported databases (e.g. DB2 and PostgreSQL).

A scripting engine allows you to transform data before importing them into your database. A command line version is also included to allow you to perform unattended upload/import tasks.

=== SQL Image Viewer ===

http://www.yohz.com/siv_details.htm

Windows

SQL Image Viewer allows you to retrieve, view, convert and export images stored in Firebird, MySQL, Oracle, SQLite, SQL Server, and various ODBC-supported databases (e.g. DB2 and PostgreSQL). It supports the following image formats: BMP, GIF, JPG, PNG, PSD, and TIFF.

It also allows you to export binary data and recognises the following binary file types: PDF, MP3, WAV, 7Z, BZ2, GZ, RAR, ZIP, and has experimental support for DOC, PPT and XLS file types.

A command line version is also included to allow you to perform unattended scheduled exports of binary data.

=== SQL Multi Select ===

http://www.yohz.com/sms_details.htm

Windows

SQL Multi Select is a query tool that allows you to run multiple scripts on multiple servers with a single click. Result sets from different servers are consolidated into a single view, allowing for easy comparison and analysis.

=== SQLTool Pro Database Editor ===

http://www.sqltoolpro.com

Android

SQLTool Pro is a professional Android SQL editor for MySQL, SQL Server, PostgreSQL, Sybase, and Oracle Databases.

=== SSIS Data Flow Components for PostgreSQL ===

https://www.devart.com/ssis/

Windows

'''Devart SSIS Data Flow Components for PostgreSQL''' allow you to integrate database and cloud data via SQL Server Integration Services (SSIS).

Devart SSIS Data Flow Components provide easy to set up cost-effective data integration using SSIS ETL engine. They provide high performance data loading, convenient component editors, SQL support for cloud data sources and lots of data source specific features.

=== DbVisualizer ===

http://www.dbvis.com/

Windows/OS X/Linux/UNIX

DbVisualizer is a feature rich, intuitive multi-database tool for developers, database administrators, and increasingly for advanced analysts providing a single powerful interface across a wide variety of operating systems. With its easy-to-use and clean interface, DbVisualizer has proven to be one of the most cost effective database tools available, yet to mention that it runs on all major operating systems and supports all major RDBMS that are available. Users only need to learn and master one application. DbVisualizer integrates transparently with the operating system being used.

[[Category:Tool]]
[[Category:General articles and guides]]

=== Valentina Studio (Free) ===

http://www.valentina-db.com/valentina-studio-overview

Windows/OS X/Linux/

Valentina Studio is a powerful PostgreSQL Database Server administration and development tool. It offers for free many advanced editors:
* Schema Editor with Tree and Column views
* Diagram Editor with reverse engineering
* SQL Editor with auto-completion, syntax-highlighting, recent and favorite queries, templates of commands, many result tab-panels, ...
* Data Editor with easy sorting and filtering of records without SQL, in-cell editing.
* Related Data Editor that allow s you to learn related records in different modes.
* Import/Export
* SQL dumps
* and so on ...

Valentina Studio PRO - adds additional advanced features as:
* Report Editor to developer reports based on Valentina Report Engine with datasources from PostgreSQL and other databases.
* Diagrams forward engineering
* SQL DIFF
* Data Transfer

[[Category:Tool]]

=== JackDB ===

http://www.jackdb.com/

Html5 Web Browser (Linux/Mac OS X/Windows)

JackDB is a database client that runs entirely in your web browser. There's no software to install locally so you can use it on Mac OS X, Linux, and Windows and it works on all major modern browsers (eg. Chrome, Firefox, IE, Safari, and Opera). It supports connecting to PostgreSQL, as well as MySQL, Oracle, and SQL Server databases.

Features:
* Html5 interface with no client installation
* Query editor with syntax highlighting
* Scrolling result sets
* Schema/Object browser
* SSL connections with certificate pinning
* Eliminates password sharing
* Two-factor authentication
* BLOB display (images and Html5 audio/video)

=== Tadpole DB Hub ===

https://github.com/hangum/TadpoleForDBTools/wiki

Tadpole DB Hub is Unified infrastructure tool, a various environment based interface for managing Apache Hive, Amazon RDS, CUBRID, MariaDB, MySQL, Oracle, SQLite, MSSQL, PostgreSQL and MongoDB databases. It enables you to handle typical DB over the World Wide Web.

Features:
* Intuitive web interface (Safari, Chrome, IE 10, Firefox)
* User Management (Admin, Manager, User)
* Select, Insert, Update, Delete
* Download query result
* SQL Syntax Highlighting
* SQL Formatting
* SQL Statement <-> Java, PHP String Literal Each Convert
* SQL Assist
* Execute SQL Statement
* SQL Result Set to CSV
* SQL History And Export text
* Generate SQL Statement (Select, Insert, Update, Delete, Table, View, Index, Procedure, Function, Trigger)
* Generate ER Diagram (Auto Layout)

=== Vertabelo ===

http://www.vertabelo.com

Vertabelo is an online database designer working under Chrome. It free to use for smaller projects and have a proprietary version for larger database projects.

Features:
* Intuitive HTML5 web interface (Chrome)
* OS independent
* Sharing DB model with team members
* Support for PostgreSQL, MySQL, Oracle, MS SQL Server, DB2, SQLite, HSQLDB,
* Model versioning
* Dynamic/Visual search
* Live model validation
* Reverse engineering

=== pgModeler ===

PostgreSQL Database Modeler

http://pgmodeler.com.br

PostgreSQL Database Modeler, or simply, pgModeler is an open source tool for modeling databases that merges the classical concepts of entity-relationship diagrams with specific features that only PostgreSQL implements. The pgModeler translates the models created by the user to SQL code and apply them onto database clusters from version 8.0 to 9.1. $3.50 per copy as of 2014/04/09.

=== GenMyModel ===

https://www.genmymodel.com

GenMyModel is an online modeling tool supporting [http://www.genmymodel.com/database-diagram-online database modeling]. It is free to use for smaller projects and have a proprietary version for larger database projects.

Features:
* Intuitive HTML5 web interface (Chrome, Firefox, Safari, Internet Explorer)
* OS independent
* Instant sharing and collaboration
* Customizable SQL generators
* Model versioning
* Live model validation

=== DBHawk ===

http://www.datasparc.com/

Web Browser (Linux/Mac OS X/Windows)

DBHawk is a web based SQL tool and reporting software designed for PostgreSQL, Oracle, SQL Server and other databases. Its easy to deploy and use.

Features:
* Web based interface with no client installation
* Advanced Query editor with syntax highlighting and multi tabs results
* Online visual query builder
* Online SQL Report Builder
* Online SQL Job Scheduler
* Export results to html, csv, pdf, google docs, amazon s3
* SQL Auditing and Security
* Schema/Object browser
* SQL and data snippet sharing
* Blob data viewer and editor

=== Datazenit ===

https://datazenit.com/

Windows, Mac OS X, Linux

Datazenit is a cross-platform PostgreSQL and MySQL GUI with data grid, schema builder and interactive charts.
It also has query builder, raw query editor with auto-complete, team collaboration features like connection, query and chart sharing among team members.

=== EDB Postgres Enterprise Manager ===

http://www.enterprisedb.com/products/postgres-enterprise-manager

Windows, Mac OS X, Linux

Postgres Enterprise Manager is the only solution available today that allows you to intelligently manage, monitor, and tune large scale Postgres installations from a single GUI console.

Monitoring features include: server auto-discovery, over 225 pre-configured ready to run probes, custom probes, alert management, personalized alerts, remote monitoring, versatile charting, custom dashboards and web client.

DBA tools include: database objects management, Postgres Expert (best practice configuration settings), Audit Manager, Log Manager, Log Analysis Expert, Capacity Manager and Team Support.

Developer tools include: Query Tool, Data Grid, SQL Profiler, SQL Debugger and Import tools.

Tuning tools include: At-A-Glance performance dashboards, Tuning Wizard, Performance Diagnostics and Index Advisor.

=== ClusterControl by Severalnines ===

https://severalnines.com/product/clustercontrol/for_postgresql

ClusterControl is an all-inclusive open source database management system that allows you to deplore, monitor, manage and scale your database environments. ClusterControl provides the basic functionality you need to get PostgreSQL up-and-running using our deployment wizard, monitoring and basic management abilities like automatic failover, backups, and restores.

* Point and Click Replication Deployments - ClusterControl allows you to easily deploy and configure master/slave replication PostgreSQL instances.
* Advanced Performance Monitoring - ClusterControl monitors queries and detects anomalies with built-in alerts.
* Automated Failover Handling - ClusterControl detects master failures and automatically promotes a new master
* Database Automation - ClusterControl lets you manage configurations, schedule, and restore backups.

== No longer Supported/Developed ==

* OpenOffice postgresql SDBC Driver. no work on the project since 2010; last version was a beta. http://www.openoffice.org/dba/drivers/postgresql/index.html
* RedHat: hasn't been refreshed since Pg 8.4. http://sources.redhat.com/rhdb
* SQuirrel: website 404. http://squirrel-sql.sourceforge.net/

PostgreSQL Clients

2018-08-20T01:29:48Z

Dfetter:

This page is a partial list of interactive SQL clients - that doesn't include reporting engines, ETL data loaders, visual design tools, just interactive clients that you can type SQL in to and get results from them.

== CLI Clients ==

=== Open Source / Free Software ===

==== psql ====

https://www.postgresql.org/docs/current/static/app-psql.html

The standard command line client, maintained by the postgresql development group and typically distributed as part of the server installation.

==== pgcli ====

https://www.pgcli.com

A command line client with syntax highlighting and pop-up command completion.

==== jaqy ====

https://teradata.github.io/jaqy/

A universal JDBC command line client with lots of features. It is not specific to PostgreSQL, but it is pre-configured to handle PostgreSQL servers. Requires PostgreSQL JDBC driver.

== macOS GUI Clients ==

=== Open Source / Free Software ===

==== Postbird ====

https://github.com/paxa/postbird

Open source, desktop application to manage your local or remote PostgreSQL databases.

=== Proprietary ===

==== SQLPro for Postgres ====

http://www.macpostgresclient.com/SQLProPostgres

macOS 10.8 and above

100% native OS X app with a clean and simple to use interface. Query editor with syntax highlighting and autocomplete.

==== TablePlus ====

https://tableplus.io/

A modern, native client for relational databases with nice UI and very convenient query editor. It's compatible with all versions of Postgres.

==== Postico ====

https://eggerapps.at/postico/

A nice native client by the developers of [http://postgresapp.com Postgres.app]. A free "demo" version of an inexpensive proprietary app, but it has very reasonable limits and no time limit.

==== pgEdit ====

http://pgedit.com

Not a standalone client, rather a plugin for [https://macromates.com Textmate] for using psql.

==== PSequel ====

http://www.psequel.com/

OS X Yosemite only, free, "Sequel Pro" inspired.

==== SEQUEL for PostgreSQL ====

http://www.sequel.tech

SEQUEL for PostgreSQL is a professional DB administration and management tool, with extremely intuitive and feature rich GUI that makes it the best assistant tool for developers and admins. SEQUEL is lightweight, fast and powerful that it can significantly simplify the DB management process. For those who cannot live without a CLI, SEQUEL offers a powerful Query Editor with syntax highlight, autocomplete and a Console log view that is always visible, so you can monitor the communication with your databases.

== Windows GUI Clients ==

=== Open Source / Free Software ===

=== Proprietary ===

==== DBTools Manager ====

http://www.dbtools.com.br

Freeware, available for PostgreSQL and MySQL, allows managing all aspects of the database: db, table, triggers, functions, etc. Includes import/export wizards to migrate data and structure to/from other database engines.

==== EMS SQL Manager for PostgreSQL Freeware ====

http://www.sqlmanager.net/en/tools/free

EMS SQL Manager for PostgreSQL Freeware (EMS SQL Manager Lite for PostgreSQL) is an excellent and easy-to-use freeware graphical tool for PostgreSQL database administration. It has the minimal required set of tools for those users who are new to PostgreSQL server and need only its basic functionality.

There is a proprietary version available with significantly more functionality.

==== Marshal SQL Utility ====

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1756

The Marshal SQL Utility is a generic cross database utility with batch execution capabilities. It allows you to test ODBC connections, browse database schemas, discover tables, views and columns.

==== dbForge Studio for PostgreSQL ====

https://www.devart.com/dbforge/postgresql/studio/

dbForge Studio for PostgreSQL is a GUI tool for managing and developing databases and objects. The PostgreSQL IDE allows users to create, develop, and execute queries, edit and adjust the code to your requirements in a convenient and UI. The tool provides a data editing tool to customize your queries and property window so that users can view all the required information of PostgreSQL database objects they are interested in.

==== AnySQL Maestro ====

http://www.sqlmaestro.com/products/anysql/maestro/

AnySQL Maestro is a freeware tool for administering any database engine (PostgreSQL, SQL Server, Oracle, MySQL, MS Access, etc.), which is accessible via ODBC driver or OLE DB provider. Includes Database Designer, Visual Query Builder, BLOB Viewer/Editor, SQL Editor, Data export/import and other features.

==== PostgreSQL Maestro ====

https://www.sqlmaestro.com/products/postgresql/maestro/

Allows you to create, edit, copy, drop and dump database objects easy and fast. You can also design your database as ER diagram, build queries visually, execute SQL queries and scripts, debug PL/pgSQL functions, view and edit data including BLOBs, represent data as diagrams, export and import data to/from most popular file formats, analyze your data summarized into multidimensional views and hierarchies (OLAP cubes), manage PostgreSQL roles, users, groups and privileges, and use a lot of other admin tools designed for making your work with PostgreSQL database server comfortable and efficient.

==== Access ====

https://products.office.com/en-us/access

Yes, you can use MS Access as a PostgreSQL database interface. Supports data access to PostgreSQL tables and views; many ODBC-based limitations and errors.

==== VSQL++ for PostgreSQL ====

http://www.sqlpp.com/products/postgresql-management/

A powerful Postgresql database management tool to help DBA sto manage the database objects easy and quickly.

==== Nucleon Database Master ====

http://nucleonsoftware.com/products/database-master

Supports PostgreSQL MongoDB, Oracle, DB2, Informix, Ingres, SQL Server, SQL Azure, MySQL, FireBird, SQLite

==== SQLPro ====

http://www.vive.net/products/sqlpro.htm

SqlPro is an easy to use database GUI tool for six popular databases (Oracle, MySQL, PostgreSQL, SQL Server, SQLite and Access). One IDE makes database administration and development faster and error free.
SQLPro Key Features: color-coding of the SQL, drag-and-drop of objects into the editor pane to save you from typing their names, retrieval of SQL code for things like stored procedures and triggers from the underlying database, and one-click creation of SELECT and INSERT statements. You can open, save and print SQL scripts.

=== Obsolete or End-of-Life ===

==== PGExplorer ====

http://www.PGExplorer.com

Hasn't been significantly updated in many years, but latest downloads suggest it may support Postgresql 9.* to some extent.

== Linux / Unix GUI Clients ==

=== Open Source / Free Software ===

==== Gnome DB ====

http://www.gnome-db.org

Database administration/user tool for GNOME, based on libgda/libgnomedb, which are a complete database-independent access layer for UNIX systems, with support for PostgreSQL, MySQL, Sybase, MS SQL Server, Oracle, Interbase/Firebird, MS Access files, xBase.

Has an experimental Windows build available too.

==== Kexi ====

http://www.kexi-project.org/

A visual database application creator, c.f. Access or FileMaker

== Cross-platform GUI Clients ==

=== Open Source / Free Software ===

==== pgAdmin 3 ====

http://www.pgadmin.org/

Windows, Linux, FreeBSD, macOS, OpenBSD, Solaris

For many years the "standard" freely available GUI client for Postgresql, and so is bundled in many packaged installers. It provides a SQL query tool, an editor for procedural languages and a CRUD interface. It's also one of the few clients to provide a GUI front end to the plpgsql debugger.

Development has been discontinued by pgadmin.org, but it is still being maintained by BigSQL who are doing basic maintenance to support current versions of PostgreSQL and packaging it for current OS releases [[https://www.openscg.com/bigsql/pgadmin3/index.jsp/ here]]

==== pgAdmin 4 ====

http://www.pgadmin.org/

Windows, macOS, [https://yum.postgresql.org rpm], Python

pgAdmin 4 is a ground-up rewrite of pgAdmin 3. Rather than being a native application it's primarily a web application that's also packaged as desktop web shell. At the time of writing it's considered inferior to pgAdmin 3 both in terms of functionality and stability.

==== LibreOffice Base ====

http://www.libreoffice.org/discover/base/

Supports MySQL/MariaDB, Adabas D, MS Access and PostgreSQL, as well as other JDBC/ODBC databases.

==== Tora ====

http://tora.sf.net/

Linux, Windows, macOS

Oracle, MySQL, and PostgreSQL, as well as limited support for ODBC targets. Inspired by the proprietary Toad client.

==== SQL Workbench/J ====

http://www.sql-workbench.net

Java

An OpenSource (though it prohibits usage by government agencies from USA, UK, Canada, China, Russia, North Korea, Syria, Saudi Arabia, Turkey and the Chechen Republic) SQL GUI tool similar to Squirrel. Data can be edited directly in the result set. It has strong support for exporting and importing data between databases using its own SQL command extension. It can be used in GUI mode or as a console application. All SQL Workbench specific commands can also be run in batch mode to automate export and import task. It supports schema comparison ("diff") and copying data between databases.

It has some [http://sql-workbench.net/manual/license.html#license-restrictions restrictions] on use by government employees.

==== Druid III ====

http://druid.sourceforge.net/

Java

The druid is a tools that allows users to create databases in a graphical way. The user can add tables, fields, folders to group tables and can modify most of the database options that follow the SQL-92 standard. In addition to sql options, the user can document each table and each field with HTML information.

==== Power*Architect ====

http://www.sqlpower.ca/page/architect

Java

Power*Architect is an ERD modelling tool that is based on Java and JDBC. Support for forward and reverse engineering PostgreSQL databases is supported. It's OpenSource with a GPL license.

==== DBeaver ====

http://dbeaver.jkiss.org/

Eclipse/Java

Eclipse-based environment, supporting many SQL databases from different vendors, as well as few NoSQL ones (Cassandra, etc).
Good query editor with syntax highlighting, completion and autosave.
Editing of query results. SSH tunneling support. Tons of other cool features.
Quite good, but not 100% perfect PostgreSQL support (yet?). Regularly updated, as of 2018.

==== pgManage ====

https://github.com/pgManage/pgManage

An alternative to pgAdmin, which runs in both application and server modes.

=== Proprietary ===

==== Valentina Studio (Free) ====

http://www.valentina-db.com/valentina-studio-overview

Windows/OS X/Linux

Valentina Studio is a powerful PostgreSQL Database Server administration and development tool.

There is a proprietary version available with additional functionality.

==== RazorSQL ====

http://www.razorsql.com/

Macintosh/Windows/Linux/Solaris

RazorSQL is an SQL query tool, database browser, SQL editor, and database administration tool that supports PostgreSQL and any other JDBC or ODBC compliant database. Some of the major features are tools for creating, dropping, and altering objects such as tables, views, indexes, triggers, functions, users, and databases; a programming editor that supports 20 different programming languages; import and export tools; auto column and table lookup; and a query builder, query scheduler, and SQL formatter.

==== JetBrains DataGrip ====

https://www.jetbrains.com/datagrip/

Windows, macOS, Linux

JetBrains has a dedicated SQL IDE — DataGrip which can connect to PostgreSQL as well. It provides code completion, multicursors, local query history, navigation, refactorings and language injection support.

Other JetBrains IDEs have plugins available to provide similar functionality.

==== Aqua Data Studio ====

http://www.aquafold.com/index-postgresql.html

Java: Windows/Linux/macOS/Solaris

Aqua Data Studio is a management tool for the PostgreSQL relational database w/ administration capabilities and a database query tool. The visual administration features provide users the ability to browse and modify database structures, including schema objects, database storage and maintain database security. An integrated query tool allows users to quickly create, edit and execute SQL queries and scripts. Aqua Data Studio also provides an import and export tool to allow users to easily move data in and out of the PostgreSQL database in and from different data formats.

==== Navicat ====

https://www.navicat.com/en/products/navicat-for-postgresql

Windows, macOS, iOS

Navicat is a powerful PostgreSQL Database Server administration and development tool. It works with PostgreSQL 8.0 version or above and supports most of the PostgreSQL features including Trigger, Function, View, Manage User, and so on. It is also not only sophisticated enough for professional developers, but also easy to learn for new users. With its well-designed GUI, Navicat lets you quickly and easily create, organize, access and share information in a secure and easy way.

==== DbVisualizer ====

http://www.dbvis.com/

Windows/macOS/Linux/UNIX

DbVisualizer is a feature rich, intuitive multi-database tool for developers, database administrators, and increasingly for advanced analysts providing a single powerful interface across a wide variety of operating systems. With its easy-to-use and clean interface, DbVisualizer has proven to be one of the most cost effective database tools available, yet to mention that it runs on all major operating systems and supports all major RDBMS that are available. Users only need to learn and master one application. DbVisualizer integrates transparently with the operating system being used.

==== Datazenit ====

https://datazenit.com/

Windows, Mac OS X, Linux

Datazenit is a cross-platform PostgreSQL and MySQL GUI with data grid, schema builder and interactive charts.
It also has query builder, raw query editor with auto-complete, team collaboration features like connection, query and chart sharing among team members.

Web-based, but available packaged as a desktop app.

== Android ==

=== Proprietary ===

==== SQLTool Pro Database Editor ====

http://www.sqltoolpro.com

SQLTool Pro is a professional Android SQL editor for MySQL, SQL Server, PostgreSQL, Sybase, and Oracle Databases. JDBC.

== Web Clients ==

=== Open Source / Free Software ===

==== franchise ====

https://franchise.cloud/

Web client, either hosted (free) or running locally, connects to a local postgresql instance via a small bridge application.

Can share the interface with others, rather like sqlfiddle.com, but accessing your database.

==== pgAdmin 4 ====

http://www.pgadmin.org/

Python

pgAdmin 4 is a ground-up rewrite of pgAdmin 3. Rather than being a native application it's primarily a web application that's also packaged as desktop web shell. At the time of writing it's considered inferior to pgAdmin 3 both in terms of functionality and stability.

==== TeamPostgreSQL ====

http://www.teampostgresql.com

browser-based, webserver included

AJAX/JavaScript-powered web interface for PostgreSQL administration. Browse, maintain and create data and database objects from anywhere, in the web browser. Supports SSH for both the web interface and the database connections. Rich interface with tabbed SQL editor with auto-completion, inline row-editing widgets, click-through foreign key navigation between rows and tables, 'favorites' management for commonly used scripts, and more.

Installers available for Windows, Mac and Linux, alternatively download a simple cross-platform archive that runs anywhere with simple script.

==== Adminer ====

http://www.adminer.org

PHP

Adminer (formerly phpMinAdmin) is a full-featured database management tool written in PHP. A single PHP file ready to deploy to the target server. Adminer is available for MySQL, PostgreSQL, SQLite, MS SQL and Oracle.

==== OmniDB ====

https://github.com/OmniDB/OmniDB

Django/Python

Open source full-featured web tool for database management. Currently supports PostgreSQL only. More RDBMS support coming soon, including the ability of converting databases from any supported RDBMS to PostgreSQL and back.

==== Tadpole DB Hub ====

https://github.com/hangum/TadpoleForDBTools/wiki

Tadpole DB Hub is Unified infrastructure tool, various environment based interface for managing Apache Hive, Amazon RDS, CUBRID, MariaDB, MySQL, Oracle, SQLite, MSSQL, PostgreSQL and MongoDB databases. It enables you to handle typical DB over the World Wide Web.

==== SIDU ====

http://topnew.net/sidu/

PHP

Schema and data browser and editor.

=== Proprietary ===

==== JackDB ====

http://www.jackdb.com/

Html5 Web Browser (Linux/Mac OS X/Windows)

JackDB is a database client that runs entirely in your web browser. There's no software to install locally so you can use it on Mac OS X, Linux, and Windows and it works on all major modern browsers (eg. Chrome, Firefox, IE, Safari, and Opera). It supports connecting to PostgreSQL, as well as MySQL, Oracle, and SQL Server databases.

A hosted service, so it requires external access to your database.

==== DBHawk ====

https://www.datasparc.com/dbhawk/

DBHawk is a web based SQL tool and reporting software designed for PostgreSQL, Oracle, SQL Server and other databases. Its easy to deploy and use.

Query editor, report builder, schema and data browser.

==== Datazenit ====

https://datazenit.com/

Java

Datazenit is a cross-platform PostgreSQL and MySQL GUI with data grid, schema builder and interactive charts.
It also has query builder, raw query editor with auto-complete, team collaboration features like connection, query and chart sharing among team members.

Web-based, but available packaged as a desktop app.

=== Obsolete or End-of-Life ===

==== phpPgAdmin ====

http://phppgadmin.sourceforge.net/doku.php

PHP

Similar to phpMyAdmin, enhanced for PostgreSQL, supports browsing and modification of most types of PostgreSQL database objects, plus execution of ad-hoc queries.

(last updated 2013, 9.2.x)

== Other Resources ==

[[Community Guide to PostgreSQL GUI Tools]] - the source for a lot of this page. Includes many non-client tools, such as bulk loaders, schema diff, schema design, etc.

[http://www.postgresonline.com/journal/index.php?/archives/133-Database-Administration,-Reporting,-and-Light-application-development.html Database Administration, Reporting, and Light application development] - from 2009

[[GUI Database Design Tools]] - tools for designing database schemas

Ecosystem:High Availability (HA)

2018-08-20T01:26:43Z

Dfetter: /* EDB Postgres Failover Manager */

== EDB Postgres Failover Manager ==

* Provider -- EnterpriseDB
* Website -- https://www.edbpostgres.com
* License -- Proprietary
* Interoperability level -- explicitly supports PostgreSQL 9.5 or higher
* Verified PostgreSQL versions -- See: https://www.enterprisedb.com/services/edb-supported-products-and-platforms#EFM
* Last update (YYYY-MM-DD) -- See: https://www.enterprisedb.com/services/edb-supported-products-and-platforms#EFM
* Description -- Failover Manager creates highly available fault tolerant clusters minimizing database downtime with health monitoring, failure detection/notification, and automatic failover required in stringent 9s based high availability solutions. A simple and lightweight architecture without a single point of failure protects against a variety of failure scenarios that can be customized to specific application needs.
* Additional info -- https://www.enterprisedb.com/products/edb-postgres-platform/edb-postgres-failover-manager

Monitoring

2018-08-20T01:15:48Z

Dfetter:

{{Languages}}

== PostgreSQL builtin & contrib ==

=== Statistics collector ===

PostgreSQL collects lots of data on its own and offers it via the <tt>pg_stat(io)_</tt> system views

* Official documentation on the [http://www.postgresql.org/docs/current/static/monitoring-stats.html Statistics Collector]
* [http://www.varlena.com/GeneralBits/107.php Interpreting pg_stat Views]

=== contrib extensions ===

The following extensions offer access to Postgres internals which may be of interest or collect additional information. Most of them are shipped with Postgres (the <tt>-contrib</tt> packages may need to be installed) and can be activated via the [http://www.postgresql.org/docs/current/static/sql-createextension.html extension interface].

==== pg_stat_statements ====

<tt>[http://www.postgresql.org/docs/current/static/pgstatstatements.html pg_stat_statements]</tt> tracks all queries that are executed on the server and records average runtime per query "class" among other parameters.

==== pg_stat_plans ====

<tt>[https://github.com/2ndQuadrant/pg_stat_plans pg_stat_plans]</tt> extends on pg_stat_statements and records query plans for all executed quries. This is very helpful when you're experiencing performance regressions due to inefficient query plans due to changed parameters or table sizes.

==== pgstattuple ====

<tt>[http://www.postgresql.org/docs/current/static/pgstattuple.html pgstattuple]</tt> can generate statistics for tables and indexes, showing how much space in each table & index is consumed by live tuples, deleted tuples as well as how much unused space is available in each relation.

==== pg_buffercache ====

<tt>[http://www.postgresql.org/docs/current/static/pgbuffercache.html pg_buffercache]</tt> gives you introspection into Postgres' [http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-SHARED-BUFFERS shared buffers], showing how many pages of which relations are currently held in the cache.

== External projects ==

=== CLI tools ===

==== pg_view ====

<tt>[https://github.com/zalando/pg_view/ pg_view]</tt> is a Python-based tool to quickly get information about running databases and resources used by them as well as correlate running queries and why they might be slow.

==== pg_activity ====

<tt>[https://github.com/julmon/pg_activity pg_activity]</tt> is a htop like application for PostgreSQL server activity monitoring, written in Python.

==== pgmetrics ====

<tt>[https://pgmetrics.io/ pgmetrics]</tt> collects a lot of information and statistics from a running PostgreSQL server and displays it in easy-to-read text format or export it as JSON for scripting.

==== pgstats ====

<tt>[https://github.com/gleu/pgstats pgstats]</tt> is a command line tool written in C which can sample various PostgreSQL informations. It also provides a tool to generate CSV files to graph the pgstats metrics.
=== Checkers ===

==== check_postgres ====

<tt>[http://bucardo.org/wiki/Check_postgres check_postgres]</tt> is a command line tool which is designed to be run from software like Icinga, MRTG or as a standalone tool. It can monitor many aspects of the database and trigger warnings when thresholds are violated.

=== Interfaces & collectors ===

These tools either offer an interface to PostgreSQL monitoring-relevant data or can aggregate and prepare them for other systems.

==== pgsnmpd ====

<tt>[http://pgsnmpd.projects.postgresql.org/ pgsnmpd]</tt> can run as a standalone SNMP server and implements the [http://www.faqs.org/rfcs/rfc1697.html RFC 1697 MIB] which is generic RDBMS [http://en.wikipedia.org/wiki/Management_information_base MIB]

This is useful for network management systems which are limited to SNMP protocol.

==== pganalyze/collector ====

<tt>[https://github.com/pganalyze/collector pganalyze/collector]</tt> is a tool which collects <tt>pg_stat_plans</tt> query information as well as various performance-relevant database parameters and converts them into a JSON structure for easy ingestion in other systems.

=== Generic monitoring solutions with plugins ===

==== Zabbix ====

[http://pg-monz.github.io/pg_monz/index-en.html pg_monz] is a [http://www.zabbix.com/ Zabbix] monitoring template for PostgreSQL.

[http://cavaliercoder.github.io/libzbxpgsql/ libzbxpgsql] is a [http://www.zabbix.com/ Zabbix] monitoring template and native agent module for PostgreSQL.

==== Munin ====

PostgreSQL Plugins developed in Perl are included in the Core [http://munin-monitoring.org/ Munin] Distribution. The following plugins are included by default: <tt>postgres_bgwriter, postgres_locks_, postgres_tuples_, postgres_cache_, postgres_querylength_, postgres_users, postgres_checkpoints, postgres_scans_, postgres_xlog, postgres_connections_, postgres_size_, postgres_connections_db, postgres_transactions_</tt>

[http://aouyar.github.com/PyMunin/ PyMunin] includes a Multigraph Munin Plugin written in Python that implements the following graphs: <tt>pg_connections, pg_diskspace, pg_blockreads, pg_xact, pg_tup_read, pg_tup_write, pg_blockreads_detail, pg_xact_commit_detail, pg_xact_rollback_detail, pg_tup_return_detail, pg_tup_fetch_detail, pg_tup_delete_detail, pg_tup_update_detail, pg_tup_insert_detail</tt>

==== NewRelic ====

[http://newrelic.com/ NewRelic] is a proprietary SaaS application monitoring solution which offers a [https://newrelic.com/plugins/enterprisedb-corporation/30 PostgreSQL plugin] maintained by EnterpriseDB.

====Datadog====
[http://www.datadoghq.com/ Datadog] is a proprietary saas that collects postgres metrics on connections, transactions, row crud operations, locks, temp files, bgwriter, index usage, replication status, memory, disk, cpu and lets you visualize and alert on those metrics alongside your other system and application metrics.

==== Circonus ====
[https://www.circonus.com Circonus] is a general purpose monitoring, analytic and alerting saas that has predefined queries for postgres to monitor some of the common metrics and checks like connections, transactions, WALs, vacuum and table stats. More information can be found [https://login.circonus.com/resources/docs/user/Data/CheckTypes/PostgreSQL.html here]

====ClusterControl by Severalnines====

[https://severalnines.com/product/clustercontrol/for_postgresql ClusterControl] is an all-inclusive open source database management system that allows you to deploy, monitor, manage and scale your database environments. ClusterControl provides the basic functionality you need to get PostgreSQL up-and-running using the deployment wizard. It offers Advanced Performance Monitoring - ClusterControl monitors queries and detects anomalies with built-in alerts. Deployment and monitoring are free, with management features as part of a paid version.

==== Cacti ====

There has been work done on building a Postgres template for [http://www.cacti.net/ Cacti], Details can be found at the [[Cacti]] page.

====Okmeter====

[http://okmeter.io/pg Okmeter.io] is a proprietary SaaS that collects a whole lot of PostgreSQL status and operational data: over 50 types of metrics on connections, transactions, table CRUD operations, locks, bgwriter, index usage and ops, replication, autovacuum. Also, query timings, disk and CPU usage by queries from pg_stat_statements, and system metrics — CPU, memory, fd and disk usage per process, socket connections per port and tcp status. Collecting the data requires minimal to no configuration, there's pre-built [https://okmeter.io/example/hosts/db-postgresql1/Postgresql chart dashboards], detailed query reports and pre-set alerts, that will notify you if something's wrong with you DB. [https://okmeter.io/pg?lang=en More information here] and [https://okmeter.io/i/integrations/postgresql-monitoring?lang=en detailed info of what's collected - here.]

=== Postgres-centric monitoring solutions ===

==== EnterpriseDB Postgres Enterprise Manager ====

[http://www.enterprisedb.com/products-services-training/products/postgres-enterprise-manager Postgres Enterprise Manager] monitors, alerts, manages and tunes local and remote large scale Postgres deployments from a single graphical console. Out of the box features include: server auto-discovery, point and click management of database objects, 225+ pre-configured database alerts by SMTP/SNMP, custom alerts, global At-a-Glance monitoring dashboards, Performance monitoring dashboards, custom dashboards, an Audit Manager, Postgres Expert best practice configuration recommendations, a Log Manager, a Log Analyzer Expert, a SQL Profiler, and Index Advisor.

==== pganalyze ====

[https://pganalyze.com/ pganalyze] is a proprietary SaaS offering which focuses on performance monitoring and automated tuning suggestions.

==== pgwatch2 ====

[https://github.com/cybertec-postgresql/pgwatch2 pgwatch2] is a self-contained, easy to install and highly configurable PostgreSQL monitoring tool. It is dockerized, features a dashboard and can send alerts. No extensions or superuser privileges required!

==== pg_statsinfo & pg_stats_reporter ====

[http://pgstatsinfo.sourceforge.net/ pg_statsinfo] is a Postgres extension that collects lots of performance-relevant information inside the Postgres server which then can be aggregated by pg_stats_reporter instances which provide a web interface to the collected data. Both are FOSS software maintained by NTT.

==== PGObserver ====

[http://zalando.github.io/PGObserver/ PGObserver] is a Python & Java-based Postgres monitoring solution developed by Zalando. It was developed with a focus on stored procedure performance but extended well beyond that.

==== pgCluu ====

[http://pgcluu.darold.net/ pgCluu] is a Perl-based monitoring solution which uses psql and [http://en.wikipedia.org/wiki/Sar_(Unix) sar] to collect information about Postgres servers and render comprehensive performance stats.

==== PoWA ====

[http://dalibo.github.io/powa/ PoWA] is a PostgreSQL Workload Analyzer that gathers performance stats and provides real-time charts and graphs to help monitor and tune your PostgreSQL servers. It relies on extensions such as pg_stat_statements, pg_qualstats, pg_stat_kcache, pg_track_settings and HypoPG, and can help you optimize you database easily.

==== OPM: Open PostgreSQL Monitoring ====

[http://opm.io Open PostgreSQL Monitoring (OPM)] is a free software suite designed to help you manage your PostgreSQL servers. It's a flexible tool that will follow the activity of each instance. It can gather stats, display dashboards and send warnings when something goes wrong. The long-term goal of the project is to provide similar features to those of Oracle Grid Control or SQL Server Management Studio.

==== PASH-Viewer: PostgreSQL Active Session History Viewer ====

[https://github.com/dbacvetkov/PASH-Viewer PASH-Viewer] is a free open-source software which provides graphical view of active session history and help you to answer questions like "What wait events were taking most time?", "Which sessions were taking most time?", "Which queries were taking most time and what were they doing?". It also supports Active Session History extension by pgsentinel.

[[Category:Monitoring|!]]
[[Category:Performance]]

Replication, Clustering, and Connection Pooling

2018-08-13T15:33:45Z

Dfetter:

==Introduction==
There are many approaches available to scale PostgreSQL beyond running on a single server. An outline of the terminology and basic technologies involved is at [http://www.postgresql.org/docs/current/interactive/high-availability.html High Availability and Load Balancing]. There is a [http://momjian.us/main/writings/pgsql/replication.pdf presentation] covering some of these solutions.

There is no one-size fits all replication software. You have to understand your requirements and how various approaches fit into that. For example, here are two extremes in the replication problem space:

* You have a few servers connected to a local network you want to always keep current for failover and load-balancing purposes. Here you would be considering solutions that are synchronous, eager, and therefore conflict-free.
* Your users take a local copy of the database with them on laptops when they leave the office, make changes while they are away, and need to merge those with the main database when they return. Here you'd want an asynchronous, lazy replication approach, and will be forced to consider how to handle conflicts in cases where the same record has been modified both on the primary server and on a local copy.

These are both database replication problems, but the best way to solve them is very different. And as you can see from these examples, replication has a lot of specific terminology that you'll have to understand to figure out what class of solution makes sense for your requirements. A great source for this background is in the
[http://www.postgres-r.org/documentation/terms Postgres-R Terms and Definitions for Database Replication]. The main theoretical topic it doesn't mention is how to resolve conflict resolution in lazy replication cases like the laptop situation, which involves voting and similar schemes.

== Features in the Core of PostgreSQL ==

*[[Hot Standby]]/[[Streaming Replication]] is available as of PostgreSQL 9.0 and provides asynchronous binary replication to one or more standbys. Standbys may also become hot standbys meaning they can be queried as a read-only database. This is the fastest type of replication available as WAL data is sent immediately rather than waiting for a whole segment to be produced and shipped.

*[[Warm Standby]]/Log Shipping is a HA solution which 'replicates' a database cluster to an archive or a warm (can be brought up quickly, but not available for querying) standby server. Overhead is very low and it's easy to set up. This is a simple and appropriate solution if all you care about is continuous backup and short failover times.

* PostgreSQL 9.4's [[Logical Changeset Extraction]] forms the foundation of the [[Bi-Directional Replication]] and [[Logical Log Streaming Replication]] features being added to PostgreSQL.

Historically, the PostgreSQL core team considered replication and clustering technology outside the scope of the main project's focus but this changed in 2008, see the [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00913.php Core Team's statement]. Replication is now a significant focus of ongoing PostgreSQL development.

==Comparison matrix==

This page is being overhauled at [[Clustering]]

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-layout: fixed;"
|- style="background: #ececec"
! Program
! License
! Maturity
! Replication Method
! Sync
! Connection Pooling
! Load Balancing
! Query Partitioning
|-
! style="text-align:block;" bgcolor="#ececec" | [[PgCluster]]
| bgcolor="#ffffaa" | BSD
| bgcolor="#ffffaa" | Not production ready
| bgcolor="#ffffaa" | Master-Master
| bgcolor="#ffffaa" | Synchronous
| bgcolor="#ffaaaa" | No
| bgcolor="#ddffdd" | Yes
| bgcolor="#ffaaaa" | No
|-
! style="text-align:block;" bgcolor="#ececec" | '''pgpool-I'''
| bgcolor="#ffffaa" | BSD
| bgcolor="#ffffaa" | Stable
| bgcolor="#ffffaa" | Statement-Based Middleware
| bgcolor="#ffffaa" | Synchronous
| bgcolor="#ddffdd" | Yes
| bgcolor="#ddffdd" | Yes
| bgcolor="#ffaaaa" | No
|-
! style="text-align:block;" bgcolor="#ececec" | [[Pgpool-II]]
| bgcolor="#ffffaa" | BSD
| bgcolor="#ffffaa" | Recent release
| bgcolor="#ffffaa" | Statement-Based Middleware
| bgcolor="#ffffaa" | Synchronous
| bgcolor="#ddffdd" | Yes
| bgcolor="#ddffdd" | Yes
| bgcolor="#ddffdd" | Yes
|-
! style="text-align:block;" bgcolor="#ececec" | [[slony]]
| bgcolor="#ffffaa" | BSD
| bgcolor="#ffffaa" | Stable
| bgcolor="#ffffaa" | Primary-Replica
| bgcolor="#ffffaa" | Asynchronous
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
|-
! style="text-align:block;" bgcolor="#ececec" | [[Bucardo]]
| bgcolor="#ffffaa" | BSD
| bgcolor="#ffffaa" | Stable
| bgcolor="#ffffaa" | Master-Master, Primary-Replica
| bgcolor="#ffffaa" | Asynchronous
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
|-
! style="text-align:block;" bgcolor="#ececec" | [[Londiste]]
| bgcolor="#ffffaa" | BSD
| bgcolor="#ffffaa" | Stable
| bgcolor="#ffffaa" | Primary-Replica
| bgcolor="#ffffaa" | Asynchronous
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
|-
! style="text-align:block;" bgcolor="#ececec" | [[Mammoth]]
| bgcolor="#ffffaa" | BSD
| bgcolor="#ffffaa" | No longer maintained
| bgcolor="#ffffaa" | Primary-Replica
| bgcolor="#ffffaa" | Asynchronous
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
|-
! style="text-align:block;" bgcolor="#ececec" | [[rubyrep]]
| bgcolor="#ffffaa" | MIT
| bgcolor="#ffffaa" | No longer maintained
| bgcolor="#ffffaa" | Master-Master, Primary-Replica
| bgcolor="#ffffaa" | Asynchronous
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
|-
! style="text-align:block;" bgcolor="#ececec" | [https://2ndquadrant.com/en/resources/bdr/ Bi-Directional Replication]
| bgcolor="#ffffaa" | PostgreSQL (BSD)
| bgcolor="#ffffaa" | Recent release
| bgcolor="#ffffaa" | Master-Master (no triggers needed)
| bgcolor="#ffffaa" | Asynchronous
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
|-
! style="text-align:block;" bgcolor="#ececec" | [https://www.citusdata.com/citus-products/pg-shard pg_shard]
| bgcolor="#ffffaa" | LGPL
| bgcolor="#ffffaa" | Recent release
| bgcolor="#ffffaa" | Statement-based Middleware (as an extension)
| bgcolor="#ffffaa" | Synchronous
| bgcolor="#ffaaaa" | No
| bgcolor="#ddffdd" | Yes
| bgcolor="#ddffdd" | Yes
|-
! style="text-align:block;" bgcolor="#ececec" | [http://2ndquadrant.com/resources/pglogical pglogical]
| bgcolor="#ffffaa" | PostgreSQL
| bgcolor="#ffffaa" | Recent release
| bgcolor="#ffffaa" | Primary-Replica
| bgcolor="#ffffaa" | Asynchronous
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
| bgcolor="#ffaaaa" | No
|-
! style="text-align:block;" bgcolor="#ececec" | [http://postgres-xl.org/ Postgres-XL]
| bgcolor="#ffffaa" | PostgreSQL
| bgcolor="#ffffaa" | Recent release
| bgcolor="#ffffaa" | MPP Postgres, scalable writes & reads
| bgcolor="#ffffaa" | Synchronous
| bgcolor="#ddffdd" | Yes
| bgcolor="#ddffdd" | Yes
| bgcolor="#ddffdd" | Yes
|-
! style="text-align:block;" bgcolor="#ececec" | [https://www.citusdata.com/ Citus]
| bgcolor="#ffffaa" | AGPL
| bgcolor="#ffffaa" | Recent release
| bgcolor="#ffffaa" | MPP Postgres, scalable writes & reads
| bgcolor="#ffffaa" | Asynchronous or Synchronous
| bgcolor="#ddffdd" | Yes
| bgcolor="#ddffdd" | Yes
| bgcolor="#ddffdd" | Yes
|}

==Replication==

Aside from the in-core streaming replication, mentioned above...

*Slony-I: Seems good, single primary only, primary is a single point of failure, no good failover system for electing a new primary or having a failed primary rejoin the cluster. Replica databases are mostly for safety or for parallelizing queries for performance. Suffers from O(N^2) communications (N = cluster size). with reasonable sysadmin you can implement failover system yourself. regarding communications, you can cascade the replication to reduce load on the primary. If you were implementing a large replication cluster, this would probably be a good idea. Slony is powerful, trigger based, and highly configurable.

* PGCluster: PGCluster (which, incidentally, is not the same as PGCluster-II, a shared-disk solution), which does synchronous multimaster replication. Two single-points failure spots, load balancer and the data replicator. The project has historically looked a bit dead, but they just released a new version and http://pgfoundry.org/projects/pgcluster is up to date (at least downloads page) One major downside to PGCluster is that it uses a modified version of PostgreSQL, and it usually lags a few releases behind.

* http://www.pgpool.net/ pgpool 1/2 is a reasonable solution. it's statement level replication, which has some downsides, but is good for certain things. pgpool 2 has a neat distributed table mechanism which is interesting. You might want to be looking here if you have extremely high ratios of read to write but need to service a huge transaction volume. Supports load-balancing and replication by implementing a proxy that duplicates all updates to all replicas. It can partition data by doing this, and it can semi-intelligently route queries to the appropriate servers.

* "Mammoth Replicator" - BSD - http://www.commandprompt.com/products/mammothreplicator/ - Former proprietary solution, now open source. Uses a central logging process to distribute data changes amongst nodes. Essentially a fork of Postgres, as the changes are written directly into the backend.

* "Bucardo" - BSD License - http://bucardo.org/ - Trigger-based, asynchronous, multi-master or primary-replica, written using plperl.

* Cybertec, an Austrian company, offers a proprietary packaging of PGCluster. They simply call it PostgreSQL Multimaster-Replication, see http://www.cybertec.at.

* [[Londiste_Tutorial|Londiste]], a part of [[Skytools]] (https://developer.skype.com/SkypeGarage/DbProjects/SkyTools) which is a collection of replication tools from the Skype people. Purports to be simpler to use than Slony.

* [https://2ndquadrant.com/en/resources/bdr/ BDR (Bi-Directional Replication for PostgreSQL)] - multi-master replication based on log streaming logical replication.

* [https://2ndquadrant.com/en/resources/pglogical/ pglogical] - pglogical is a logical replication system implemented entirely as a PostgreSQL extension. Fully integrated, it requires no triggers or external programs. This alternative to physical replication is a highly efficient method of replicating data using a publish/subscribe model for selective replication.

* [http://www.continuent.com/index.php?option=com_content&task=view&id=212&Itemid=169 Continuent uni/cluster], proprietary and the related Sequoia (jdbc, formerly known as c-jdbc)

* [http://www.postgres-r.org Postgres-R] is still in development. It features eager and thus conflict-free, but async multi-master replication.

* [http://symmetricds.codehaus.org/ SymmetricDS] is an open-source, web-enabled, database independent, data synchronization software application. It uses web and database technologies to replicate tables between relational databases in near real time. The software was designed to scale for a large number of databases, work across low-bandwidth connections, and withstand periods of network outages. Supports several relational databases, including PostgreSQL. Licensed under Lesser GPL (LGPL).

* DRBD (http://www.drbd.org/), a device driver that replicates disk blocks to other nodes. This works for failover only, not for scaling reads. Easy migration of devices if combined with an NFS export.

* [http://sourceforge.net/projects/daffodilreplica/ Daffodil Replicator]. Supports several relational databases, including PostgreSQL. Licensed under GPL.

* "RubyRep" - MIT License - http://www.rubyrep.org/ - Ruby based, asynchronous, multi-master replication system, which supports Postgres and MySQL.

* "pg_comparator" - BSD License - http://pgfoundry.org/projects/pg-comparator/ - Perl-based, table-level async primary-replica "diff" and "patch" method of replication. Low configuration overhead.

* [https://www.citusdata.com/ Citus Data] develops the [https://www.citusdata.com/citus-products/pg-shard pg_shard extension] which can transparently shard a PostgreSQL table across many servers and replicate the shards, and [https://www.citusdata.com/product/citus Citus] which parallelizes queries across many servers and cores for real-time analytics and supports bulk loading, distributed joins, columnar storage and more.

* [http://www.enterprisedb.com/products-services-training/products-overview/tools/ EDB Replication Server]: Provides single and multi-master solutions for read/write scalability, availability, performance, and data integration with Oracle, SQL Server, and Postgres. EDB Replication Server uses Postgres' fast Logical Decoding technology to support large multi-master clusters and single primary configurations for a wide variety of data center solutions.

===Inactive projects===
* Slony-II
* PGReplication

==Clustering==

* [https://www.citusdata.com/product/citus Citus] - shards and replicates tables across a scalable, high availability cluster of commodity PostgreSQL servers and parallelizes queries for real-time SQL on big data.

* [http://www.greenplum.org Greenplum Database] - Not so much a replication solution as a way to parallelize queries, and targeted at the data warehousing and big data crowd. Greenplum is tightly integrated with PostgreSQL.

* [http://www.enterprisedb.com/products/gridsql.do GridSQL for EnterpriseDB Advanced Server] (formerly ExtenDB)

* [http://db.cs.yale.edu/hadoopdb/hadoopdb.html HadoopDB] - A MapReduce layer put in front of a cluster of postgres back end servers. Shared-nothing clustering.

* [[PL/Proxy]] - database partitioning system implemented as PL language.

* [https://postgrespro.com Postgres Pro Multimaster] - part of Postgres Pro Enterprise DBMS. Provides fail-safe shared nothing cluster with transactional integrity and no read overhead. Based on enhanced logical replication.

* [https://www.citusdata.com/citus-products/pg-shard pg_shard] - extension that shards and replicates table across many servers, can also [https://www.citusdata.com/blog/14-marco/178-scaling-out-postgresql-on-amazon-rds-using-masterless-pg-shard scale out Amazon RDS]

* sequoia (jdbc, formerly known as c-jdbc)

* [http://www.postgres-xl.org/ Postgres-XL] is a shared nothing, multi-master clustering solution which can transparently distribute a table on a set of nodes and execute queries in parallel of those nodes. It has a additional component called Global Transaction Manager (GTM) for providing globally consistent view of the cluster. The project is based on the latest available 9.5 release of PostgreSQL. Some companies, such as [http://www.2ndquadrant.com 2ndQuadrant] provides commercial support for the product.

==Connection Pooling and Acceleration==

Connection pooling programs let you reduce database-related overhead when it's the sheer number of physical connections dragging performance down. This is particularly important on Windows, where system limitations prevent large number of connections; see "I cannot run with more than about 125 connections at once" in [[Running & Installing PostgreSQL On Native Windows]]. It's also vital for web applications where the number of connections can get very large.

Some programs that implement connection pooling are:
* [[PgBouncer]]
* [http://www.pgpool.net/ pgpool]
* [https://www.heimdalldata.com/ Heimdall Data] - (Proprietary) Provides a multi-vendor solution for database caching, connection pooling, load balancing, query routing, analytics and security. Provides a GUI for simple configuration, as well as a distributed engine for processing queries at scale. Also supports run-time reconfiguration cluster-wide without application restarts. Requires zero code changes to implement.

Some people also or alternately use [http://www.danga.com/memcached/ memcached] in various ways to reduce the work the database handles directly by caching popular data. [https://github.com/ohmu/pgmemcache/ pgmemcache] is a PostgreSQL extension for interfacing with memcached servers.

== Cluster management ==

* [https://github.com/ohmu/pglookout/ pglookout] - PostgreSQL replication monitoring and failover daemon
* [[repmgr]] - replication manager for PostgreSQL clusters
* [https://github.com/MasahikoSawada/pg_keeper/tree/REL1_0_STABLE pg_keeper] - Background worker based simple failover daemon.

== Other Resources ==

Sources for more information located but not yet integrated into here.

=== Articles ===

* <strike>[http://bristlecone.continuent.org/uploads/bristlecone/HomePage/PG_East-Scale-Out-Benchmarks_FINAL2.pdf Portable Scale-Out Benchmarks for PostgreSQL] by Robert Hodges</strike> not available (2012-10-11)
* <strike>[http://www.fastware.com.au/docs/PostgreSQL_HighAvailability.pdf High Availability and PostgreSQL] by Gavin Sherry</strike> not available (2012-10-11)
* [http://www.palominodb.com/blog/2012/08/01/cascade-replication-and-delayed-servers-postgresql-92 Cascade Replication and Delayed servers on PostgreSQL 9.2]
* [http://prongs.org/blog/postgresql-replication Streaming Replication on PostgreSQL 9.3 by Afra Ahmad]

* [http://burger-ag.de/postgresql_replikation.whtml Replikation - Lösungen für PostgreSQL] page covering this topic in German. It translates pretty well through [http://babelfish.altavista.com/ Babelfish].

=== Video tutorials ===

* [http://youtu.be/qTPNB0y37EI Alex Alexander presenting Managing Postgres HA using DRBD, Pacemaker and Corosync] youtube video

==Credits==

Sources for the initial information on this page include:
*[http://archives.postgresql.org/pgsql-performance/2007-06/msg00264.php replication thread]
*[http://archives.postgresql.org/pgsql-general/2007-08/msg00085.php pgpool2 vs sequoia]
*[http://archives.postgresql.org/pgsql-hackers/2006-10/msg00810.php Postgresql Caching]

[[Category:Replication]][[Category:Administration]][[Category:Performance]][[Category:Clustering]]

PostgreSQL Clients

2018-08-13T15:31:48Z

Dfetter: Proprietary software is proprietary even when there isn't a per-seat license fee at the moment.

This page is a partial list of interactive SQL clients - that doesn't include reporting engines, ETL data loaders, visual design tools, just interactive clients that you can type SQL in to and get results from them.

== CLI Clients ==

=== Open Source / Free Software ===

==== psql ====

https://www.postgresql.org/docs/current/static/app-psql.html

The standard command line client, maintained by the postgresql development group and typically distributed as part of the server installation.

==== pgcli ====

https://www.pgcli.com

A command line client with syntax highlighting and pop-up command completion.

==== jaqy ====

https://teradata.github.io/jaqy/

A universal JDBC command line client with lots of features. It is not specific to PostgreSQL, but it is pre-configured to handle PostgreSQL servers. Requires PostgreSQL JDBC driver.

== macOS GUI Clients ==

=== Open Source / Free Software ===

==== Postbird ====

https://github.com/paxa/postbird

Open source, desktop application to manage your local or remote PostgreSQL databases.

=== Proprietary ===

==== SQLPro for Postgres ====

http://www.macpostgresclient.com/SQLProPostgres

macOS 10.8 and above

100% native OS X app with a clean and simple to use interface. Query editor with syntax highlighting and autocomplete.

==== TablePlus ====

https://tableplus.io/

A modern, native client for relational databases with nice UI and very convenient query editor. It's compatible with all versions of Postgres.

==== Postico ====

https://eggerapps.at/postico/

A nice native client by the developers of [http://postgresapp.com Postgres.app]. A free "demo" version of an inexpensive commercial app, but it has very reasonable limits and no time limit.

==== pgEdit ====

http://pgedit.com

Not a standalone client, rather a plugin for [https://macromates.com Textmate] for using psql.

==== PSequel ====

http://www.psequel.com/

OS X Yosemite only, free, "Sequel Pro" inspired.

==== SEQUEL for PostgreSQL ====

http://www.sequel.tech

SEQUEL for PostgreSQL is a professional DB administration and management tool, with extremely intuitive and feature rich GUI that makes it the best assistant tool for developers and admins. SEQUEL is lightweight, fast and powerful that it can significantly simplify the DB management process. For those who cannot live without a CLI, SEQUEL offers a powerful Query Editor with syntax highlight, autocomplete and a Console log view that is always visible, so you can monitor the communication with your databases.

== Windows GUI Clients ==

=== Open Source / Free Software ===

=== Proprietary ===

==== DBTools Manager ====

http://www.dbtools.com.br

Freeware, available for PostgreSQL and MySQL, allows managing all aspects of the database: db, table, triggers, functions, etc. Includes import/export wizards to migrate data and structure to/from other database engines.

==== EMS SQL Manager for PostgreSQL Freeware ====

http://www.sqlmanager.net/en/tools/free

EMS SQL Manager for PostgreSQL Freeware (EMS SQL Manager Lite for PostgreSQL) is an excellent and easy-to-use freeware graphical tool for PostgreSQL database administration. It has the minimal required set of tools for those users who are new to PostgreSQL server and need only its basic functionality.

There is a commercial version available with significantly more functionality.

==== Marshal SQL Utility ====

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1756

The Marshal SQL Utility is a generic cross database utility with batch execution capabilities. It allows you to test ODBC connections, browse database schemas, discover tables, views and columns.

==== dbForge Studio for PostgreSQL ====

https://www.devart.com/dbforge/postgresql/studio/

dbForge Studio for PostgreSQL is a GUI tool for managing and developing databases and objects. The PostgreSQL IDE allows users to create, develop, and execute queries, edit and adjust the code to your requirements in a convenient and UI. The tool provides a data editing tool to customize your queries and property window so that users can view all the required information of PostgreSQL database objects they are interested in.

==== AnySQL Maestro ====

http://www.sqlmaestro.com/products/anysql/maestro/

AnySQL Maestro is a freeware tool for administering any database engine (PostgreSQL, SQL Server, Oracle, MySQL, MS Access, etc.), which is accessible via ODBC driver or OLE DB provider. Includes Database Designer, Visual Query Builder, BLOB Viewer/Editor, SQL Editor, Data export/import and other features.

==== PostgreSQL Maestro ====

https://www.sqlmaestro.com/products/postgresql/maestro/

Allows you to create, edit, copy, drop and dump database objects easy and fast. You can also design your database as ER diagram, build queries visually, execute SQL queries and scripts, debug PL/pgSQL functions, view and edit data including BLOBs, represent data as diagrams, export and import data to/from most popular file formats, analyze your data summarized into multidimensional views and hierarchies (OLAP cubes), manage PostgreSQL roles, users, groups and privileges, and use a lot of other admin tools designed for making your work with PostgreSQL database server comfortable and efficient.

==== Access ====

https://products.office.com/en-us/access

Yes, you can use MS Access as a PostgreSQL database interface. Supports data access to PostgreSQL tables and views; many ODBC-based limitations and errors.

==== VSQL++ for PostgreSQL ====

http://www.sqlpp.com/products/postgresql-management/

A powerful Postgresql database management tool to help DBA sto manage the database objects easy and quickly.

==== Nucleon Database Master ====

http://nucleonsoftware.com/products/database-master

Supports PostgreSQL MongoDB, Oracle, DB2, Informix, Ingres, SQL Server, SQL Azure, MySQL, FireBird, SQLite

==== SQLPro ====

http://www.vive.net/products/sqlpro.htm

SqlPro is an easy to use database GUI tool for six popular databases (Oracle, MySQL, PostgreSQL, SQL Server, SQLite and Access). One IDE makes database administration and development faster and error free.
SQLPro Key Features: color-coding of the SQL, drag-and-drop of objects into the editor pane to save you from typing their names, retrieval of SQL code for things like stored procedures and triggers from the underlying database, and one-click creation of SELECT and INSERT statements. You can open, save and print SQL scripts.

=== Obsolete or End-of-Life ===

==== PGExplorer ====

http://www.PGExplorer.com

Hasn't been significantly updated in many years, but latest downloads suggest it may support Postgresql 9.* to some extent.

== Linux / Unix GUI Clients ==

=== Open Source / Free Software ===

==== Gnome DB ====

http://www.gnome-db.org

Database administration/user tool for GNOME, based on libgda/libgnomedb, which are a complete database-independent access layer for UNIX systems, with support for PostgreSQL, MySQL, Sybase, MS SQL Server, Oracle, Interbase/Firebird, MS Access files, xBase.

Has an experimental Windows build available too.

==== Kexi ====

http://www.kexi-project.org/

A visual database application creator, c.f. Access or FileMaker

== Cross-platform GUI Clients ==

=== Open Source / Free Software ===

==== pgAdmin 3 ====

http://www.pgadmin.org/

Windows, Linux, FreeBSD, macOS, OpenBSD, Solaris

For many years the "standard" freely available GUI client for Postgresql, and so is bundled in many packaged installers. It provides a SQL query tool, an editor for procedural languages and a CRUD interface. It's also one of the few clients to provide a GUI front end to the plpgsql debugger.

Development has been discontinued by pgadmin.org, but it is still being maintained by BigSQL who are doing basic maintenance to support current versions of PostgreSQL and packaging it for current OS releases [[https://www.openscg.com/bigsql/pgadmin3/index.jsp/ here]]

==== pgAdmin 4 ====

http://www.pgadmin.org/

Windows, macOS, [https://yum.postgresql.org rpm], Python

pgAdmin 4 is a ground-up rewrite of pgAdmin 3. Rather than being a native application it's primarily a web application that's also packaged as desktop web shell. At the time of writing it's considered inferior to pgAdmin 3 both in terms of functionality and stability.

==== LibreOffice Base ====

http://www.libreoffice.org/discover/base/

Supports MySQL/MariaDB, Adabas D, MS Access and PostgreSQL, as well as other JDBC/ODBC databases.

==== Tora ====

http://tora.sf.net/

Linux, Windows, macOS

Oracle, MySQL, and PostgreSQL, as well as limited support for ODBC targets. Inspired by the commercial Toad client.

==== SQL Workbench/J ====

http://www.sql-workbench.net

Java

An OpenSource (though it prohibits usage by government agencies from USA, UK, Canada, China, Russia, North Korea, Syria, Saudi Arabia, Turkey and the Chechen Republic) SQL GUI tool similar to Squirrel. Data can be edited directly in the result set. It has strong support for exporting and importing data between databases using its own SQL command extension. It can be used in GUI mode or as a console application. All SQL Workbench specific commands can also be run in batch mode to automate export and import task. It supports schema comparison ("diff") and copying data between databases.

It has some [http://sql-workbench.net/manual/license.html#license-restrictions restrictions] on use by government employees.

==== Druid III ====

http://druid.sourceforge.net/

Java

The druid is a tools that allows users to create databases in a graphical way. The user can add tables, fields, folders to group tables and can modify most of the database options that follow the SQL-92 standard. In addition to sql options, the user can document each table and each field with HTML information.

==== Power*Architect ====

http://www.sqlpower.ca/page/architect

Java

Power*Architect is an ERD modelling tool that is based on Java and JDBC. Support for forward and reverse engineering PostgreSQL databases is supported. It's OpenSource with a GPL license.

==== DBeaver ====

http://dbeaver.jkiss.org/

Eclipse/Java

Eclipse-based environment, supporting many SQL databases from different vendors, as well as few NoSQL ones (Cassandra, etc).
Good query editor with syntax highlighting, completion and autosave.
Editing of query results. SSH tunneling support. Tons of other cool features.
Quite good, but not 100% perfect PostgreSQL support (yet?). Regularly updated, as of 2018.

==== pgManage ====

https://github.com/pgManage/pgManage

An alternative to pgAdmin, which runs in both application and server modes.

=== Proprietary ===

==== Valentina Studio (Free) ====

http://www.valentina-db.com/valentina-studio-overview

Windows/OS X/Linux

Valentina Studio is a powerful PostgreSQL Database Server administration and development tool.

There is a commercial version available with additional functionality.

==== RazorSQL ====

http://www.razorsql.com/

Macintosh/Windows/Linux/Solaris

RazorSQL is an SQL query tool, database browser, SQL editor, and database administration tool that supports PostgreSQL and any other JDBC or ODBC compliant database. Some of the major features are tools for creating, dropping, and altering objects such as tables, views, indexes, triggers, functions, users, and databases; a programming editor that supports 20 different programming languages; import and export tools; auto column and table lookup; and a query builder, query scheduler, and SQL formatter.

==== JetBrains DataGrip ====

https://www.jetbrains.com/datagrip/

Windows, macOS, Linux

JetBrains has a dedicated SQL IDE — DataGrip which can connect to PostgreSQL as well. It provides code completion, multicursors, local query history, navigation, refactorings and language injection support.

Other JetBrains IDEs have plugins available to provide similar functionality.

==== Aqua Data Studio ====

http://www.aquafold.com/index-postgresql.html

Java: Windows/Linux/macOS/Solaris

Aqua Data Studio is a management tool for the PostgreSQL relational database w/ administration capabilities and a database query tool. The visual administration features provide users the ability to browse and modify database structures, including schema objects, database storage and maintain database security. An integrated query tool allows users to quickly create, edit and execute SQL queries and scripts. Aqua Data Studio also provides an import and export tool to allow users to easily move data in and out of the PostgreSQL database in and from different data formats.

==== Navicat ====

https://www.navicat.com/en/products/navicat-for-postgresql

Windows, macOS, iOS

Navicat is a powerful PostgreSQL Database Server administration and development tool. It works with PostgreSQL 8.0 version or above and supports most of the PostgreSQL features including Trigger, Function, View, Manage User, and so on. It is also not only sophisticated enough for professional developers, but also easy to learn for new users. With its well-designed GUI, Navicat lets you quickly and easily create, organize, access and share information in a secure and easy way.

==== DbVisualizer ====

http://www.dbvis.com/

Windows/macOS/Linux/UNIX

DbVisualizer is a feature rich, intuitive multi-database tool for developers, database administrators, and increasingly for advanced analysts providing a single powerful interface across a wide variety of operating systems. With its easy-to-use and clean interface, DbVisualizer has proven to be one of the most cost effective database tools available, yet to mention that it runs on all major operating systems and supports all major RDBMS that are available. Users only need to learn and master one application. DbVisualizer integrates transparently with the operating system being used.

==== Datazenit ====

https://datazenit.com/

Windows, Mac OS X, Linux

Datazenit is a cross-platform PostgreSQL and MySQL GUI with data grid, schema builder and interactive charts.
It also has query builder, raw query editor with auto-complete, team collaboration features like connection, query and chart sharing among team members.

Web-based, but available packaged as a desktop app.

== Android ==

=== Proprietary ===

==== SQLTool Pro Database Editor ====

http://www.sqltoolpro.com

SQLTool Pro is a professional Android SQL editor for MySQL, SQL Server, PostgreSQL, Sybase, and Oracle Databases. JDBC.

== Web Clients ==

=== Open Source / Free Software ===

==== franchise ====

https://franchise.cloud/

Web client, either hosted (free) or running locally, connects to a local postgresql instance via a small bridge application.

Can share the interface with others, rather like sqlfiddle.com, but accessing your database.

==== pgAdmin 4 ====

http://www.pgadmin.org/

Python

pgAdmin 4 is a ground-up rewrite of pgAdmin 3. Rather than being a native application it's primarily a web application that's also packaged as desktop web shell. At the time of writing it's considered inferior to pgAdmin 3 both in terms of functionality and stability.

==== TeamPostgreSQL ====

http://www.teampostgresql.com

browser-based, webserver included

AJAX/JavaScript-powered web interface for PostgreSQL administration. Browse, maintain and create data and database objects from anywhere, in the web browser. Supports SSH for both the web interface and the database connections. Rich interface with tabbed SQL editor with auto-completion, inline row-editing widgets, click-through foreign key navigation between rows and tables, 'favorites' management for commonly used scripts, and more.

Installers available for Windows, Mac and Linux, alternatively download a simple cross-platform archive that runs anywhere with simple script.

==== Adminer ====

http://www.adminer.org

PHP

Adminer (formerly phpMinAdmin) is a full-featured database management tool written in PHP. A single PHP file ready to deploy to the target server. Adminer is available for MySQL, PostgreSQL, SQLite, MS SQL and Oracle.

==== OmniDB ====

https://github.com/OmniDB/OmniDB

Django/Python

Open source full-featured web tool for database management. Currently supports PostgreSQL only. More RDBMS support coming soon, including the ability of converting databases from any supported RDBMS to PostgreSQL and back.

==== Tadpole DB Hub ====

https://github.com/hangum/TadpoleForDBTools/wiki

Tadpole DB Hub is Unified infrastructure tool, various environment based interface for managing Apache Hive, Amazon RDS, CUBRID, MariaDB, MySQL, Oracle, SQLite, MSSQL, PostgreSQL and MongoDB databases. It enables you to handle typical DB over the World Wide Web.

==== SIDU ====

http://topnew.net/sidu/

PHP

Schema and data browser and editor.

=== Proprietary ===

==== JackDB ====

http://www.jackdb.com/

Html5 Web Browser (Linux/Mac OS X/Windows)

JackDB is a database client that runs entirely in your web browser. There's no software to install locally so you can use it on Mac OS X, Linux, and Windows and it works on all major modern browsers (eg. Chrome, Firefox, IE, Safari, and Opera). It supports connecting to PostgreSQL, as well as MySQL, Oracle, and SQL Server databases.

A hosted service, so it requires external access to your database.

==== DBHawk ====

https://www.datasparc.com/dbhawk/

DBHawk is a web based SQL tool and reporting software designed for PostgreSQL, Oracle, SQL Server and other databases. Its easy to deploy and use.

Query editor, report builder, schema and data browser.

==== Datazenit ====

https://datazenit.com/

Java

Datazenit is a cross-platform PostgreSQL and MySQL GUI with data grid, schema builder and interactive charts.
It also has query builder, raw query editor with auto-complete, team collaboration features like connection, query and chart sharing among team members.

Web-based, but available packaged as a desktop app.

=== Obsolete or End-of-Life ===

==== phpPgAdmin ====

http://phppgadmin.sourceforge.net/doku.php

PHP

Similar to phpMyAdmin, enhanced for PostgreSQL, supports browsing and modification of most types of PostgreSQL database objects, plus execution of ad-hoc queries.

(last updated 2013, 9.2.x)

== Other Resources ==

[[Community Guide to PostgreSQL GUI Tools]] - the source for a lot of this page. Includes many non-client tools, such as bulk loaders, schema diff, schema design, etc.

[http://www.postgresonline.com/journal/index.php?/archives/133-Database-Administration,-Reporting,-and-Light-application-development.html Database Administration, Reporting, and Light application development] - from 2009

[[GUI Database Design Tools]] - tools for designing database schemas

Community Guide to PostgreSQL GUI Tools

2018-08-13T15:10:30Z

Dfetter: Proprietary software is proprietary even when there isn't a per-seat license fee at the moment.

{{Languages}}

== Alternate Guides ==

Another detailed summary from 2009 is available at
[http://www.postgresonline.com/journal/index.php?/archives/133-Database-Administration,-Reporting,-and-Light-application-development.html Database Administration, Reporting, and Light application development]

== Open Source / Free Software ==

=== pgAdmin 4 ===

http://www.pgadmin.org/

MS Windows, GNU/Linux, FreeBSD, Mac OS X, OpenBSD, Solaris

Admin

pgAdmin III is THE Open Source management tool for your PostgreSQL databases. Features full Unicode support, fast, multithreaded query and data editting tools and support for all PostgreSQL object types.

pgAdmin III is bundled with the Windows installer, and you can use that such a client to administer a remote server on another OS. Note that binary packages for platforms like RPM don't show up in every point release, you currently have to go back to v1.8.0 to get the last full set of packages.

Free Administration Centre for the PostgreSQL database. Includes a graphical administration interface, an SQL query tool, a procedural code editor and much more. pgAdmin III is designed to answer the needs of most users, from writing simple SQL queries to developing complex databases. The graphical interface supports all PostgreSQL features and makes administration easy. Available in more than 30 languages and for several operating systems.

=== phpPgAdmin ===

http://sourceforge.net/projects/phppgadmin

browser-based, requires webserver

Admin

Similar to the ever-popular phpMyAdmin, enhanced for PostgreSQL, supports browsing and modification of most types of PostgreSQL database objects, plus execution of ad-hoc queries. Maintained by (who else?) the phpPgAdmin team. (JMB 11.2002).

phpPgAdmin (and the required Apache and PHP packages) may be easily installed using Stack Builder if you are running a one-click-installer PostgreSQL distribution.

=== Adminer ===

http://www.adminer.org

browser-based, requires webserver

Adminer (formerly phpMinAdmin) is a full-featured database management tool written in PHP. Conversely to phpMyAdmin, it consist of a single file ready to deploy to the target server. Adminer is available for MySQL, PostgreSQL, SQLite, MS SQL and Oracle.

=== Libre Office ===

http://www.libreoffice.org/download/3-5-new-features-and-fixes/

New native driver for PostgreSQL databases (for versions > 8.4 - support for version 8.4 will be included in LibreOffice 3.5.1).

=== GNOME-DB ===

http://www.gnome-db.org

Linux, Unix

Admin

Database administration/user tool for GNOME, based on libgda/libgnomedb, which are a complete database-independent access layer for UNIX systems, with support for PostgreSQL, MySQL, Sybase, MS SQL Server, Oracle, Interbase/Firebird, MS Access files, xBase.

=== TOra, an Oracle tool with some PostgreSQL support ===

http://tora.sf.net/

Linux & Windows

Admin

An Oracle database administration interface, with limited ability to browse PostgreSQL databases (tables, views, and functions only). I'm told that if you have the Oracle libraries, Tora's sophisticated function editor will work for PostgreSQL as well. Developed by Henrik Johnson as a Quest Toad clone. (JMB 11.2002)

=== Kexi ===

http://www.kexi-project.org/

Kexi is part of the Calligra Suite and is released under the GNU General Public License (GPL) and LGPL.

available for
FreeBSD & Linux, Apple, Windows, (Android)

=== SQL Workbench/J ===

http://www.sql-workbench.net

Java (multi-platform)

An OpenSource SQL GUI tool similar to Squirrel. Data can be edited directly in the result set. It has strong support for exporting and importing data between databases using its own SQL command extension. It can be used in GUI mode or as a console application. All SQL Workbench specific commands can also be run in batch mode to automate export and import task. It supports schema comparison ("diff") and copying data between databases.

=== Druid III ===

http://druid.sourceforge.net/

Java (multi-platform)

The druid is a tools that allows users to create databases in a graphical way. The user can add tables, fields, folders to group tables and can modify most of the database options that follow the SQL-92 standard. In addition to sql options, the user can document each table and each field with HTML information. Once the database is created, the druid can generate:

* HTML documentation: for all tables, with browsing facilities
* PDF documentation: for all tables
* Java classes: (one class for each table) that contain tables' constants (such as fields size) plus java code added by the user
* A data dictionarythat contains all tables and fields present in the database
* SQL script which contains all table definitions that can be piped to the DBMS
* And much more info...

=== Power*Architect ===

http://www.sqlpower.ca/page/architect

Java (multi-platform)

Power*Architect is an ERD modelling tool that is based on Java and JDBC. Support for forward and reverse engineering PostgreSQL databases is supported. It's OpenSource with a GPL license.

=== RISE PostgreSQL code generator ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1889

Windows

The RISE PostgreSQL code generator generates native PL/pgSQL scripts. Model your information in the free RISE Editor and generate your database script. The script incrementally updates the tables, columns, indexes and constraints in the database to match the RISE model. Once the database model is updated, the views defined in the RISE model are created in the database and possible default data, entered in the model, is inserted.

=== Open Source CMS ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=2017

Windows

The CMS is a free Visual Studio 2010 solution template with a set of projects providing a complete Content Management System (CMS) based on RISE Visual Modeling with model, full source, sample site and DB-scripts for PostgreSQL, MySQL and SQL Server.

It’s a complete ready-to-run Visual Studio solution with model, source code and web clients. It illustrates how to use RISE, how to implement a SOA backend and how to build RIA frontends.

=== DBeaver ===

http://dbeaver.jkiss.org/

Eclipse/Java (multi-platform)

Eclipse-based environment, supporting many SQL databases from different vendors, as well as few NoSQL ones (Cassandra, etc).
Good query editor with syntax highlighting, completion and autosave.
Editing of query results. SSH tunneling support. Tons of other cool features.
Quite good, but not 100% perfect PostgreSQL support (yet?). Regularly updated, as of 2018.

=== OmniDB ===

https://github.com/OmniDB/OmniDB

Django/Python (multi-platform), browser-based

Open source full-featured web tool for database management. Currently supports PostgreSQL only. More RDBMS support coming soon, including the ability of converting databases from any supported RDBMS to PostgreSQL and back.

=== Postbird ===

https://github.com/paxa/postbird

MacOs

Open source, desktop application to manage your local or remote PostgreSQL databases.

=== Sohag Developer ===
[http://sohag-developer.com/ Sohag Developer]

Gnu/Linux Windows (Other OS can compile from source code).

Build a powerful database applications following few steps using Sohag Developer .
Sohag Developer currently supports PostgreSQL database and has a set of generators that generates (Qt/C++ code and ui forms - PHP web applications uses web forms and bootstrap framework ) to manipulate the data in the database tables or views.

=== PASH-Viewer: PostgreSQL Active Session History Viewer ===
https://github.com/dbacvetkov/PASH-Viewer

Java (multi-platform).

Open-source software which provides graphical view of active session history and help you to answer questions like "What wait events were taking most time?", "Which sessions were taking most time?", "Which queries were taking most time and what were they doing?". It also supports Active Session History extension by pgsentinel.

== Proprietary ==

=== dbForge Studio for PostgreSQL ===

https://www.devart.com/dbforge/postgresql/studio/

Free GUI tool for managing and developing databases and objects. The IDE for PostgreSQL allows users to create, develop, and execute queries, edit and adjust the code to your requirements in a convenient and user-friendly interface.

=== PSequel ===

http://www.psequel.com/

OS X Yosemite only, free, "Sequel Pro" inspired.

=== EMS SQL Manager for PostgreSQL Freeware ===

http://www.sqlmanager.net/en/tools/free

Windows

EMS SQL Manager for PostgreSQL Freeware (EMS SQL Manager Lite for PostgreSQL) is an excellent and easy-to-use freeware graphical tool for PostgreSQL database administration. It has the minimal required set of tools for those users who are new to PostgreSQL server and need only its basic functionality.
EMS SQL Manager for PostgreSQL Freeware allows you to work with servers, databases and schemas, view, edit, search, group, sort and filter any data stored in a database, create and execute SQL queries with powerful SQL editor, handle multiple selected objects at a time and much more.

=== Marshal SQL Utility ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1756

Windows

The Marshal SQL Utility is a generic cross database utility with batch execution capabilities. It allows you to test ODBC connections, browse database schemas, discover tables, views and columns.

Key features of Marshal SQL Utility:

* Execute any query supported by your database server
* Execute batches of queries
* Discover tables and views in your database
* Discover columns for a selected table or view
* Supports BLOBS and CLOBS
* Save your results to file
* Use any ODBC compliant database such as PostgreSQL.

=== RISE PHP for PostgreSQL code generator ===

http://www.risetobloome.com/Page_1_S.aspx?ITEM=1888

Windows

The RISE PHP for PostgreSQL code generator renders PHP source code for database access. Model your information and programming interfaces in the free RISE Editor and generate your code. The generated code implements the classes and methods corresponding to the information interfaces specified in the RISE model. This includes classes for database access and, optionally, classes implementing SOAP/JSON web services and proxy classes assisting the implementation of a PHP SOAP client.

=== RISE - Model Driven Development using ERD / UML ===

http://www.risetobloome.com

Windows

RISE is a free software suite for model driven information system development. Use a single source RISE model to generate your entire information solution including database, web services and documentation. Boost development throughput and improve quality and maintainability!

The RISE user experience is based on a project concept, similar to that of most integrated development environments. The user works with resources and drawings that are part of a single development project.

RISE supports a fully graphical approach to information modeling and system engineering, using ERD (Entity Relationship Diagram) as well as UML (Unified Modeling Language). This includes drag-and-drop of entities, their attributes and relations, as well as of views and entire web services.

RISE supports graphic editing of complex objects such as views and orchestrated methods. RISE automatically safeguards the combination process, thus, assuring a technically correct result.

RISE provides several ways to generate code from the model; directly to file, via the RISE Server or as an Internet service. RISE provides code generators for the database layer (SQL/DDL) as well as for the server side application layer (web services and persistent classes). All database scripts are incremental allowing you to install and maintain any number of databases from a single model.

Feature list
http://www.risetobloome.com/Page_1_S.aspx?ITEM=1355

=== WaveMaker Ajax GUI Design Tool ===

http://www.wavemaker.com/

Windows, Macintosh, Linux

WaveMaker is an Ajax-based GUI design tool for Postgres. WaveMaker is built using itself! WaveMaker generates a standard Java WAR file based on Spring, Hibernate and Dojo. WaveMaker supports Postgres schema creation and import and includes a visual query editor.

=== AnySQL Maestro ===

http://www.sqlmaestro.com/products/anysql/maestro/

Windows

AnySQL Maestro is a freeware tool for administering any database engine (PostgreSQL, SQL Server, Oracle, MySQL, MS Access, etc.), which is accessible via ODBC driver or OLE DB provider. Includes Database Designer, Visual Query Builder, BLOB Viewer/Editor, SQL Editor, Data export/import and other features.

=== TeamPostgreSQL ===

http://www.teampostgresql.com

browser-based, webserver included

AJAX/JavaScript-powered web interface for PostgreSQL administration. Browse, maintain and create data and database objects from anywhere, in the web browser. Supports SSH for both the web interface and the database connections. Rich interface with tabbed SQL editor with auto-completion, inline row-editing widgets, click-through foreign key navigation between rows and tables, 'favorites' management for commonly used scripts, and more.

Installers available for Windows, Mac and Linux, alternatively download a simple cross-platform archive that runs anywhere with simple script.

=== Postgres Compare ===

[[File:Postgres_compare.png|thumb|left|frameless]]

https://www.postgrescompare.com/

Windows, Mac & Linux

A comprehensive tool for identifying the differences between databases and generating an update script to synchronize them. Postgres Compare reads the system catalogs to determine the structure of the database and compares it to another to find the changes. Generate SQL and deploy the alterations, save snapshots for later. Automate the process via the command line.

Alpha build available now https://www.postgrescompare.com/downloads

<div style="clear:both;"></div>

=== JetBrains IDEs - DataGrip, IntelliJ IDEA, PHPStorm, PyCharm, RubyMine, etc ... ===

http://www.jetbrains.com/

Windows, Mac OS X, Linux

JetBrains has a dedicated SQL IDE — DataGrip which can connect to PostgreSQL as well. It provides code completion, multi cursors, local query history, navigation, refactorings and language injection support.
https://www.jetbrains.com/datagrip/

Other JetBrains Products, for example, PHPStorm, have built-in database plugin, and it has the same functionality as DataGrip.

After you configured the data sources of your project, you can easily create tables, foreign keys, indexes much easier than usual, because the IDE is very smart; for example by foreign keys it automatically sets the name of the key and the related columns. For me, it is so far the best experience by creating a basic database schema. Even with editable EER models was it slower...
By the settings of [http://goo.gl/TuqiPRpantun romantis terbaru] your data source you can configure the SQL dialect of your database. After that, if you want to add stored procedures or triggers, you will have code completion which is favorable too. So I think JetBrains products speed up your work if you exactly know what you want, and how can you make it.

For any JetBrains IDE, there is a free license for open source projects. For enterprise usage there is a 30 days trial, after that, you can buy a personal or commercial license which is very cheap compared to other products.

For PyCharm (even the Community Edition) you can install the free third-party plugin [http://confluence.jetbrains.com/display/CONTEST/Database+Navigator Database Navigator] (Settings -> IDE Settings -> Plugins). It appears to deliver the same functionality described above for PHPStorm. You will get a new menu DB Navigator, left to the Help menu.

=== TablePlus ===

https://tableplus.io/

macOS

A modern, native tool with an elegant UI that allows you to simultaneously manage multiple databases, including PostgreSQL.

* True native built.

* Workspace supports multiple tabs, multiple windows

* Powerful SQL editor with full features: auto syntax highlight, auto-suggestion, split pane, favorite and history.

* Data Filter & Sorting, import & export

* Full-dark theme & modern shortcut

With plugin system, you can be able to write your own new features to work with database per your needs (export charts, pretty json…).

=== SQLPro for Postgres ===

http://www.hankinsoft.com/SQLProPostgres

Mac OS X 10.8 and above

Features:
* 100% native OS X app with a clean and simple to use interface.
* Query editor with syntax highlighting and autocomplete.
* Support for multiple result set execution.
* History feature, displaying your last ten executed queries.
* Primary key detection for inline result set modifications.
* Custom theme support allowing developers to work with style.

=== Postico ===

https://eggerapps.at/postico/

Mac OS X

Postico is a fully native Mac app for connecting to your PostgreSQL server. It supports encrypted connections via SSL and SSH to PostgreSQL 8.0 and later, including Amazon Redshift.

Postico has a powerful table content editor with in-cell editing and form-based row editing in a sidebar. You can quickly filter tables by keywords or even complex SQL expressions.

There's also a table structure editor for editing columns, types, default values, foreign keys, check constraints etc.

Finally, there's a convenient SQL Query Editor with support for query history and syntax highlighting. It also has convenience features like auto-indent and shortcuts for comment line etc.

=== SEQUEL for PostgreSQL ===

http://www.sequel.tech

macOS

SEQUEL for PostgreSQL is a professional DB administration and management tool, with extremely intuitive and feature-rich GUI that makes it the best assistant tool for developers and admins. SEQUEL is lightweight, fast and powerful that it can significantly simplify the DB management process. For those who cannot live without a CLI, SEQUEL offers a powerful Query Editor with syntax highlight, autocomplete and a Console log view that is always visible, so you can monitor the communication with your databases. It includes:

* Database management forms for Schema, Table, Index, Foreign key, Trigger, Rule, Sequence, Collation, Domain, Enum type, Tablespace and Language objects with full parameters support
* Assistant info views for Object information, Actions, Help, and Documentation
* Jump bar for quick objects selection and navigation
* Taskbar with multi-task monitoring support
* Console log view
* Syntax highlight, autocomplete, current and selection query execution and explain, line numbering and working statement detection
* Direct editing in the results view, query results explanation
* Powerful Field editor
* Transaction based database updates
* Code preview and Content editing

=== dbForge Data Compare for PostgreSQL ===

http://www.devart.com/dbforge/postgresql/datacompare/

Microsoft Windows 2000/XP/2003/Vista and Windows 7, 8, 10

'''dbForge Data Compare for PostgreSQL''' by '''Devart''' is a tool for table data comparison and synchronization. When using PostgreSQL data compare tool developer can detect data differences in compared PostgreSQL tables; generate data synchronization script and execute it to eliminate all these differences.

'''Key features:'''

* Identify the differences between two databases
* Compare separate tables or table groups by table name mask
* Compare tables with different structure
* Generate a report embodying data diff and save it for further analysis
* Sync data in tables and views in full or in part
* Generate SQL script for database synchronization
* Organize database synchronization according to the schedule

=== Full Convert ===

https://www.spectralcore.com/fullconvert

Database conversion and synchronization between PostgreSQL and Microsoft Access, dBase, FoxPro, Microsoft Excel, Firebird, Interbase, MySQL, Oracle, Paradox, Microsoft SQL Server, SQL Server, SQL Server Azure, SQL Server Compact(SQLCE), SQLite, Delimited text files (CSV), XML and many more via ODBC.

=== Nucleon Database Master for PostgreSQL and Others ===

Nucleon Database Master is a modern, powerful, intuitive, easy to use and all in one PostgreSQL MongoDB, Oracle, DB2, Informix, Ingres, SQL Server, SQL Azure, MySQL, FireBird, SQLite client application with a consistent interface that simplifies managing, querying, editing, visualizing, designing and [http://mitraharga.blogspot.co.uk/2014/09/harga-tablet-pc-axioo.htmlharga tablet axioo] reporting relational and schema-free (NoSQL) database systems. You can connect any database system via ODBC and OleDB connections.Using Database Master, you can execute SQL, LINQ, JSON queries or you can create, edit and delete all database objects such as tables, views, procedures, columns, indexes, collections, and triggers. You can execute SQL queries and scripts, view and edit table data including BLOBs (Image, Text or any file), represent tables and its relations as an ER(Entity Relationship) diagram.

Info:
http://www.nucleonsoftware.com/
Windows, other platforms via WINE
Admin

=== DBTools Manager ===

http://www.dbtools.com.br

Windows

Admin

Freeware, available for PostgreSQL and MySQL, allows managing all aspects of the database: db, table, triggers, functions, etc. Includes import/export wizards to migrate data and structure to/from other database engines. Developed by DBTools Software.

=== PgManager ===

http://www.ems-hitech.com/pgmanager

Windows, Linux version just released

Admin

Basically a proprietary, more powerful version of PGAdmin II or PGAccess. Adds support for trigger and constraint editing, metadata logging, and query monitoring. Also includes multiple-format data import/export tools, which are also available on their own for Linux. Developed by EMS Hitech. (JMB 4.2003).

=== DeZign for Databases ===

http://www.datanamic.com

Windows

ERD

DeZign is a database development tool using an entity relationship diagram. It visually supports the layout of the entities and relations and automatically generates SQL schemas for most leading databases including PostgreSQL.

=== Case Studio 2 / Toad Data Modeler ===

http://www.casestudio.com/enu/index.aspx

Windows

ERD

Commenter 1: I just downloaded the trial version, so far it looks really promising and claims to support PostgreSQL. Handles reverse engineering of existing databases, and has a really nice interface for setting up tables, relationships etc. You can get a lite or full version. The description from the website... Professional database modeling tool for various databases. CASE Studio 2 includes following key features:

LITE version features + Reverse Engineering from various database systems Version Manager Data Flow Diagrams Definition of user-defined variables Large COM interface Users, User groups and User permission support and many more.

Case Studio was acquired, and renamed 'Toad Data Modeler'.

Commenter 2: I've used the licensed version before and after the name change. PostgreSQL support is excellent.

=== PostgreSQL PHP Generator ===

http://www.sqlmaestro.com/products/postgresql/phpgenerator/

Windows

PostgreSQL PHP Generator is a freeware but powerful PostgreSQL GUI frontend that allows you to generate high-quality PHP scripts for the selected tables, views and queries for the further working with these objects through the web.

=== pgEdit ===

http://pgedit.com

Macintosh
pgEdit is a high-performance SQL editor and development environment designed specifically for PostgreSQL relational databases. pgEdit features include SQL syntax coloring, direct source code execution, PHP support, integrated documentation, and extensive customizable editing facilities.

pgEdit uses psql, the interactive terminal application included with every PostgreSQL installation. This makes it easy to develop with pgEdit and then transfer your work to any PostgreSQL installation for maintenance and production tasks.

pgEdit is a native application for both Macintosh and Windows. It does not use Java or require installation of external libraries. You have the option of using the version of psql included with pgEdit or a different version installed anywhere on your hard drive.

=== RazorSQL ===

http://www.razorsql.com/

Macintosh/Windows/Linux/Solaris

RazorSQL is an SQL query tool, database browser, SQL editor, and database administration tool that supports PostgreSQL and any other JDBC or ODBC compliant database. Some of the major features are tools for creating, dropping, and altering objects such as tables, views, indexes, triggers, functions, users, and databases; a programming editor that supports 20 different programming languages; import and export tools; auto column and table lookup; and a query builder, query scheduler, and SQL formatter.

=== MicroOLAP Database Designer ===

http://www.microolap.com/products/database/postgresql-designer/

Windows ODBC

Database Designer for PostgreSQL is an easy CASE tool with an intuitive graphical interface allowing you to build a clear and effective database structure visually, see the complete picture (diagram) representing all the tables, references between them, views, stored procedures and other objects. Then you can easily generate a physical database on a server, modify it according to any changes you made to the diagram using fast ALTER statements.

=== Import / Export and synchronization tools for PostgreSQL ===

http://convertdb.com/postgresql

Microsoft Windows 8 / 7 / Vista / XP / 2000 / NT.
The software is able to connect to remote PostgreSQL 9.x/7.4 located on Linux, Solaris, Mac OS X, and Windows.

ConvertDB cross-database migration tools assist in data conversion and synchronization among PostgreSQL, MySQL, MS SQL Server, MS Windows SQL Azure, and MS Access databases

* 1 Million of records can be transferred in 5-10 minutes.
* Bi-directional synchronization between PostgreSQL, MS SQL, MySQL and Oracle
* Scheduling migration and synchronization jobs.

=== dbForge Studio for PostgreSQL ===

https://www.devart.com/dbforge/postgresql/studio/

Microsoft Windows 7, 8, 10

'''dbForge Studio for PostgreSQL''' is a brand new tool for PostgreSQL databases development, management, and editing process enjoyable and easy by Devart. The PostgreSQL IDE allows users to create, develop, and execute queries, edit and adjust the code to the requirements in a convenient and UI. The tool provides the PostgreSQL data editor functionality for queries customization and property window for the viewing all the required information of PostgreSQL database objects.

'''Key features:'''

* Code Completion helps to improve code quality when creating and editing queries with List Members, Parameter Info, Quick Info, Complete Word.
* Object Explorer for easy navigation through the object tree. You can retrieve data from the database on a single SQL document, truncate a table, select Properties to view some information on the object.
* Data Editor for management settings of tables, such as adjust column width, set either paginal or auto-search mode by default. Color and format rows and cells using a rich set of fonts and size. The tool has predefined data type formats to meet your own needs.

=== dotConnect for PostgreSQL ===

https://www.devart.com/dotconnect/postgresql/

Windows

'''dotConnect for PostgreSQL''', formerly known as PostgreSQLDirect .NET, is an enhanced ORM enabled data provider for PostgreSQL that builds on ADO.NET technology to present a complete solution for developing PostgreSQL-based database applications. It introduces new approaches for designing application architecture, boosts productivity, and leverages database applications.

'''Key features:'''

* Direct Mode
* Database Application Development Extension
* PostgreSQL Advanced Features Support
* Optimized Code
* ORM Support
* BIS Support

=== PostgreSQL Data Access Components ===

Windows

https://www.devart.com/pgdac/

PostgreSQL Data Access Components (PgDAC) is a library of components that provides native connectivity to PostgreSQL from Delphi, C++Builder, Lazarus (and Free Pascal) on Windows, Mac OS X, iOS, Android, Linux, and FreeBSD for both 32-bit and 64-bit platforms. PgDAC is designed to help programmers develop really lightweight, faster and cleaner PostgreSQL database applications without deploying any additional libraries.

Native Connectivity to PostgreSQL
PgDAC is a complete replacement for standard PostgreSQL connectivity solutions and presents an efficient alternative to the Borland Database Engine (BDE) and standard dbExpress driver for access to PostgreSQL. It provides direct access to PostgreSQL without PostgreSQL Client.

=== ODBC Driver for PostgreSQL ===

https://www.devart.com/odbc/postgresql/

Windows

Devart ODBC Driver for PostgreSQL provides high-performance and feature-rich connectivity solution for ODBC-based applications to access PostgreSQL databases from Windows, both 32-bit and 64-bit. Full support for standard ODBC API functions and data types implemented in our driver makes the interaction of your database applications with PostgreSQL fast, easy and extremely handy.

=== Excel Add-in for PostgreSQL ===

https://www.devart.com/excel-addins/postgresql.html

Windows

Devart Excel Add-in for PostgreSQL allows you to quickly and easily connect Microsoft Excel to PostgreSQL, load data from PostgreSQL to Excel, instantly refresh data in an Excel workbook from the database, edit these data, and save them back to PostgreSQL. It enables you to work with PostgreSQL data like with usual Excel worksheets, easily perform data cleansing and de-duplication, and apply all the Excel's powerful data processing and analysis capabilities to these data.

=== EMS Database Management Tools for PostgreSQL ===

http://www.sqlmanager.net/en/products/postgresql

Windows

PostgreSQL Tools Products Family:

* [http://www.sqlmanager.net/en/products/studio/postgresql SQL Management Studio for PostgreSQL] - a single workbench for administering PostgreSQL databases, managing database schema and objects as well as for database design, migration, extraction, query building, data import, export, and database comparison.

* [http://www.sqlmanager.net/en/products/postgresql/manager SQL Manager for PostgreSQL] - high performance graphical tool for PostgreSQL database administration and development. It makes creating and editing PostgreSQL database objects easy and fast, and allows you to run SQL scripts, visually design databases, build SQL queries, extract, print and search metadata, import and export PostgreSQL database data and much more.

* [http://www.sqlmanager.net/en/products/postgresql/dataexport Data Export for PostgreSQL] - tool to export PostgreSQL database data quickly to any of 19 available formats, including MS Access, MS Excel, MS Word, RTF, HTML, TXT, ODF and more. Data Export for PostgreSQL has a [http://aurora-ndut.blogspot.fr/2013/10/kata-kata-lucu.htmlkata kata lucu] friendly wizard, which allows you to set various options of PostgreSQL export process visually and a command-line utility to automate your PostgreSQL export jobs using the configuration file.

* [http://www.sqlmanager.net/en/products/postgresql/dataimport Data Import for PostgreSQL] - tool to import data to PostgreSQL tables from MS Excel 97-2007, MS Access, DBF, TXT, CSV, MS Word 2007, RTF, ODF and HTML files. This utility allows you to quickly import data to one or several PostgreSQL tables or views at once, save all PostgreSQL import parameters set on current wizard session, use special batch insert mode to import PostgreSQL data at the maximum possible speed and much more.

* [http://www.sqlmanager.net/en/products/postgresql/datapump Data Pump for PostgreSQL] - migration tool for converting databases and importing table data from an ADO-compatible source (e.g. MS Access, MS SQL database or any other database with ADO support) to PostgreSQL databases.

* [http://www.sqlmanager.net/en/products/postgresql/datagenerator Data Generator for PostgreSQL] - tool for generating test data to PostgreSQL database tables. The utility can help you to simulate the database production environment and allows you to populate several PostgreSQL database tables with test data simultaneously, define tables for generating data, set value ranges, control a wide variety of generation parameters for each field type and much more.

* [http://www.sqlmanager.net/en/products/postgresql/dbcomparer DB Comparer for PostgreSQL] - a tool for comparing PostgreSQL database schemas and discovering differences in their structures. You can view all the differences in compared database objects and execute an automatically generated script to synchronize structure of PostgreSQL databases and eliminate these differences.

* [http://www.sqlmanager.net/en/products/postgresql/extract DB Extract for PostgreSQL] - easy-to-use tool for creating PostgreSQL database backups in a form of SQL scripts. This database script utility allows you to save metadata of all PostgreSQL database objects as well as PostgreSQL table data as database snapshots.

* [http://www.sqlmanager.net/en/products/postgresql/query SQL Query for PostgreSQL] - a useful tool that lets you quickly and simply build SQL queries to PostgreSQL databases. Visual PostgreSQL query building, as well as direct editing of a query text, is available.

* [http://www.sqlmanager.net/en/products/postgresql/datacomparer Data Comparer for PostgreSQL] - tool for PostgreSQL data comparison and synchronization. Using this utility you can view all the differences in compared PostgreSQL tables and execute an automatically generated script to eliminate these differences.

=== SQL Maestro Group products for PostgreSQL ===

http://www.sqlmaestro.com/products/postgresql/

Windows

[http://www.sqlmaestro.com SQL Maestro Group] offers a number of tools for PostgreSQL.

* [http://www.sqlmaestro.com/products/postgresql/maestro/ PostgreSQL Maestro] allows you to create, edit, copy, drop and dump database objects easy and fast. You can also design your database as ER diagram, build queries visually, execute SQL queries and scripts, debug PL/pgSQL functions, view and edit data including BLOBs, represent data as diagrams, export and import data to/from most popular file formats, analyze your data summarized into multidimensional views and hierarchies (OLAP cubes), manage PostgreSQL roles, users, groups and privileges, and use a lot of other admin tools designed for making your work with PostgreSQL database server comfortable and efficient.

* [http://www.sqlmaestro.com/products/postgresql/datawizard/ PostgreSQL Data Wizard] provides you with a number of easy-to-use wizards to transfer any database to PostgreSQL, export data from PostgreSQL tables, views and queries to most popular formats, and import data from various sources into PostgreSQL tables.

* [http://www.sqlmaestro.com/products/postgresql/codefactory/ PostgreSQL Code Factory] is a GUI tool aimed at the SQL queries and scripts development.

* [http://www.sqlmaestro.com/products/postgresql/datasync/ PostgreSQL Data Sync] is a powerful and easy-to-use tool for database contents comparison and synchronization.

* [http://www.sqlmaestro.com/products/postgresql/phpgenerator/ PostgreSQL PHP Generator Professional] is a frontend that allows you to generate high-quality PHP applications for your database in a few mouse clicks.

SQL Maestro Group also produces similar tools for MySQL, Oracle, MS SQL Server, SQLite, Firebird, DB2, SQL Anywhere, and MaxDB.

=== Datanamic DataDiff for PostgreSQL ===

http://www.datanamic.com/datadiff-for-postgresql/

Windows

Datanamic DataDiff for PostgreSQL is a utility for data comparison and synchronization. Compare data for selected tables in two databases, view differences and publish changes quickly and safely. Flexible comparison and synchronization settings will enable you to set up a customized comparison key and to select tables and fields for comparison and for synchronization.
DB Data Difftective can be used for data migrations, verification of (corrupt) data, data auditing etc.

=== Datanamic SchemaDiff for PostgreSQL ===

http://www.datanamic.com/schemadiff-for-postgresql/index.html

Windows

Datanamic SchemaDiff for PostgreSQL is a tool for comparison and synchronization of database schemas. It allows you to compare and synchronize tables, views, functions, sequences (generators), stored procedures, triggers and constraints between two databases.

=== DB MultiRun PostgreSQL Edition ===

http://www.datanamic.com/multirun/index.html

Windows

DB MultiRun is a simple tool to execute multiple SQL scripts on multiple databases quickly.
Define a list of databases, add SQL scripts to execute on these databases and click "execute" to run those scripts on the databases in the list. The multi-threaded execution of the SQL scripts makes it complete the task fast. After execution of the scripts, you can examine the results of the executed scripts on each database.

=== SQLPro ===

http://www.vive.net/products/sqlpro.htm

Windows

SqlPro is an easy to use database GUI tool for six popular databases (Oracle, MySQL, PostgreSQL, SQL Server, SQLite, and Access). One IDE makes database administration and development faster and error free.
SQLPro Key Features: color-coding of the SQL, drag-and-drop of objects into the editor pane to save you from typing their names, retrieval of SQL code for things like stored procedures and triggers from the underlying database, and one-click creation of SELECT and INSERT statements. You can open, save and print SQL scripts.
SQLPro uses native drivers to connect to the databases (no ODBS or third party engines to install).

=== DB Doc ===

http://www.yohz.com/dbdoc_details.htm

Windows/Linux(Wine)

DB Doc helps you document your database structure and objects. Documents can be generated as PDF reports, HTML pages, Microsoft Word (docx) file, or a single compiled HTML file. The layout is fully customizable, and you can quickly view inter-object dependencies using hyperlinks.

DB Doc supports PostgreSQL 8.3 to 9.4.

=== SQL Blob Export ===

http://www.yohz.com/sbe_details.htm

Windows

SQL Blob Export exports unlimited images and files from your tables or queries in 5 simple steps.

=== SQL File Import ===

http://www.yohz.com/sfi_overview.htm

Windows

SQL File Import allows you to upload files, images, and other data into your database, without having to write any SQL statements. SQL File Import supports PostgreSQL, Firebird, MySQL, Oracle, SQLite, SQL Server, and various ODBC-supported databases (e.g. DB2 and PostgreSQL).

A scripting engine allows you to transform data before importing them into your database. A command line version is also included to allow you to perform unattended upload/import tasks.

=== SQL Image Viewer ===

http://www.yohz.com/siv_details.htm

Windows

SQL Image Viewer allows you to retrieve, view, convert and export images stored in Firebird, MySQL, Oracle, SQLite, SQL Server, and various ODBC-supported databases (e.g. DB2 and PostgreSQL). It supports the following image formats: BMP, GIF, JPG, PNG, PSD, and TIFF.

It also allows you to export binary data and recognises the following binary file types: PDF, MP3, WAV, 7Z, BZ2, GZ, RAR, ZIP, and has experimental support for DOC, PPT and XLS file types.

A command line version is also included to allow you to perform unattended scheduled exports of binary data.

=== SQL Multi Select ===

http://www.yohz.com/sms_details.htm

Windows

SQL Multi Select is a query tool that allows you to run multiple scripts on multiple servers with a single click. Result sets from different servers are consolidated into a single view, allowing for easy comparison and analysis.

=== SQLTool Pro Database Editor ===

http://www.sqltoolpro.com

Android

SQLTool Pro is a professional Android SQL editor for MySQL, SQL Server, PostgreSQL, Sybase, and Oracle Databases.

=== SSIS Data Flow Components for PostgreSQL ===

https://www.devart.com/ssis/

Windows

'''Devart SSIS Data Flow Components for PostgreSQL''' allow you to integrate database and cloud data via SQL Server Integration Services (SSIS).

Devart SSIS Data Flow Components provide easy to set up cost-effective data integration using SSIS ETL engine. They provide high performance data loading, convenient component editors, SQL support for cloud data sources and lots of data source specific features.

=== DbVisualizer ===

http://www.dbvis.com/

Windows/OS X/Linux/UNIX

DbVisualizer is a feature rich, intuitive multi-database tool for developers, database administrators, and increasingly for advanced analysts providing a single powerful interface across a wide variety of operating systems. With its easy-to-use and clean interface, DbVisualizer has proven to be one of the most cost effective database tools available, yet to mention that it runs on all major operating systems and supports all major RDBMS that are available. Users only need to learn and master one application. DbVisualizer integrates transparently with the operating system being used.

[[Category:Tool]]
[[Category:General articles and guides]]

=== Valentina Studio (Free) ===

http://www.valentina-db.com/valentina-studio-overview

Windows/OS X/Linux/

Valentina Studio is a powerful PostgreSQL Database Server administration and development tool. It offers for free many advanced editors:
* Schema Editor with Tree and Column views
* Diagram Editor with reverse engineering
* SQL Editor with auto-completion, syntax-highlighting, recent and favorite queries, templates of commands, many result tab-panels, ...
* Data Editor with easy sorting and filtering of records without SQL, in-cell editing.
* Related Data Editor that allow s you to learn related records in different modes.
* Import/Export
* SQL dumps
* and so on ...

Valentina Studio PRO - adds additional advanced features as:
* Report Editor to developer reports based on Valentina Report Engine with datasources from PostgreSQL and other databases.
* Diagrams forward engineering
* SQL DIFF
* Data Transfer

[[Category:Tool]]

=== JackDB ===

http://www.jackdb.com/

Html5 Web Browser (Linux/Mac OS X/Windows)

JackDB is a database client that runs entirely in your web browser. There's no software to install locally so you can use it on Mac OS X, Linux, and Windows and it works on all major modern browsers (eg. Chrome, Firefox, IE, Safari, and Opera). It supports connecting to PostgreSQL, as well as MySQL, Oracle, and SQL Server databases.

Features:
* Html5 interface with no client installation
* Query editor with syntax highlighting
* Scrolling result sets
* Schema/Object browser
* SSL connections with certificate pinning
* Eliminates password sharing
* Two-factor authentication
* BLOB display (images and Html5 audio/video)

=== Tadpole DB Hub ===

https://github.com/hangum/TadpoleForDBTools/wiki

Tadpole DB Hub is Unified infrastructure tool, a various environment based interface for managing Apache Hive, Amazon RDS, CUBRID, MariaDB, MySQL, Oracle, SQLite, MSSQL, PostgreSQL and MongoDB databases. It enables you to handle typical DB over the World Wide Web.

Features:
* Intuitive web interface (Safari, Chrome, IE 10, Firefox)
* User Management (Admin, Manager, User)
* Select, Insert, Update, Delete
* Download query result
* SQL Syntax Highlighting
* SQL Formatting
* SQL Statement <-> Java, PHP String Literal Each Convert
* SQL Assist
* Execute SQL Statement
* SQL Result Set to CSV
* SQL History And Export text
* Generate SQL Statement (Select, Insert, Update, Delete, Table, View, Index, Procedure, Function, Trigger)
* Generate ER Diagram (Auto Layout)

=== Vertabelo ===

http://www.vertabelo.com

Vertabelo is an online database designer working under Chrome. It free to use for smaller projects and have a commercial version for larger database projects.

Features:
* Intuitive HTML5 web interface (Chrome)
* OS independent
* Sharing DB model with team members
* Support for PostgreSQL, MySQL, Oracle, MS SQL Server, DB2, SQLite, HSQLDB,
* Model versioning
* Dynamic/Visual search
* Live model validation
* Reverse engineering

=== pgModeler ===

PostgreSQL Database Modeler

http://pgmodeler.com.br

PostgreSQL Database Modeler, or simply, pgModeler is an open source tool for modeling databases that merges the classical concepts of entity-relationship diagrams with specific features that only PostgreSQL implements. The pgModeler translates the models created by the user to SQL code and apply them onto database clusters from version 8.0 to 9.1. $3.50 per copy as of 2014/04/09.

=== GenMyModel ===

https://www.genmymodel.com

GenMyModel is an online modeling tool supporting [http://www.genmymodel.com/database-diagram-online database modeling]. It is free to use for smaller projects and have a commercial version for larger database projects.

Features:
* Intuitive HTML5 web interface (Chrome, Firefox, Safari, Internet Explorer)
* OS independent
* Instant sharing and collaboration
* Customizable SQL generators
* Model versioning
* Live model validation

=== DBHawk ===

http://www.datasparc.com/

Web Browser (Linux/Mac OS X/Windows)

DBHawk is a web based SQL tool and reporting software designed for PostgreSQL, Oracle, SQL Server and other databases. Its easy to deploy and use.

Features:
* Web based interface with no client installation
* Advanced Query editor with syntax highlighting and multi tabs results
* Online visual query builder
* Online SQL Report Builder
* Online SQL Job Scheduler
* Export results to html, csv, pdf, google docs, amazon s3
* SQL Auditing and Security
* Schema/Object browser
* SQL and data snippet sharing
* Blob data viewer and editor

=== Datazenit ===

https://datazenit.com/

Windows, Mac OS X, Linux

Datazenit is a cross-platform PostgreSQL and MySQL GUI with data grid, schema builder and interactive charts.
It also has query builder, raw query editor with auto-complete, team collaboration features like connection, query and chart sharing among team members.

=== EDB Postgres Enterprise Manager ===

http://www.enterprisedb.com/products/postgres-enterprise-manager

Windows, Mac OS X, Linux

Postgres Enterprise Manager is the only solution available today that allows you to intelligently manage, monitor, and tune large scale Postgres installations from a single GUI console.

Monitoring features include: server auto-discovery, over 225 pre-configured ready to run probes, custom probes, alert management, personalized alerts, remote monitoring, versatile charting, custom dashboards and web client.

DBA tools include: database objects management, Postgres Expert (best practice configuration settings), Audit Manager, Log Manager, Log Analysis Expert, Capacity Manager and Team Support.

Developer tools include: Query Tool, Data Grid, SQL Profiler, SQL Debugger and Import tools.

Tuning tools include: At-A-Glance performance dashboards, Tuning Wizard, Performance Diagnostics and Index Advisor.

=== ClusterControl by Severalnines ===

https://severalnines.com/product/clustercontrol/for_postgresql

ClusterControl is an all-inclusive open source database management system that allows you to deplore, monitor, manage and scale your database environments. ClusterControl provides the basic functionality you need to get PostgreSQL up-and-running using our deployment wizard, monitoring and basic management abilities like automatic failover, backups, and restores.

* Point and Click Replication Deployments - ClusterControl allows you to easily deploy and configure master/slave replication PostgreSQL instances.
* Advanced Performance Monitoring - ClusterControl monitors queries and detects anomalies with built-in alerts.
* Automated Failover Handling - ClusterControl detects master failures and automatically promotes a new master
* Database Automation - ClusterControl lets you manage configurations, schedule, and restore backups.

== No longer Supported/Developed ==

* OpenOffice postgresql SDBC Driver. no work on the project since 2010; last version was a beta. http://www.openoffice.org/dba/drivers/postgresql/index.html
* RedHat: hasn't been refreshed since Pg 8.4. http://sources.redhat.com/rhdb
* SQuirrel: website 404. http://squirrel-sql.sourceforge.net/

Don't Do This

2018-07-19T05:44:11Z

Dfetter: /* When should you? */

A short list of common mistakes.

== Don't use psql -W or --password ==

Don't use <tt>psql -W</tt> or <tt>psql --password</tt>.

=== Why not? ===

Using the --password or -W flags will tell [https://www.postgresql.org/docs/current/static/reference-client.html psql] to prompt you for a password, before trying to connect to the server - so you'll be prompted for a password even if the server doesn't require one.

It's never required, as if the server does require a password psql will prompt you for one, and it can be very confusing when setting up permissions. If you're connecting with -W to a server configured to allow you access via <tt>peer</tt> authentication you may think that it's requiring a password when it really isn't. And if the user you're logging in as doesn't have a password set or you enter the wrong password at the prompt you'll still be logged in and think you have the right password - but you won't be able to log in from other clients (that connect via localhost) or when logged in as other users.

=== When should you? ===

Never, pretty much. It will save a round trip to the server but that's about it.

== Don't use NOT IN ==

Don't use <code>NOT IN</code>, or any combination of <code>NOT</code> and <code>IN</code> such as <code>NOT (x IN (select...))</code>.

=== Why not? ===

Two reasons:

1. <code>NOT IN</code> behaves in unexpected ways if there is a null present:

<code>select * from foo where col not in (1,null); -- always returns 0 rows</code>

<code>select * from foo where col not in (select x from bar);
-- returns 0 rows if any value of bar.x is null</code>

This happens because <code>col IN (1,null)</code> returns <code>TRUE</code> if col=1, and <code>NULL</code> otherwise (i.e. it can never return <code>FALSE</code>). Since <code>NOT (TRUE)</code> is <code>FALSE</code>, but <code>NOT (NULL)</code> is still <code>NULL</code>, there is no way that <code>NOT (col IN (1,null))</code> (which is the same thing as <code>col NOT IN (1,null)</code>) can return <code>TRUE</code> under any circumstances.

2. Because of point 1 above, <code>NOT IN (SELECT ...)</code> does not optimize very well. In particular, the planner can't transform it into an anti-join, and so it becomes either a hashed Subplan or a plain Subplan. The hashed subplan is fast, but the planner only allows that plan for small result sets; the plain subplan is '''horrifically''' slow (in fact O(N²)). This means that the performance can look good in small-scale tests but then slow down by 5 or more orders of magnitude once a size threshold is crossed; you '''do not''' want this to happen.

=== When should you? ===

<code>NOT IN (list,of,values,...)</code> is mostly safe ''unless'' you might have a null in the list (via a parameter or otherwise). So it's sometimes natural and even advisable to use it when excluding specific constant values from a query result.

== Don't use timestamp (without time zone) ==

Don't use the <tt>timestamp</tt> type to store timestamps, use <tt>timestamptz</tt> (also known as <tt>timestamp with time zone</tt>) instead.

=== Why not? ===

<tt>timestamptz</tt> records a single moment in time. Despite what the name says it doesn't store a timestamp, just a point in time described as the number of microseconds since January 1st, 2000 in UTC. You can insert values in any timezone and it'll store the point in time that value describes. By default it will display times in your current timezone, but you can use <tt>at time zone</tt> to display it in other time zones.

Because it stores a point in time it will do the right thing with arithmetic involving timestamps entered in different timezones - including between timestamps from the same location on different sides of a daylight savings time change.

<tt>timestamp</tt> (also known as <tt>timestamp without time zone</tt>) doesn't do any of that, it just stores a date and time you give it. You can think of it being a picture of a calendar and a clock rather than a point in time. Without additional information - the timezone - you don't know what time it records. Because of that, arithmetic between timestamps from different locations or between timestamps from summer and winter may give the wrong answer.

So if what you want to store is a point in time, rather than a picture of a clock, use timestamptz.

[https://it.toolbox.com/blogs/josh-berkus/zone-of-misunderstanding-092811 More about timestamptz].

=== When should you? ===

If you're dealing with timestamps in an abstract way, or just saving and retrieving them from an app, where you aren't going to be doing arithmetic with them then timestamp might be suitable.

== Don't use money ==

The <tt>money</tt> data type isn't actually very good for storing monetary values. Numeric, or (rarely) integer may be better.

=== Why not? ===

[https://www.postgresql.org/message-id/flat/20130328092819.237c0106@imp#20130328092819.237c0106@imp lots of reasons.]

It's a fixed-point type, implemented as a machine int, so arithmetic with it is fast. But it doesn't handle fractions of a cent (or equivalents in other currencies), it's rounding behaviour is probably not what you want.

It doesn't store a currency with the value, rather assuming that all money columns contain the currency specified by the database's [https://www.postgresql.org/docs/current/static/runtime-config-client.html#GUC-LC-MONETARY lc_monetary] locale setting. If you change the lc_monetary setting for any reason, all money columns will contain the wrong value. That means that if you insert '$10.00' while lc_monetary is set to 'en_US.UTF-8' the value you retrieve may be '10,00 Lei' or '¥1,000' if lc_monetary is changed.

Storing a value as a numeric, possibly with the currency being used in an adjacent column, might be better.

=== When should you? ===

If you're only working in a single currency, aren't dealing with fractional cents and are only doing addition and subtraction then money might be the right thing.

== Don't use timetz ==

Don't use the <tt>timetz</tt> type. You probably want <tt>timestamptz</tt> instead.

=== Why not? ===

Even the manual tells you it's only implemented for SQL compliance.

<blockquote>The type time with time zone is defined by the SQL standard, but the definition exhibits properties which lead to questionable usefulness. In most cases, a combination of date, time, timestamp without time zone, and timestamp with time zone should provide a complete range of date/time functionality required by any application.</blockquote>

=== When should you? ===

Never.

== Don't use upper case table or column names ==

Don't use NamesLikeThis, use names_like_this.

=== Why not? ===

PostgreSQL folds all names - of tables, columns, functions and everything else - to lower case unless they're "double quoted".

So <tt>create table Foo()</tt> will create a table called <tt>foo</tt>, while <tt>create table "Bar"()</tt> will create a table called <tt>Bar</tt>.

These select commands will work: <tt>select * from Foo</tt>, <tt>select * from foo</tt>, <tt>select * from "Bar"</tt>.

These will fail with "no such table": <tt>select * from "Foo"</tt>, <tt>select * from Bar</tt>, <tt>select * from bar</tt>.

This means that if you use uppercase characters in your table or column names you have to either ''always'' double quote them or ''never'' double quote them. That's annoying enough by hand, but when you start using other tools to access the database, some of which always quote all names and some don't, it gets very confusing.

Stick to using a-z, 0-9 and underscore for names and you never have to worry about quoting them.

=== When should you? ===

If it's important that "pretty" names are displaying in report output then you might want to use them. But you can also use column aliases to use lower case names in a table and still get pretty names in the output of a query: <tt>select character_name as "Character Name" from foo</tt>.

== Don't use char(n) ==

Don't use the type <tt>char(n)</tt>. You probably want <tt>text</tt>.

=== Why not? ===

char(n) is a fixed width type, and any string you insert into it will be padded with spaces to that fixed width. That's probably not what you actually want.

The manual says:

<blockquote>Values of type character are physically padded with spaces to the specified width n, and are stored and displayed that way. However, trailing spaces are treated as semantically insignificant and disregarded when comparing two values of type character. In collations where whitespace is significant, this behavior can produce unexpected results; for example SELECT 'a '::CHAR(2) collate "C" < E'a\n'::CHAR(2) returns true, even though C locale would consider a space to be greater than a newline. Trailing spaces are removed when converting a character value to one of the other string types. Note that trailing spaces are semantically significant in character varying and text values, and when using pattern matching, that is LIKE and regular expressions.</blockquote>

That should scare you off it.

It being a fixed width type does waste space, but doesn't make operations on it any faster.

=== When should you? ===

When you're porting very, very old software that uses fixed width fields. Or when you read the snippet from the manual above and think "yes, that makes perfect sense and is a good match for my requirements" rather than gibbering and running away.

== Don't use varchar(n) by default ==

Don't use the type <tt>varchar(n)</tt> by default. Consider <tt>varchar</tt> (without the length limit) or <tt>text</tt> instead.

=== Why not? ===

<tt>varchar(n)</tt> is a variable width text field that will throw an error if you try and insert a string longer than n characters (not bytes) into it.

<tt>varchar</tt> (without the <tt>(n)</tt>) or <tt>text</tt> are similar, but without the length limit. If you insert the same string into the three field types they will take up exactly the same amount of space, and you won't be able to measure any difference in performance.

If what you really need is a text field with an length limit then varchar(n) is great, but if you pick an arbitrary length and choose varchar(20) for a surname field you're risking production errors in the future when Hubert Blaine Wolfeschlegelsteinhausenbergerdorff signs up for your service.

Some databases don't have a type that can hold arbitrary long text, or if they do it's not as convenient or efficient or well-supported as varchar(n). Users from those databases will often use something like <tt>varchar(255)</tt> when what they really want is <tt>text</tt>.

If you need to constrain the value in a field you probably need something more specific than a maximum length - maybe a minimum length too, or a limited set of characters - and a [https://www.postgresql.org/docs/current/static/ddl-constraints.html#DDL-CONSTRAINTS-CHECK-CONSTRAINTS check constraint] can do all of those things as well as a maximum string length.

=== When should you? ===

When you want to, really. If what you want is a text field that will throw an error if you insert too long a string into it, and you don't want to use an explicit check constraint then varchar(n) is a perfectly good type. Just don't use it automatically without thinking about it.

== Don't use rules ==

Don't use [https://www.postgresql.org/docs/current/static/sql-createrule.html rules]. If you think you want to, use a [https://www.postgresql.org/docs/current/static/plpgsql-trigger.html trigger] instead.

=== Why not? ===

Rules are incredibly powerful, but they don't do what they look like they do. They look like they're some conditional logic, but they actually rewrite a query to modify it or add additional queries to it.

That means that [http://blog.rhodiumtoad.org.uk/2010/06/21/the-rule-challenge/ all non-trivial rules are incorrect].

Depesz has [https://www.depesz.com/2010/06/15/to-rule-or-not-to-rule-that-is-the-question/ more to say] about them.

=== When should you? ===

Never. While the rewriter is an implementation detail of VIEWs, there is no reason to pry up this cover plate directly.

== Don't use BETWEEN (especially with timestamps) ==

=== Why not? ===

<code>BETWEEN</code> uses a closed-interval comparison: the values of both ends of the specified range are included in the result.

This is a particular problem with queries of the form

<code>SELECT * FROM blah WHERE timestampcol BETWEEN '2018-06-01' AND '2018-06-08'</code>

This will include results where the timestamp is ''exactly'' 2018-06-08 00:00:00.000000, but not timestamps later in that same day. So the query might seem to work, but as soon as you get an entry exactly on midnight, you'll end up double-counting it.

Instead, do:

<code>SELECT * FROM blah WHERE timestampcol >= '2018-06-01' AND timestampcol < '2018-06-08'</code>

=== When should you? ===

<code>BETWEEN</code> is safe for discrete quantities like integers or dates, as long as you remember that both ends of the range are included in the result. But it's a bad habit to get into.

Don't Do This

2018-07-19T05:41:15Z

Dfetter: Reverted edits by Elein (talk) to last revision by Rhodiumtoad

A short list of common mistakes.

== Don't use psql -W or --password ==

Don't use <tt>psql -W</tt> or <tt>psql --password</tt>.

=== Why not? ===

Using the --password or -W flags will tell [https://www.postgresql.org/docs/current/static/reference-client.html psql] to prompt you for a password, before trying to connect to the server - so you'll be prompted for a password even if the server doesn't require one.

It's never required, as if the server does require a password psql will prompt you for one, and it can be very confusing when setting up permissions. If you're connecting with -W to a server configured to allow you access via <tt>peer</tt> authentication you may think that it's requiring a password when it really isn't. And if the user you're logging in as doesn't have a password set or you enter the wrong password at the prompt you'll still be logged in and think you have the right password - but you won't be able to log in from other clients (that connect via localhost) or when logged in as other users.

=== When should you? ===

Never, pretty much. It will save a round trip to the server but that's about it.

== Don't use NOT IN ==

Don't use <code>NOT IN</code>, or any combination of <code>NOT</code> and <code>IN</code> such as <code>NOT (x IN (select...))</code>.

=== Why not? ===

Two reasons:

1. <code>NOT IN</code> behaves in unexpected ways if there is a null present:

<code>select * from foo where col not in (1,null); -- always returns 0 rows</code>

<code>select * from foo where col not in (select x from bar);
-- returns 0 rows if any value of bar.x is null</code>

This happens because <code>col IN (1,null)</code> returns <code>TRUE</code> if col=1, and <code>NULL</code> otherwise (i.e. it can never return <code>FALSE</code>). Since <code>NOT (TRUE)</code> is <code>FALSE</code>, but <code>NOT (NULL)</code> is still <code>NULL</code>, there is no way that <code>NOT (col IN (1,null))</code> (which is the same thing as <code>col NOT IN (1,null)</code>) can return <code>TRUE</code> under any circumstances.

2. Because of point 1 above, <code>NOT IN (SELECT ...)</code> does not optimize very well. In particular, the planner can't transform it into an anti-join, and so it becomes either a hashed Subplan or a plain Subplan. The hashed subplan is fast, but the planner only allows that plan for small result sets; the plain subplan is '''horrifically''' slow (in fact O(N²)). This means that the performance can look good in small-scale tests but then slow down by 5 or more orders of magnitude once a size threshold is crossed; you '''do not''' want this to happen.

=== When should you? ===

<code>NOT IN (list,of,values,...)</code> is mostly safe ''unless'' you might have a null in the list (via a parameter or otherwise). So it's sometimes natural and even advisable to use it when excluding specific constant values from a query result.

== Don't use timestamp (without time zone) ==

Don't use the <tt>timestamp</tt> type to store timestamps, use <tt>timestamptz</tt> (also known as <tt>timestamp with time zone</tt>) instead.

=== Why not? ===

<tt>timestamptz</tt> records a single moment in time. Despite what the name says it doesn't store a timestamp, just a point in time described as the number of microseconds since January 1st, 2000 in UTC. You can insert values in any timezone and it'll store the point in time that value describes. By default it will display times in your current timezone, but you can use <tt>at time zone</tt> to display it in other time zones.

Because it stores a point in time it will do the right thing with arithmetic involving timestamps entered in different timezones - including between timestamps from the same location on different sides of a daylight savings time change.

<tt>timestamp</tt> (also known as <tt>timestamp without time zone</tt>) doesn't do any of that, it just stores a date and time you give it. You can think of it being a picture of a calendar and a clock rather than a point in time. Without additional information - the timezone - you don't know what time it records. Because of that, arithmetic between timestamps from different locations or between timestamps from summer and winter may give the wrong answer.

So if what you want to store is a point in time, rather than a picture of a clock, use timestamptz.

[https://it.toolbox.com/blogs/josh-berkus/zone-of-misunderstanding-092811 More about timestamptz].

=== When should you? ===

If you're dealing with timestamps in an abstract way, or just saving and retrieving them from an app, where you aren't going to be doing arithmetic with them then timestamp might be suitable.

== Don't use money ==

The <tt>money</tt> data type isn't actually very good for storing monetary values. Numeric, or (rarely) integer may be better.

=== Why not? ===

[https://www.postgresql.org/message-id/flat/20130328092819.237c0106@imp#20130328092819.237c0106@imp lots of reasons.]

It's a fixed-point type, implemented as a machine int, so arithmetic with it is fast. But it doesn't handle fractions of a cent (or equivalents in other currencies), it's rounding behaviour is probably not what you want.

It doesn't store a currency with the value, rather assuming that all money columns contain the currency specified by the database's [https://www.postgresql.org/docs/current/static/runtime-config-client.html#GUC-LC-MONETARY lc_monetary] locale setting. If you change the lc_monetary setting for any reason, all money columns will contain the wrong value. That means that if you insert '$10.00' while lc_monetary is set to 'en_US.UTF-8' the value you retrieve may be '10,00 Lei' or '¥1,000' if lc_monetary is changed.

Storing a value as a numeric, possibly with the currency being used in an adjacent column, might be better.

=== When should you? ===

If you're only working in a single currency, aren't dealing with fractional cents and are only doing addition and subtraction then money might be the right thing.

== Don't use timetz ==

Don't use the <tt>timetz</tt> type. You probably want <tt>timestamptz</tt> instead.

=== Why not? ===

Even the manual tells you it's only implemented for SQL compliance.

<blockquote>The type time with time zone is defined by the SQL standard, but the definition exhibits properties which lead to questionable usefulness. In most cases, a combination of date, time, timestamp without time zone, and timestamp with time zone should provide a complete range of date/time functionality required by any application.</blockquote>

=== When should you? ===

Never.

== Don't use upper case table or column names ==

Don't use NamesLikeThis, use names_like_this.

=== Why not? ===

PostgreSQL folds all names - of tables, columns, functions and everything else - to lower case unless they're "double quoted".

So <tt>create table Foo()</tt> will create a table called <tt>foo</tt>, while <tt>create table "Bar"()</tt> will create a table called <tt>Bar</tt>.

These select commands will work: <tt>select * from Foo</tt>, <tt>select * from foo</tt>, <tt>select * from "Bar"</tt>.

These will fail with "no such table": <tt>select * from "Foo"</tt>, <tt>select * from Bar</tt>, <tt>select * from bar</tt>.

This means that if you use uppercase characters in your table or column names you have to either ''always'' double quote them or ''never'' double quote them. That's annoying enough by hand, but when you start using other tools to access the database, some of which always quote all names and some don't, it gets very confusing.

Stick to using a-z, 0-9 and underscore for names and you never have to worry about quoting them.

=== When should you? ===

If it's important that "pretty" names are displaying in report output then you might want to use them. But you can also use column aliases to use lower case names in a table and still get pretty names in the output of a query: <tt>select character_name as "Character Name" from foo</tt>.

== Don't use char(n) ==

Don't use the type <tt>char(n)</tt>. You probably want <tt>text</tt>.

=== Why not? ===

char(n) is a fixed width type, and any string you insert into it will be padded with spaces to that fixed width. That's probably not what you actually want.

The manual says:

<blockquote>Values of type character are physically padded with spaces to the specified width n, and are stored and displayed that way. However, trailing spaces are treated as semantically insignificant and disregarded when comparing two values of type character. In collations where whitespace is significant, this behavior can produce unexpected results; for example SELECT 'a '::CHAR(2) collate "C" < E'a\n'::CHAR(2) returns true, even though C locale would consider a space to be greater than a newline. Trailing spaces are removed when converting a character value to one of the other string types. Note that trailing spaces are semantically significant in character varying and text values, and when using pattern matching, that is LIKE and regular expressions.</blockquote>

That should scare you off it.

It being a fixed width type does waste space, but doesn't make operations on it any faster.

=== When should you? ===

When you're porting very, very old software that uses fixed width fields. Or when you read the snippet from the manual above and think "yes, that makes perfect sense and is a good match for my requirements" rather than gibbering and running away.

== Don't use varchar(n) by default ==

Don't use the type <tt>varchar(n)</tt> by default. Consider <tt>varchar</tt> (without the length limit) or <tt>text</tt> instead.

=== Why not? ===

<tt>varchar(n)</tt> is a variable width text field that will throw an error if you try and insert a string longer than n characters (not bytes) into it.

<tt>varchar</tt> (without the <tt>(n)</tt>) or <tt>text</tt> are similar, but without the length limit. If you insert the same string into the three field types they will take up exactly the same amount of space, and you won't be able to measure any difference in performance.

If what you really need is a text field with an length limit then varchar(n) is great, but if you pick an arbitrary length and choose varchar(20) for a surname field you're risking production errors in the future when Hubert Blaine Wolfeschlegelsteinhausenbergerdorff signs up for your service.

Some databases don't have a type that can hold arbitrary long text, or if they do it's not as convenient or efficient or well-supported as varchar(n). Users from those databases will often use something like <tt>varchar(255)</tt> when what they really want is <tt>text</tt>.

If you need to constrain the value in a field you probably need something more specific than a maximum length - maybe a minimum length too, or a limited set of characters - and a [https://www.postgresql.org/docs/current/static/ddl-constraints.html#DDL-CONSTRAINTS-CHECK-CONSTRAINTS check constraint] can do all of those things as well as a maximum string length.

=== When should you? ===

When you want to, really. If what you want is a text field that will throw an error if you insert too long a string into it, and you don't want to use an explicit check constraint then varchar(n) is a perfectly good type. Just don't use it automatically without thinking about it.

== Don't use rules ==

Don't use [https://www.postgresql.org/docs/current/static/sql-createrule.html rules]. If you think you want to, use a [https://www.postgresql.org/docs/current/static/plpgsql-trigger.html trigger] instead.

=== Why not? ===

Rules are incredibly powerful, but they don't do what they look like they do. They look like they're some conditional logic, but they actually rewrite a query to modify it or add additional queries to it.

That means that [http://blog.rhodiumtoad.org.uk/2010/06/21/the-rule-challenge/ all non-trivial rules are incorrect].

Depesz has [https://www.depesz.com/2010/06/15/to-rule-or-not-to-rule-that-is-the-question/ more to say] about them.

=== When should you? ===

Probably never. If you're doing something like "ON SELECT DO INSTEAD SELECT" you can probably use a view instead.

== Don't use BETWEEN (especially with timestamps) ==

=== Why not? ===

<code>BETWEEN</code> uses a closed-interval comparison: the values of both ends of the specified range are included in the result.

This is a particular problem with queries of the form

<code>SELECT * FROM blah WHERE timestampcol BETWEEN '2018-06-01' AND '2018-06-08'</code>

This will include results where the timestamp is ''exactly'' 2018-06-08 00:00:00.000000, but not timestamps later in that same day. So the query might seem to work, but as soon as you get an entry exactly on midnight, you'll end up double-counting it.

Instead, do:

<code>SELECT * FROM blah WHERE timestampcol >= '2018-06-01' AND timestampcol < '2018-06-08'</code>

=== When should you? ===

<code>BETWEEN</code> is safe for discrete quantities like integers or dates, as long as you remember that both ends of the range are included in the result. But it's a bad habit to get into.

PostgreSQL 11 Open Items

2018-05-08T23:54:44Z

Dfetter: /* Important Dates */

== Open Issues ==

* [https://www.postgresql.org/message-id/d8ja7ubjnyp.fsf@dalvik.ping.uio.no JSONB PL/Perl transform bugs]

* [http://postgr.es/m/86137f17-1dfb-42f9-7421-82fd786b04a1@anayrat.info Explain buffers wrong counter with parallel plans]
** reported as a possible defect in commit 01edb5c7fc3bcf6aea15f2b3be36189b52ad9d1a

* [https://www.postgresql.org/message-id/CAH2-WzkOKptQiE51Bh4_xeEHhaBwHkZkGtKizrFMgEkfUuRRQg%40mail.gmail.com Local partitioned indexes and pageinspect]

* [http://postgr.es/m/877eovbjc3.fsf@news-spur.riddles.org.uk breakage calling a procedure with a toasted parameter]

* [https://www.postgresql.org/message-id/ff8f9bfa485ff961d6bb43e54120485b@postgrespro.ru Crash with partition pruning with handling of ArrayCoerceExpr]

== Decisions to Recheck Mid-Beta ==

* [https://www.postgresql.org/message-id/20180328212751.eskdxpljte6ga6wu@alap3.anarazel.de reconsider jit=on default shortly before release]

== Older Bugs ==

=== Live issues ===

* [https://www.postgresql.org/message-id/20153.1523471686%40sss.pgh.pa.us IsInParallelMode() check in set_config_option is wrong (was: WARNING in parallel index creation)]
* [https://www.postgresql.org/message-id/20180309075538.GD9376@paquier.xyz Fixes for missing schema qualifications]
* [https://www.postgresql.org/message-id/CAFiTN-u4BA8KXcQUWDPNgaKAjDXC=C2whnzBM8TAcv=stckYUw@mail.gmail.com Allocation done in critical section when initializing WAL]
* [https://www.postgresql.org/message-id/AD7252BEFBCA3846A8D34ABCDA258D080120F025C6@EXMBX05.mailcloud.dk pg_dump misses public role on schema public]

* [https://www.postgresql.org/message-id/87lgdyz1wj.fsf@ars-thinkpad Fix slot's xmin advancement and subxact's lost snapshots in decoding]
* [https://www.postgresql.org/message-id/1519917758.6586.8.camel@cybertec.at SHOW ALL does not honor pg_read_all_settings membership]

=== Fixed issues ===

* [https://www.postgresql.org/message-id/20170117.193645.160386781.horiguchi.kyotaro@lab.ntt.co.jp Continued WAL record can prevent standby from startup]
** Fixed in: {{PgCommitURL|0668719801838aa6a8bda330ff9b3d20097ea844}}
* [https://www.postgresql.org/message-id/3AD85097-A3F3-4EBA-99BD-C38EDF8D2949@postgrespro.ru FinishPreparedTransaction missing HOLD_INTERRUPTS section]
** Fixed in: {{PgCommitURL|8f9be261f43772ccee2eae94d971bac6557cbe6a}}

== Non-bugs ==

== Resolved Issues ==

=== resolved before 11beta1 ===

* [https://www.postgresql.org/message-id/2018041911380869070310%40i-soft.com.cn Memory leaks with _SPI_stack handling in TopMemoryContext]
** Regression caused by commit 8561e48.
** Fixed in: {{PgCommitURL|30c66e77be1d890c3cca766259c0bec80bcac1b5}}

* [https://www.postgresql.org/message-id/5AD4882B.10002%40lab.ntt.co.jp Oddity in tuple routing for foreign partitions]
** Fixed in: {{PgCommitURL|37a3058bc7c8224d4c0d8b36176d821636a1f90e}}

* [https://www.postgresql.org/message-id/20180419052436.GA16000%40paquier.xyz Corrupted btree index on HEAD because of covering indexes]
** Fixed in: {{PgCommitURL|6db4b49986be3fe59a1f6ba6fabf9852864efc3e}}

* [https://www.postgresql.org/message-id/flat/CAFjFpRcwq7G16J_w%2Byy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA%40mail.gmail.com#CAFjFpRcwq7G16J_w+yy_xiE7daD0Bm6iYTnhz81f79yrSOn4DA@mail.gmail.com Decide if we want a GUC to disable partition pruning]
** Fixed in: {{PgCommitURL|055fb8d33da6ff9003e3da4b9944bdcd2e2b2a49}}

* [https://www.postgresql.org/message-id/2b02f1e9-9812-9c41-972d-517bdc0f815d%40lab.ntt.co.jp Fix partition pruning for the cases where partition key is of array, enum, record, or range type]
** [https://www.postgresql.org/message-id/69879396-3a63-8fa9-2fa7-4fd1035b9623%40lab.ntt.co.jp Patch exists]
** Bug fix: {{PgCommitURL|e5dcbb88a15d445e0ccb3db3194f4a122b792df6}}

* [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Run-time pruning and Parallel Append don't work properly together]
** [https://www.postgresql.org/message-id/CAKJS1f-tux=KdUz6ENJ9GHM_V2qgxysadYiOyQS9Ko9PTteVhQ@mail.gmail.com Patch exists]
** Bug fixes: {{PgCommitURL|47c91b55991883322fdbc4495ce7fe6b2166e8fe}} {{PgCommitURL|4d0f6d3f207d}} {{PgCommitURL|b47a86f5008f2674af20dd00bc233e7b74e01bba}}

* [https://www.postgresql.org/message-id/87woxi24uw.fsf@ansel.ydns.eu expand_tuple segfaults]
** coverage report shows it's completely untested, too
** Bug fix: {{PgCommitURL|7c44c46deb495a2f3861f402d7f2109263e3d50a}}
** Add coverage: {{PgCommitURL|b39fd897e0398a6bdc6552daa7cacdf9c0e46d7e}}

* [https://www.postgresql.org/message-id/96cf4a6c-49ad-fa92-0d41-e4b911086dab%40lab.ntt.co.jp Handling of whole-row vars in ON CONFLICT on partitioned tables]
** Bug fix: {{PgCommitURL|158b7bc6d77948d2f474dc9f2777c87f81d1365a}}

* [https://www.postgresql.org/message-id/12085bc4-0bc6-0f3a-4c43-57fe0681772b@lab.ntt.co.jp relispartition for index partitions]
** Bug fix: {{PgCommitURL|9e9befac4a2228ae8a5309900645ecd8ead69f53}}

* [https://www.postgresql.org/message-id/CAGPqQf0W%2Bv-Ci_qNV_5R3A%3DZ9LsK4%2BjO7LzgddRncpp_rrnJqQ%40mail.gmail.com failure to validate default partition's constraint when attaching after4dba331cb3]
** [https://www.postgresql.org/message-id/487870f2-d538-9d07-13e8-4ca390e27d18%40lab.ntt.co.jp Patch exists]
** Bug fix: {{PgCommitURL|72cf7f310c0729a331f321fad39835ac886603dc}}

* [https://www.postgresql.org/message-id/87in923lyw.fsf@ansel.ydns.eu Failed assertion on pfree() via perform_pruning_combine_step]
** Original commit: {{PgCommitURL|9fdb675fc5d2de825414e05939727de8b120ae81}}
** Bug fix: {{PgCommitURL|7ba6ee815dc90d4fab7226d343bf72aa28c9aa5c}}

* [https://www.postgresql.org/message-id/CAH2-WzkryAPcQOHBJKuDKfni-HGFny31yjcbM-yp5HO-71iCdw@mail.gmail.com Parallel index workers don't have activity set]
** Original commit: {{PgCommitURL|9da0cc35284bdbe8d442d732963303ff0e0a40bc}}
** Bug fix: {{PgCommitURL|7de4a1bcc56f494acbd0d6e70781df877dc8ecb5}}

* [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz check_ssl_key_file_permissions should be in be-secure-common.c]
** Original commit: {{PgCommitURL|8a3d9425290ff5f6434990349886afae9e1c6008}}
** [https://www.postgresql.org/message-id/20180402065149.GC1908%40paquier.xyz Patch exists]
** Bug fix: {{PgCommitURL|2764d5dcfa84d240c901c20ec6e194f72d82b78a}}

* [https://www.postgresql.org/message-id/flat/CAFjFpRcOTHZSFfHNwhAe4DmS%2BqvWmqK_UW3QF3wG8e0pAKW0tA%40mail.gmail.com#CAFjFpRcOTHZSFfHNwhAe4DmS+qvWmqK_UW3QF3wG8e0pAKW0tA@mail.gmail.com Missing break statement after transformCallStmt in transformStmt]
** Original commit: {{PgCommitURL|76b6aa41f41db66004b1c430f17a546d4102fbe7}}
** Bug fix: {{PgCommitURL|13c7c65ec900a30bcddcb27f5fd138dcdbc2ca2e}}

* [https://www.postgresql.org/message-id/CAKJS1f91kq1wfYR8rnRRfKtxyhU2woEA+=whd640UxMyU+O0EQ@mail.gmail.com Parallel index creation does not properly clean up after error]
** Original commit: {{PgCommitURL|29d58fd3adae9057c3fd502393b2f131bc96eaf9}}
** Bug fix: {{PgCommitURL|47cb9ca49a611fa518e1a0fe46526507c96a5612}}

* [https://www.postgresql.org/message-id/30721.1519750231@sss.pgh.pa.us pg_proc.prokind change means we need server-version-dependent tab completion in psql]
** [https://www.postgresql.org/message-id/24314.1520190408@sss.pgh.pa.us Proposed patch]

* [https://www.postgresql.org/message-id/20180409010031.GA11599%40paquier.xyz "make -j 4 install" broken after running configure]
** Bug fix: {{PgCommitURL|3b8f6e75f3c8c6d192621f21624cc8cee04ec3cb}}

* [https://www.postgresql.org/message-id/152056616579.4966.583293218357089052@wrigleys.postgresql.org OpenTransientFile() should be paired with CloseTransientFile() rather than close()]
** Bug fix: {{PgCommitURL|231bcd0803eb91c526d4e7522c993fa5ed71bd45}}

* [https://www.postgresql.org/message-id/20180409051112.GC1740%40paquier.xyz Fix pg_rewind which can be run as root user]
** Bug fix: {{PgCommitURL|5d5aeddabfe0b6b21f556c72a71e0454833d63e5}}

* [https://www.postgresql.org/message-id/CAMyN-kA7aOJzBmrYFdXcc7Z0NmW+5jBaf_m=_-77uRNyKC9r=A@mail.gmail.com Fix for pg_stat_activity putting client hostaddr into appname field]
** Bug fix: {{PgCommitURL|a820b4c32946c499a2d19846123840a0dad071b5}} and {{PgCommitURL|811969b218ac2e8030dfbbb05873344967461618}}

* [https://www.postgresql.org/message-id/CAFj8pRCgQ5_O4YL4ZKC5=6Oi7DW_q4xB7==_iN2yRKq7+1Tv9Q@mail.gmail.com Missing support of named convention for procedures]
** Bug fix: {{PgCommitURL|a8677e3ff6bb8ef78a9ba676faa647bba237b1c4}}

* [https://www.postgresql.org/message-id/20180410042147.GB1552%40paquier.xyz Gotchas about pg_verify_checksums]

* [https://www.postgresql.org/message-id/20180411001058.GJ26769%40paquier.xyz pg_verify_checksums does not check after all-zero'd pages]

* [https://www.postgresql.org/message-id/20180411075223.GB19732%40paquier.xyz Typos from the original patch]

* [https://www.postgresql.org/message-id/20180411082020.GD19732%40paquier.xyz Fixes for the documentation]

* [https://www.postgresql.org/message-id/5767.1523995174@sss.pgh.pa.us Repeated crashes in GENERATED ... AS IDENTITY tests]
** Bug fix: {{PgCommitURL|b1b71f16581fb5385fa9f9a663ffee271cdfaba5}}
** Bug fix: {{PgCommitURL|676858bcb4c4d9d2d5ee63a87dbff01085984ee0}}

* [https://www.postgresql.org/message-id/flat/CAKJS1f-BL%2Br5FXSejDu%3D%2BMAvzRARaawRnQ_ZFtbv_o6tha9NJw%40mail.gmail.com Partitions with bool partition keys]

* [https://www.postgresql.org/message-id/3041e853-b1dd-a0c6-ff21-7cc5633bffd0%40lab.ntt.co.jp wrong memory context used in FmgrInfo's contained in PartitionKey]
** Bug fix (HEAD): {{PgCommitURL|a4d56f583e7cff052c2699e62d867ae1c8fda4f3}}
** Bug fix (PG 10): {{PgCommitURL|5f11c6ec61a579d60347a5d13af7e42b17fadc56}}

* [https://www.postgresql.org/message-id/20180422111100.GA1393%40paquier.xyz BGWORKER_BYPASS_ALLOWCONN used nowhere (infra part of on-line checksum switcher)]
** Bug fix: {{PgCommitURL|9cad926eb876a30d58a5b39789098da83a6ef91c}}
** Bug fix: {{PgCommitURL|43cc4ee6340779f2a17fb5bab27355c2cb2e23a6}}

* [https://www.postgresql.org/message-id/87po3a3n46.fsf@ansel.ydns.eu Failed assertion in create_gather_path]
** Bug fix: {{PgCommitURL|dc1057fcd878d5c062c5c4c2b548af2be513b6ab}}

* [https://www.postgresql.org/message-id/20180428073935.GB1736%40paquier.xyz Cold welcoming message when installing anything because of LLVM bitcode stuff]

* [https://www.postgresql.org/message-id/CCAJrrPGedKiFE2fqntSauUfhapCksOJzam+QtHfSgx86LhXLeOQ@mail.gmail.com jitflags in _outPlannedStmt and _readPlannedStmt treated as bool type]
** Bug fix: {{PgCommitURL|cfffe83ba82021a1819a656e7ec5c28fb3a99152}}

* [https://www.postgresql.org/message-id/flat/20180413030828.GD1552%40paquier.xyz#20180413030828.GD1552@paquier.xyz wal_consistency_checking reports an inconsistency on master branch]
** Bug fix: {{PgCommitURL|1667148a4dd98cea28b8b53d57dbc1eece1b0b5c}}

* [https://www.postgresql.org/message-id/20180507001811.GA27389%40paquier.xyz Refreshing findoidjoins for v11]
** Bug fix: {{PgCommitURL|fbb99e5883d88687de4dbd832c2843f600ab3dd8}}

=== resolved before 11beta2 ===

This lists the open items fixed between the release of 11 beta1 and 11 beta2.

== Important Dates ==

Current schedule:
* feature freeze: 8th of April 2018
* beta1: 24th of April 2018 (planned)
* beta2: ZZZ

[[Category:Open_Items]]

Apt

2018-04-15T22:50:15Z

Dfetter: /* hic hoc hæc */

==PostgreSQL packages for Debian and Ubuntu==

The PostgreSQL Global Development Group (PGDG) maintains an APT repository of PostgreSQL packages for Debian and Ubuntu located at http://apt.postgresql.org/pub/repos/apt/.
We aim at building PostgreSQL server packages as well as extensions and modules packages on several Debian/Ubuntu releases for all PostgreSQL versions supported.

Currently, we support

* '''Debian 7''' (wheezy), '''8''' (jessie), '''9''' (stretch), and '''unstable''' (sid)
* '''Ubuntu '''14.04''' (trusty), '''16.04''' (xenial)
* Architectures: '''amd64''' (64-bit x86), '''i386''' (32-bit x86), '''ppc64el''' (little-endian 64-bit POWER; not on wheezy/precise)
* '''PostgreSQL 9.2, 9.3, 9.4, 9.5, 9.6, 10''',  [[Apt/FAQ#Development_snapshots|11devel]]
* Server extensions such as Slony-I, various PL languages, and datatypes
* Applications like pgadmin3, pgbouncer, and pgpool-II

Packages for older PostgreSQL versions and older Debian/Ubuntu distributions will continue to stay in the repository; updates for those will be provided on an ''ad hoc'' basis.

==Quickstart==

Create '''/etc/apt/sources.list.d/pgdg.list'''. The distributions are called ''codename'''''-pgdg'''. In the example, replace ''stretch'' with the actual distribution you are using:

<nowiki>deb http://apt.postgresql.org/pub/repos/apt/</nowiki> ''stretch''-pgdg main

(You may determine the codename of your distribution by running '''lsb_release -c'''). For a shorthand version of the above, presuming you are using a supported release:

<nowiki>sudo sh -c 'echo "deb http://apt.postgresql.org/pub/repos/apt/ $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list'</nowiki>

Import the repository key from '''https://www.postgresql.org/media/keys/ACCC4CF8.asc''', update the package lists, and start installing packages:

<nowiki>sudo apt-get install wget ca-certificates
wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add -</nowiki>
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install postgresql-10 pgadmin4 # on wheezy/jessie/trusty: pgadmin3

Alternately, [https://salsa.debian.org/postgresql/postgresql-common/raw/master/pgdg/apt.postgresql.org.sh this shell script] will automate the repository setup.
Note that the shell script leaves the source package repo (deb-src) commented out; if you need source packages, you will need to modify /etc/apt/sources.list.d/pgdg.list to enable it.


Have a look at the '''[[Apt/FAQ|FAQ]]'''.

'''Note:''' This repository provides "postgresql", "postgresql-contrib", and "postgresql-client" ''meta-packages'' that depend on the latest postgresql-x.y, ... packages, similar to the ones present in Debian and Ubuntu. Once a new PostgreSQL version is released, these meta-packages will be updated to depend on the new version. If you rather want to stay with a particular PostgreSQL version, you should install specific packages like "postgresql-10" instead of "postgresql".

For packages of development/alpha/beta versions of PostgreSQL, see the [[Apt/FAQ#I_want_to_try_the_beta_version_of_the_next_PostgreSQL_release|FAQ entry about beta versions]].

==News==

* 2018-01-17: Ubuntu zesty (17.04) is unsupported now, Ubuntu removed it from their mirrors
* 2017-10-05: PostgreSQL 10.0 has been released, postgresql-10 is the default version pulled in by "postgresql.deb" now
* 2017-05-18: PostgreSQL 10beta1 packages added, see [[Apt/FAQ#I_want_to_try_the_beta_version_of_the_next_PostgreSQL_release]]
* 2017-04-25: Ubuntu zesty (17.04) and Debian stretch (9) added, Ubuntu precise (12.04) deprecated: https://www.postgresql.org/message-id/20170425113312.d7odg7juvnunhtex%40msg.credativ.de
* 2017-02-23: postgresql-10 development snapshots available for sid, jessie, xenial, and trusty (via -pgdg-testing): [[Apt/FAQ#Development_snapshots]]
* 2016-09-29: ppc64el added as new architecture, along with full 9.6 support for all packages: https://www.postgresql.org/message-id/c86548a4-eea0-ff5d-9a14-1c136ef39ab6%402ndquadrant.it
* 2016-09-17: Ubuntu wily (15.10) deprecated.
* 2016-09-05: Redmine project for issue tracking: https://redmine.postgresql.org/projects/pgapt/issues
* 2016-07-31: Older versions of packages available: https://www.postgresql.org/message-id/20160731194944.amiwidhsoqh4osac%40msg.df7cb.de
* 2016-03-31: Ubuntu xenial (16.04) added.
* 2016-03-05: Debian squeeze (6) deprecated.

Older news items: [[Apt/OldNews]]

==Resources==

* [[Apt/FAQ|FAQ]]
* [http://apt.postgresql.org/pub/repos/apt/ Package repository]
* [https://qa.debian.org/developer.php?login=pkg-postgresql-public@lists.alioth.debian.org PostgreSQL in Debian]

===Contact===

* Mailing list: pgsql-pkg-debian@postgresql.org ([http://archives.postgresql.org/pgsql-pkg-debian/ Archives])
* IRC channel: #postgresql-apt @ irc.freenode.net

===Maintainers===

* Christoph Berg (credativ)
* Marco Nenciarini (2ndQuadrant)

====Past Contributors====

* Dimitri Fontaine
* Magnus Hagander

===Bugs===

Please report bugs:
* on the pgsql-pkg-debian@postgresql.org mailing list, or
* open an issue in [https://redmine.postgresql.org/projects/pgapt/issues Redmine], or
* open a bug in the [http://bugs.debian.org/ Debian BTS].

===Documentation===

* [[Apt/RepoDocs]]
* [[Apt/Jenkins]]
* [[Apt/NewPostgreSQLVersion]]

==Acknowledgements==

Work on setting up the archive was kindly supported by [http://www.credativ.de/ credativ], [http://www.2ndquadrant.com/ 2ndQuadrant], [http://redpill-linpro.com/ Redpill Linpro],
and funding from the European Union's Seventh Framework Programme (FP7/2007-2013) under grant agreement 258862.

The amd64/i386 build server is kindly hosted by [https://www.dg-i.net/ DG-i].
The ppc64el build server is kindly hosted by [http://www.ibm.com/ibm/clientcenter/montpellier/ IBM Power Systems Linux Center, Montpellier].
The archive is hosted on postgresql.org hardware.

Design Tools

2017-12-22T03:58:45Z

Dfetter:

Tools to help with designing a schema, via creating [[https://en.wikipedia.org/wiki/Entity–relationship_model Entity-Relationship diagrams]] and similar.

== Windows ==

=== Proprietary ===

==== Aqua Data Studio ====

http://www.aquafold.com/aquadatastudio/er_modeler.html

The Aqua Data Studio Entity Relationship Modeler (ER Modeler) helps you design complex database models for all major RDBMS vendors and versions. Use the Forward Engineer feature to model entities and convert them into SQL Scripts, or Reverse Engineer existing databases to visualize a database model.

==== DeZign ====

http://www.datanamic.com/dezign/index.html

Aan intuitive database design and modeling tool for developers and DBA's that can help you model, create and maintain databases. The software uses entity relationship diagrams (ERDs, data models) to graphically design databases and automatically generates the most popular SQL and desktop databases.

==== PostgreSQL Maestro ====

https://www.sqlmaestro.com/products/postgresql/maestro/

==== Toad Data Modeller ====

https://www.quest.com/products/toad-data-modeler/

Toad Data Modeler enables you to rapidly deploy accurate changes to data structures across more than 20 different platforms. It allows you to construct logical and physical data models, compare and synchronize models, quickly generate complex SQL/DDL, create and modify scripts, as well as reverse and forward engineer both databases and data warehouse systems.

May have free versions? Website is a bit of a wreck.

==== EMS SQL Manager ====

https://www.sqlmanager.net/en/products/postgresql/manager

=== Obsolete or End-of-Life ===

==== DB Designer Fork ====

https://sourceforge.net/projects/dbdesigner-fork/

DB Designer Fork is a fork of the fabFORCE DBDesigner 4. It integrates entity relationship design,front-end (you can run queries) and SQL exporting.DB Designer Fork generates SQL scripts for Oracle, SQL Server, MySQL, FireBird, SQLite and PostgreSQL.

==== ModelRight ====

http://www.modelright.com

ModelRight allows you to graphically view your database, enforce complex constraints, manage database views, validate design decisions, and generate complete CREATE and ALTER scripts.

Docs mention support for Windows 7 and PostgreSQL 9.0.

== Linux ==

=== Open Source / Free Software / Zero Cost ===

==== pgdesigner ====

http://pgdesigner.sourceforge.net/en/index.html

== Cross-Platform ==

=== Open Source / Free Software / Zero Cost ===

==== pgModeler ====

https://github.com/pgmodeler
https://www.pgmodeler.com.br

Windows / Linux / macOS

This is open source (GPLv3) and can be freely built yourself, if you have Qt available, but downloadable binaries appear to be time-limited demos that can be unlocked with paypal (?).

==== Open System Architect ====

http://www.codebydesign.com

Windows / macOS / Linux / Solaris

OSA currently supports data modelling (physical and logical) with UML in the works.

==== SQL Power Architect ====

http://software.sqlpower.ca/page/architect

Java

The SQL Power Architect data modeling tool was created by data warehouse designers and has many unique features geared specifically for the data warehouse architect. It allows users to reverse-engineer existing databases, perform data profiling on source databases, and auto-generate ETL metadata.

==== Valentina Studio ====

https://www.valentina-db.com/en/valentina-studio-overview

Windows / macOS / Linux

Free version supports reverse-engineering an existing schema, but only the proprietary version supports forward-engineering.

==== Open ModelSphere ====

http://www.modelsphere.com/org/

Java

Open ModelSphere is a powerful data, process and UML modeling tool - supporting user interfaces in English and French.

==== Umbrello ====

https://umbrello.kde.org

Windows / macOS / Linux

Umbrello UML Modeller is a Unified Modelling Language (UML) diagram program based on KDE Technology.

UML allows you to create diagrams of software and other systems in a standard format to document or design the structure of your programs.

==== ERDesignerNG ====

http://mogwai.sourceforge.net/erdesignerng.html

Java, GPL

=== Proprietary ===

==== DbSchema ====

http://www.dbschema.com

Windows / macOS / Linux / Java

Features interactive diagrams, relational data browse, schema compare and synchronization, query builder, query editor, HTML5 documentation, random data generator, forms and reports.

==== DbVisualizer ====

http://www.dbvis.com

Windows / macOS / Linux / Java

A client that does a lot of things other than schema design. It has a free version that provides many of the features, but not apparently design and DDL export.

==== DbWrench ====

http://www.dbwrench.com

Windows / macOS / Linux / Java

Diagramming / Forward & Reverse Engineering

==== StarUML ====

http://staruml.io

Windows / macOS / Ubuntu

https://github.com/adrianandrei-ca/staruml-postgresql - extension to support PostgreSQL

(This is version 2. The much older, open source version 1 is available at http://staruml.sourceforge.net/v1/download.php)

==== Vertabelo ====

http://www.vertabelo.com

Purely web-based, a monthly fee per user.

==== Navicat ====

https://www.navicat.com/en/products/navicat-for-postgresql

Windows, macOS, iOS

A general purpose client with good modeling features.

=== Obsolete or End-of-Life ===

==== Druid 3 ====

https://sourceforge.net/projects/druid/

Java

The druid is a tools that allows users to create databases in a graphical way. The user can add tables, fields, folders to group tables and can modify most of the database options that follow the SQL-92 standard. In addition to sql options, the user can document each table and each field with HTML information.

== Commandline Tools ==

Tools that take a description of a database schema in one format and convert it to SQL, and sometimes vice-versa.

=== dbmstools ===

https://github.com/charlesnagy/xml2ddl

Python, uses XML as the one true format and generates migration scripts from that.

=== SQLFairy ===

http://sqlfairy.sourceforge.net

Perl, manipulate structured data definitions (mostly database schemas) in interesting ways, such as converting among different dialects of CREATE syntax (e.g., MySQL-to-Oracle), visualizations of schemas (pseudo-ER diagrams: GraphViz or GD), automatic code generation (using Class::DBI), converting non-RDBMS files to SQL schemas (xSV text files, Excel spreadsheets), serializing parsed schemas (via Storable, YAML and XML), creating documentation (HTML and POD), and more.

== Other Resources ==

[[GUI Database Design Tools]] - older list that this page was started from