PostgreSQL 9.4 Adapter Limitations

• Supported Types
• Read Table
• Execute Select SQL
• Write table
• Execute Update SQL
• Main exceptions

Supported Types

• Yes: Support.
• Limited: Support with limitations.
• No: Not supported.

Read Table

Specification Limits

• CHARACTER VARYING, CHARACTER, TEXT
  • The maximum value is 10,485,760.
• BYTEA
  • Backslash (\) and apostrophes (') is not supported.
• If the table name is enclosed by quotation marks, the table names are case-sensitive.


• Default value of [Fetch size] is "500".

Execute Select SQL

Specification Limits

• CHARACTER VARYING, CHARACTER, TEXT
  • The maximum value is 10,485,760.
• BYTEA
  • Backslash (\) and apostrophes (') is not supported.
• Default value of [Fetch size] is "500".

Write table

Specification Limits

• The following types are not supported.
  
  • BOX
  • CIDR
  • CIRCLE
  • INTERVAL
  • LSE
  • PATH
  • POINT
  • POLYGON
  • BIT VARYING
  • BIT VARYING(N)
  • ARRAY
  • INET
  • MACADDR
• CHARACTER VARYING, CHARACTER, TEXT
  • The maximum value is 10,485,760.
• BYTEA
  • Backslash (\) and apostrophes (') is not supported.
• If the table name is enclosed by quotation marks, the table names are case-sensitive.


• You can't select [Insert before update] at [Update mode]

Execute Update SQL

Specification Limits

• The following types are not supported.
  
  • BOX
  • CIDR
  • CIRCLE
  • INTERVAL
  • LSE
  • PATH
  • POINT
  • POLYGON
  • BIT VARYING
  • BIT VARYING(N)
  • ARRAY
  • INET
  • MACADDR
• CHARACTER VARYING, CHARACTER, TEXT
  • The maximum value is 10,485,760.
• BYTEA
  • Backslash (\) and apostrophes (') is not supported.

Main exceptions

Exception name		Cause	Actions
java.sql.SQLException	Batch entry 0 insert into "<table name>" ("<column names>") values ( <column values>) was aborted. Call getNextException to see the cause.	Specified table name is illeagal, or specified table does not exist.	Make sure the specified table name is valid.
org.postgresql.util.PSQLException	Connection to "<host name>:<port number>" refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.	Cannot connect to the database.	Check the [Port number].
	FATAL: database "<database name>" does not exist.	Specified database does not exist.	Make sure the specified database exists.
	FATAL: password authentication failed for user "<user name>"	Incorrect user name or password.	Check the [User name] and [Password].
	ERROR: syntax error at or near "<table name>"	Specified table name is illegal.	Make sure the specified table name is valid.
	ERROR: relation "<table name>" does not exist	Specified table does not exist.	Make sure the specified table exists.
	ERROR: permission denied for relation <table name>	User has no permission to perform the operation on the specified table.	Check the owner and permissions of the specified table.
	The server does not support SSL.	PostgreSQL server dose not support SSL connections.	Ensure the settings are correct. See PostgreSQL SSL settings for any details.
	The connection attempt failed.	Cannot connect to the database.	Check the [Hostname].
	SSL error: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target	Service certificate has not been imported into the keystore DataSpiderServer references.	Import the certificate into the keystore that DataSpiderServer references. For details, see Certificate Installation.
	FATAL: no pg_hba.conf entry for host "<host name>", user "<username>", database "<database name>", SSL off	Appropriate authentication information for Non-SSL connections to the PostgreSQL server does not exist.	Ensure that settings of the Global Resource specified in the [Destination] or of the PostgreSQL server are correct.
	FATAL: no pg_hba.conf entry for host "<host name>", user "<username>", database "<database name>", SSL on	Appropriate authentication information for SSL connections to the PostgreSQL server does not exist.	Ensure that settings of the Global Resource specified in the [Destination] or of the PostgreSQL server are correct.