PostgreSQL management, administration and development GUI for macOS
Created with passion and love

Schema (namespace) database element has a simple management form. Using it is possible to change the name, comment and the owner of the schema.

Tablespace management form can be used for modifying the name, location, comment of the tablespace and in additional two parameters / options. The parameters are:

• seq_page_cost (floating point) - sets the planner's estimate of the cost of a disk page fetch that is part of a series of sequential fetches. The default is 1.0
• random_page_cost (floating point) - sets the planner's estimate of the cost of a non-sequentially-fetched disk page. The default is 4.0.

Language management form defines and registers new procedural language by associating the language name with handler function(s) that are responsible for executing functions written in the language. The form modifies existing languages too. Supported parameters are name, comment, call, inline and validator handlers. The TRUSTED option can be used when language must not grant access to data that the user would not otherwise have.

Table management form provides access to several basic table parameters like name, schema, comment, tablespace, fillfactor percentage, inheritance, system OID availability per row and the logged status of the table. In additional the management form interface is extended with information and tabs for the columns, indices, foreign keys, check, triggers and rules belonging to that table. Also the content of the table may be revised with the ability to perform modifications in the same way like in SQL Editor. Table specific actions may be found in Action Assistant.

Column management is provided via a modal window. In additional to the basic column parameters, there are several specific checkboxes which can be used to determine r set the belonging of the column to primary or unique key, or to a normal index. Supported is also the management of the datatype, collation for collatable datatypes, array dimension, size, precision and scale for NUMERIC datatype, number of statistics details, default value, comment and more.

All available index / key types may be modified using the index management form. It combines many basic and extended settings for primary key, unique key, exclusion, unique index and normal index. Available for modification are the following parameters:

• Name, table, tablespace and comment
• The type of the index
• Condition for partial index predicate (if the index type allows it)
• Access method specific parameters
• Management of the included columns or expressions as keys of the index
• Setting the index as default for CLUSTER operations

In foreign key management form are available settings, options and parameters, which provide easy and fast creation or modification of the key:

• Foreign key name and comment.
• On DELETE and UPDATE actions selection.
• Matching type definition.
• Deferrable and validated options.

Check constraint management is provided via a modal window. The available for modification parameters are: check name, NO INHERIT and VALIDATED options, comment and an expression producing a Boolean result which new or updated rows must satisfy for an insert or update operation to succeed.

Trigger management form provides access to many of PostgreSQL trigger settings, parameters and options. It also has support for constraint triggers with referenced table parameter. Changes may be performed for:

• Trigger name, table or view and comment.
• The boolean expression / condition that determines whether the trigger function will actually be executed.
• Constraint trigger option with referenced table FROM parameter support.
• Trigger BEFORE, AFTER and INSTEAD OF type option.
• For each ROW or STATEMENT.
• Firing mode and the ability to enable / disable trigger.
• INSERT, UPDATE, DELETE and TRUNCATE events support.
• Specific columns selection for UPDATE event.
• Trigger function selection and quoted string arguments specification.

All PostgreSQL rewrite object parameters are available for modification in the rule management form, including the ability to enable disable the rule itself.

• Rule name, table or view and comment.
• SQL conditional expression, returning BOOLEAN.
• INSERT, UPDATE, DELETE and SELECT events support.
• Firing mode specification.
• INSTEAD and ALSO execution methods.
• Rule action commands management.

View management form is extended with several additional tabs for columns, triggers and rules of the view. It also provides access to the content of the view. Supported parameters are:

• View schema (namespace), name and comment.
• Support for materialized views with management for tablespace and fillfactor percentage.
• CHECK OPTION for control of automatically updatable views behaviour.
• security_barrier (boolean) for row-level security.

Functions may be managed in every possible way, provided by PostgreSQL server. In additional there is arguments generator, ability to execute and more:

• Complete arguments management, including RETURN TABLE.
• Parallelisation and volatility setup.
• Run-time configuration parameters.
• Transformation data types.

Aggregate management form provided direct access to all settings and parameters of an aggregate function. Some of the supported features are:

• Complete arguments management support for both, normal and direct arguments.
• Parallelisation setup.
• Combine, serialise and deserialise functions.
• Normal, ordered-set and hypothetical-set aggregates.

Sequence management form provided direct access to internal counting variables and parameters of the generator. It also gives the ability to change all basic settings.

• Sequence schema (namespace), name and comment.
• Owning table and column.
• Start, increment, minimum, maximum and next value.
• CYCLE and CACHE sequence parameters.
• Ability to create temporary sequences.

Collation management form provides access to all parameters of an existing collation or defines a new one using the specified operating system locale settings, or by copying from another.

• Collation schema (namespace), name and comment.
• LC_COLLATE and LC_CTYPE settings support.
• Owner of the collation

The domain management form provides access to many parameters of an existing domain datatype, including the check constrains associated with it. Also using the form a new domain can be created. Supported parameters are:

• Domain schema (namespace), name, comment and default value.
• Datatype specific settings, including type, collation, size, precision and scale, array dimensions.
• Domain check constraints managements, including NOT NULL clause.

Enum datatype management form gives access to all parameters available. It may be used for modification of an existing enum or to create new one. It also supports label reordering by dropping and recreating the type.