PostgreSQL Server

Changes in this release: 1) Updated to v9.3.17 source 2) Updated to libc066 3) minimal testing - pg_ctl doesn't seem to work 4) Rebuilt with latest pthreads and libcx from rpm 5) Updated to v9.4.15 source 5) Updated to v9.5.10 source 6) Updated to v9.6.6 source Known Issues: - running the postgresql initialisation sometimes crashes at "running bootstrap script"

PostgreSQL v8.4.3a is a powerful, enterprise class, open source relational database system. Fully ACID compliant. Requires libc063.dll.

PostgresSQL JDBC Support. USING THE DRIVER To use the driver, you must introduce it to JDBC. Again, there's two ways of doing this: 1: Hardcoded. This method hardcodes your driver into your application/applet. You introduce the driver using the following snippet of code: try { Class.forName("org.postgresql.Driver"); } catch(Exception e) { // your error handling code goes here } Remember, this method restricts your code to just the postgresql database. However, this is how most people load the driver. 2: Parameters This method specifies the driver from the command line. When running the application, you specify the driver using the option: -Djdbc.drivers=org.postgresql.Driver eg: This is an example of running one of my other projects with the driver: java -Djdbc.drivers=org.postgresql.Driver uk.org.retep.finder.Main note: This method only works with Applications (not for Applets). However, the application is not tied to one driver, so if you needed to switch databases (why I don't know ;-) ), you don't need to recompile the application (as long as you havent hardcoded the url's). --------------------------------------------------------------------------- JDBC URL syntax The driver recognises JDBC URL's of the form: jdbc:postgresql:database jdbc:postgresql://host/database jdbc:postgresql://host:port/database Also, you can supply both username and passwords as arguments, by appending them to the URL. eg: jdbc:postgresql:database?user=me jdbc:postgresql:database?user=me&password=mypass --------------------------------------------------------------------------- That's the basics related to this driver. You'll need to read the JDBC Docs on how to use it. However, there are some examples included in the example directory. To build, type: make examples To run them, they follow the same syntax. For example, the basic example shows how to insert data, and perform queries: java example.basic jdbc:postgresql:test user password --------------------------------------------------------------------------- POSTGRESQL SPECIFICS -------------------- Large Objects: A "feature" of PostgreSQL is that access to LargeObjects is only permitted within a Transaction. Because of this, any use of LargeObjects (also known as Blobs) requires that the Connection.setAutoCommit() method be called disabling the autocommit feature. For example: Connection db; // open the connection here db.setAutoCommit(false); // Turn off AutoCommit ------------------ Large Object API Most of the time, you can use the getBytes()/setBytes() methods to read and write small Large Objects. However, PostgreSQL's own internal api's are available. These allow you to access the object as if it was a file. The first thing you need to do is to open the LargeObjectManager. This class handles the opening of existing objects, and creating new ones. To do this, you use the following line of code: LargeObjectManager lobj; lobj = ((org.postgresql.Connection)db).getLargeObjectAPI(); where db is a reference to an open Connection object. Once that is done, you can use the API for the lifetime of that Connection. To create an object, you call the create() method. This takes an argument with the file modes you intend to use. The following line is normally sufficient: int oid = lobj.create(LargeObjectManager.READ|LargeObjectManager.WRITE); Here, lobj is the LargeObjectManager we have opened earlier, and oid is the Large Object's oid in the database. To open an existing object, you use the open() method. This takes an oid, and the file permissions. It then returns a LargeObject object. LargeObject obj = lobj.open(oid,LargeObjectManager.WRITE); Once the LargeObject is open, you can call methods to read, write, seek etc. Here's the supported methods: int oid = obj.getOID(); Return the objects oid obj.close(); Close the object byte data[] = obj.read(int len); Read len bytes onj.read(byte data[],int off,int len); Read into data[off] len bytes obj.write(byte data[]); Write the array data obj.write(byte data[],int off,int len); Write len bytes from data[off] obj.seek(int pos,int ref); As fseek in C. obj.seek(int pos); Move to pos (from the begining) int pos = obj.tell(); Returns the current position int size = obj.size(); Returns the objects size Caveat: If you commit(), rollback() a transaction, or turn on autocommit whilst an object is open PostgreSQL will close it. You will need to reopen the object before using it again. Using the existing LargeObject will cause an SQLException to be thrown. ------------------ Date datatype: The driver now issues the "show datestyle;" query when it first connects, so any call to ResultSet.getDate() how returns the correct date. One caveat though: if you change the datestyle from within JDBC, you must also issue the "show datestyle" query. Without this, the driver will not know of the change. ie: Statement s = db.createStatement(); ... s.executeUpdate("set datestyle='european'"); s.executeUpdate("show datestyle"); .. s.close(); Please note: This may change later, so that the driver uses the same format internally (similar to how the ODBC driver works). ------------------ JDBC supports database specific data types using the getObject() call. The following types have their own Java equivalents supplied by the driver: box, circle, line, lseg, path, point, polygon When using the getObject() method on a resultset, it returns a PG_Object, which holds the postgres type, and its value. This object also supports methods to retrive these types. Eg: column 3 contains a point, and rs is the ResultSet: PG_Object o = (PG_Object)rs.getObject(3); PGpoint p = o.getPoint(); System.out.println("point returned x="+p.x+", y="+p.y); Also, when using these classes, their toString() methods return the correct syntax for writing these to the database. --------------------------------------------------------------------------- Peter T Mount, December 29 1998 home email: pmount at retep.org.uk http://www.retep.org.uk work email: petermount at it.maidstone.gov.uk or peter at taer.maidstone.gov.uk PS: Please use the home email whenever possible. If you must contact me at work then please cc my home one at the same time.

