Online Documentation for Data Pump for PostgreSQL
Version history
Product name |
Version |
Release date |
Data Pump for PostgreSQL |
March 4, 2020 |
|
Data Pump for PostgreSQL |
March 10, 2016 |
|
Data Pump for PostgreSQL |
June 20, 2011 |
|
Data Pump 2009 for PostgreSQL |
February 17, 2009 |
|
Data Pump 2006 for PostgreSQL |
February 21, 2007 |
|
Data Pump 2006 for PostgreSQL |
June 26, 2006 |
- Implemented support for Azure, SQL Server 2017, MySQL Server 8 and PostgreSQL 12.
- The TRUNCATE statement is now used for deleting data from tables.
- MySQL. The 'MySQL has gone away' error has been fixed.
- PostgreSQL. Default values are now processed correctly.
- The total number of records for large tables is now displayed correctly.
- The error occured in case of using COPY statement for import. Fixed now.
- The error occured on loading the template with columns selection in the console version. Fixed now.
- Other fixes and improvements.
- Renewed installation program containing lots of fixes.
- Milliseconds support for the Datatime and Timestamp MySQL types.
- The 'Out of memory' error occured on transferring a large amount of data from InterBase. Fixed now.
- The script for the indices having the same name was generated incorrectly for SQL Server and MySQL. Fixed now.
- Incorrect constraints refreshing in MS SQL Server with ODBC has been fixed.
- The 'Out of memory' error occured transferring the data from DBF/FoxPro using Advantage OLE DB Provider 11. Fixed now.
- The 'Access Violation' error occured at Step 5 of the wizard in some cases while importing data from MySQL. Fixed now.
- There was an error while reconnecting to the source MySQL server. Fixed now.
- Lots of other improvements and bug-fixes.
- Added the possibility to transfer objects descriptions, if they are supported by provider.
- Added the option allowing to set sequence options after data importing.
- It is now possible to transfer views/queries data.
- Added the possibility to refresh the objects tree of source database.
- Now when importing data, foreign keys are disabled and recreated automatically.
- Support of the latest Server versions is implemented.
- Some other improvements and bugfixes.
- Implemented Unicode data support
- Source DBMS schemas support has been implemented
- Added an option allowing one to enable/disable refreshing of source objects on connection
- Added an option specifying whether all source tables are selected by default at Step 3
- Quoting identifiers for the source database can be customized at Step 4 now
- Pumping BLOB fields using ODBC drivers v5.1 for MySQL was not possible. Fixed now
- Latest versions of target PostgreSQL DBMS are supported
- Improved schema support for target database
- It is now possible to clear tables before importing data
- It is now possible to generate DROP TABLE statements
- Using OIDs for pumped objects is now optional
- The wizard window is now resizable
- The possibility to restart the wizard is added at the last step
- It is now possible to specify the wizard step that will be opened after loading a template
- It is now possible to start data import after loading a template
- Implemented password encryption in templates and registry
- A number of minor bug-fixes and visual improvements
- It is now possible to enforce quoting for object names in the result script for data import automatically (when applied to "unrecognized" OLE DB/ODBC providers)
- Implemented Private Key support for SSH authentication
- Added the ability to specify the default schema for tables import
- Added French and German interface localizations for the utility
- A number of minor bug-fixes and visual improvements
- Two types of template formats have been implemented: the fixed one which points to a certain list of objects to be transferred, and the dynamic one which defines only excluded objects; the objects out of this list are to be transferred. Template files of old format are still supported
- Added the opportunity to connect through the SSH or HTTP tunnel
- The 'Recreate database' option is implemented in the GUI version of the utility: the options allows you to delete the existing database before creating a new one (this option has been only in the console version until now)
- Now the console version returns the error code (0 - successful termination, 1 - critical error, 2 – non-critical error)
- Added an option allowing one to specify whether the COPY statement is to be used instead of the INSERT INTO statement for data import to increase the transfer speed considerably
Full version history is available at http://www.sqlmanager.net/products/postgresql/datapump/news
See also: |