There are only two client interfaces included in the base PostgreSQL distribution:
libpq is included because it is the primary C language interface, and because many other client interfaces are built on top of it.
ecpg is included because it depends on the server-side SQL grammar, and is therefore sensitive to changes in PostgreSQL itself.
All other language interfaces are external projects and are distributed separately. Table G-1 includes a list of some of these projects. Note that some of these packages might not be released under the same license as PostgreSQL. For more information on each language interface, including licensing terms, refer to its website and documentation.
Table G-1. Externally Maintained Client Interfaces
|DBD::Pg||Perl||Perl DBI driver||http://search.cpan.org/dist/DBD-Pg/|
|JDBC||JDBC||Type 4 JDBC driver||http://jdbc.postgresql.org/|
|libpqxx||C++||New-style C++ interface||http://pqxx.org/|
|Npgsql||.NET||.NET data provider||http://npgsql.projects.postgresql.org/|
|psycopg||Python||DB API 2.0-compliant||http://initd.org/psycopg/|
For OCaml, you essentially have two bindings. One called postgresql-ocaml, which is a direct binding of the libpq C library. The other, PG'OCaml, is rather peculiar in the sense that the typing in the PostgreSQL database is imported to the OCaml type system when compiling your linked code. It is a bit less flexible, but it has the advantage of enforcing the typing consistency between your program and the database. That will prevent any runtime errors if the database schema changes.