EMX -Zmt build of PostgreSQL libpq client library w/SSL. Requires EMX 0.9d runtime. Replaces libpq-7.4.5-emx.zip.

postgreSQL V8.0 source for os/2 port. Requires Warp 4.5, Compiler and a bunch of other things.

PostgreSQL v8.0 GA (FIX E) OS/2 port. The compiler used is GCC 3.3.5 beta4. It is built from the 2004-12-03 rc1 code. This program uses high memory for allocating buffers. Requires Warp 4.5. Replaces postgresqlL-8.0-os2d.zip.

PostgreSQL V8.0 GA fix c release os/2 port. The compiler used is GCC 3.3.5 beta4. It is built from the 2004-12-03 rc1 code. This program uses high memory for allocating buffers. Requires Warp 4.5. Replaces postgresqlL-8.0-os2b.zip.

PostgreSQL V8.0 GA fix a release os/2 port. The compiler used is GCC 3.3.5 beta2. It is built from the 2004-12-03 rc1 code. This program uses high memory for allocating buffers. Requires Warp 4.5. Replaces postgresqlL-8.0-os2.zip.

PostgreSQL V8.0 release candidate 5 os/2 port. The compiler used is GCC 3.3.5 beta2. It is built from the 2004-12-03 rc1 code. This program uses high memory for allocating buffers. Requires Warp 4.5, a processor that supports the FXSAVE instruction (fork() code uses it). Replaces postgreSQL-8.0-rc4.zip.

PostgreSQL V8.0 release candidate 3 os/2 port. The compiler used is GCC 3.3.5 beta2. It is built from the 2004-12-03 rc1 code. This program uses high memory for allocating buffers. Requires Warp 4.5, a processor that supports the FXSAVE instruction (fork() code uses it.

PostgreSQL V8.0 rc2d os/2 port. The compiler used is GCC 3.3.5 beta2. It is built from the 2004-12-03 rc1 code. This program uses high memory for allocating buffers. Requires Warp 4.5, 14.100 kernel and TCP/IP 4.1 or better and probably a non k6-2 CPU (possible failure). Replaces postgreSQL-8.0-rc2.zip postgreSQL-8.0-rc2a.zip postgresSQL-8.0-rc2C.zip.

PostgreSQL v8.0 rc2a OS/2 port update. The compiler used is GCC 3.3.5 beta2. It is built from the 2004-12-03 rc1 code. This program uses high memory for allocating buffers. Requires Warp 4.5. 14.100 kernel and TCP/IP 4.1 or better and probably a non k6-2 CPU (possible failure). Replaces postgreSQL-8.0-rc2.zip.

Upgrade release. A sophisticated Object-Relational DBMS, supporting almost all SQL constructs, including subselects, transactions, and user-defined types and functions. It is the most advanced open-source database available anywhere.Includes new PM console for logging, also includes xbase tools and PDF documentation V7.3.2.

ODBC driver + manager 3.01 for OS/2 includes drivers (postgres,db2,btrive,text,dbf,etc.), fully functional with emx and non emx apps. ODBC by ex Intersolv 3.01 - READ.ME ------------------------ Welcome to ODBC by ex Intersolv. This file contains information you need to install ODBC by ex Intersolv and additional information not included in the product documentation. This README file is divided into the following categories: - Before You Install ODBC by ex Intersolv -Software Requirements -Hardware Requirements - Getting Help - Installing ODBC by ex Intersolv - Late-Breaking News - Trademarks - Your Satisfaction Before You Install ODBC by ex Intersolv --------------------------------- Software Requirements --------------------- OS/2 WARP 3.0/4.0 Hardware Requirements --------------------- 486 processor or Pentium 1MB RAM 6MB DASD Getting Help ------------ Documentation Service and Technical Support Defect Reporting Installing ODBC by ex Intersolv ------------------------- Remove the previous ODBC installation. You must remove all ODBC files !!! Remove also the \os2\odbc.ini and \os2\odbcinst.ini, if present. Then execute ODBC Manager for driver setup. Late-Breaking News ------------------ The latest source version of this software may be obtained at ??? For more information look at our WWW home page located at http://venuto.monrif.net. Your Satisfaction ----------------- Your satisfaction with me is important to us. If you are not totally satisfied with this product, please contact us at venuto@monrif.net. Tell us what is not meeting your expectations and why you are dissatisfied. Provide your name, your organizations's name, and your telephone number so that we can contact you. We will work with you to resolve your concerns. To contact us, use any of these: o Telephone in the Italy: +39-335-6059667 o Fax in the Italy: +39-828-397244 o Internet: venuto@monrif.net