PostgreSQL 11 Adapter Limitations

• Supported Types
• Read Table
• Execute Select SQL
• Write Table
• Execute Update SQL
• Major Exceptions

Supported Types

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

Read Table

Specification Limits

• CHARACTER VARYING, CHARACTER, TEXT
  • The maximum value is 10,485,760.
• BYTEA
  • Backslash (“\”) and apostrophe (“'”) are not supported.
• When the table name is enclosed with quotation marks, it is 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 apostrophe (“'”) are not supported.
• Default value of [Fetch size] is 500.

Write Table

Specification Limits

• The following types are not supported.
  
  • CIDR
  • CIRCLE
  • INTERVAL
  • LSEG
  • 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 apostrophe (“'”) are not supported.
• When the table name is enclosed with quotation marks, it is case-sensitive.


• [Insert before update] of [Update mode] cannot be used.

Execute Update SQL

Specification Limits

• The following types are not supported.
  
  • CIDR
  • CIRCLE
  • INTERVAL
  • LSEG
  • 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 apostrophe (“'”) are not supported.

Major Exceptions

Exception name		Cause	Solution
java.sql.SQLException	Batch entry 0 insert into "<table name>" ("<column names>") values ( <column values>) was aborted: <error message> Call getNextException to see other errors in the batch.	The table name is invalid or the table does not exist.	Check the table name specified in [Table name].
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.	Unable to connect to the database.	Check [Port number] of the global resource.
	FATAL: database "<database name>" does not exist	The database is not found.	Specify an existing database in [Database name] of global resource.
	FATAL: password authentication failed for user "<user name>"	The user name or the password is incorrect.	Check [User name] and [Password] of the global resource.
	ERROR: syntax error at or near "<table name>"	The table name is invalid.	Check the table name specified in [Table name].
	ERROR: relation "<table name>" does not exist	The table does not exist.	Specify an existing table in [Table name].
	ERROR: permission denied for table <table name>	The user has no permission to read the table.	Check the read permission for the table specified in [Table name].
	The server does not support SSL.	The PostgreSQL server does not support SSL connection.	Check the PostgreSQL server settings.
	The connection attempt failed.	Cannot connect to the database server.	Check [Host name] of the global resource.
	SSL error: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target	The certificate is not imported to the keystore referred by DataSpiderServer.	Import a certificate to the keystore referred by DataSpiderServer. For more details on how to import a certificate, refer to “Import Certificate”.
	FATAL: no pg_hba.conf entry for host "<host name>", user "<user name>", database "<database name>", SSL off	Client certificate for standard (non-SSL) connection to PostgreSQL server is not found.	Check the settings of the global resource specified in [Destination], or the settings of PostgreSQL server.
	FATAL: no pg_hba.conf entry for host "<host name>", user "<user name>", database "<database name>", SSL on	Client certificate for SSL connection to PostgreSQL server is not found.	Check the settings of the global resource specified in [Destination], or the settings of PostgreSQL server.