Free postgresql databases software for linux

guile-dbd-postgresql is a PostgreSQL database driver for guile-dbi.

guile-dbi is a database generic interface. The main lib provide a way to use dbds (data base drivers) which are linked at run-time (like perl dbi or php or...).

This provide a very flexible way to use guile scheme implementation for db works. Now, implemented main dbi interface lib, mysql and postgres plugins... In near future more drivers will be available (if someone ask for)

OpenLDAP-PostgreSQL Linux HOWTO is a HOWTO for implementing PostgreSQL as an SQL backend for OpenLDAP.

This HOWTO doesnt talk about OpenLDAP, PostgreSQL or iODBC in this document I suppose that you know all that, I just provide my personnal installation of these apps.

So in this new version I will try to give all installation and configuration requirement to have OpenLDAP running with a PostgreSQL backend and a complete live example to let you see how is the work that should be done on a medium directory.

This is what I have in production state in my company with a master Bekerley db backend replicated to a remote LDAP directory using PostgreSQL as backend.

Haskell Database Connectivity project provides an abstraction layer between Haskell programs and SQL relational databases. This lets you write database code once, in Haskell, and have it work with any number of backend SQL databases (MySQL, Oracle, PostgreSQL, ODBC-compliant databases, etc.)
HDBC is modeled loosely on Perls DBI interface http://search.cpan.org/~timb/DBI/DBI.pm, though it has also been influenced by Pythons DB-API v2, JDBC in Java, and HSQL in Haskell.
HDBC is a from-scratch effort. It is not a reimplementation of HSQL, though its purpose is the same.
Main features:
- Ability to use replacable parameters to let one query be executed multiple times (eliminates the need for an escape function)
- Ability to access returned rows by column number
- Ability to read data from the SQL server on-demand rather than reading the entire result set up front
- HUnit testsuite for each backend driver
- Well-defined standard API and easy backend driver implementation
- Lazy reading of the entire result set (think hGetContents, but for the results of SELECT) (see sFetchAllRows)
- Support for translation between Haskell and SQL types
- Support for querying database server properties
- Add-on package (hdbc-missingh) to integrate with MissingH, providing a database backend for AnyDBM.
- Support for querying metadata such as column names.
- Support for querying additional metadata (column types, etc.)

KPoGre is grafical client for PostgreSQL database system for KDE. KPoGre project uses libpqxx library.
Main features:
- Browsing through PostgreSQL system catalog
- Wizards for create, modify and drop database objects - users, groups, databases, tables
- Wizards for backup, restore, vacuum, analyze and another tasks
- Wizards for changing privileges
KPoGre is in beta stage. It means, that bugs and problems are possible. Dont hesitate to contact me with bug reports, ideas and feature requests. At this time I intensively work on finishing all possible wizards.
Enhancements:
- Implemented Disk usage tab in Database property window. Contain list of ordinary tables, TOAST tables and indexes in DB, sorted by disk space used.
- Implemented actions for Server menu: Reload configuration, Rotate log file
- Added button to Server Activity tab: Cancel query, that allow stop running query, selected in activity table.
- Added info about used disk space into property pages for: Tablespace, Database, Table, Index and its folders
*Note: All it above works with PostgreSQL 8.1 or newer
- Object names containing upper-case letter are now quoted.
- When user click on Datatable header, detailed column info is displayed.
- Tables folder now contain also TOAST tables. Ordinary tables has OID link to their TOAST table in properties.

turbosql makes it possible for developers to control PostgrSQL from NetBeans quickly and visually.

turbosql is a NetBeans(3.3, 3.4, 3.5, 3.6) module for managing Postgresql(7.2, 7.3, 7.4).

It supports the creation, modification, deletion, and browsing of databases and tables.

Yukatan data model project is the schema definition of the Yukatan webmail database.
The PostgreSQL database structures defined in this file can be used as a backend store of an email message handling application. The database should be created with the "UNICODE" encoding to properly support messages in different languages.
New data types
The special data types commonly used in the Yukatan data model have been made explicit by the introduction of seven new domains. The domains and the related COMMENT statements make field semantics more clear than before.
See the SQL schema file for more detailed documentation on these domains.
Explicitly named constraints
All the table constraints in the database are now explicitly named and documented. This change makes the database implementation more orthogonal and cleans up the documentation.
Renamed fields and tables
All the *address field names have been truncated to *addr, to make it visually clearer that they are always paired with the corresponding *name fields. The change also makes parts of the documentation less repetitive.
The referencesfield table has been renamed to referencefield to avoid the plural form in the table name. Also all the contained references* field names have been renamed to reference*.
Semantic changes
Quite a few changes have been made to the semantics of various fields. The unnecessarily tight constraints on sequence numbers have been replaced with clearer documentation, the format and encoding of most fields has been explicitly documented, and the previously allowed dual use of the enttext and enddata fields has been prohibited.
Dropped envelope data
The envelope data added in version 0.5 of the data model has for now been removed. The reason for the removal is that the envelope data is not an integral part of an email message, and I wanted to make the version 1.0 as clear as possible. The database now stores "email messages" - nothing less, nothing more. Envelope data can and probably will be reintroduced in an incremental version 1.x along with other extensions.
Enhancements:
- cleans up and documents the data model that has developed since version 0.1
- removal of the envelope data added in version 0.5
- enaming and redefinition of some of the fields and tables
- database structure has also been extensively documented