In Alibaba Cloud, you can use oss_fdw plugin to load data on OSS to PostgreSQL and PPAS databases, and you can also write data in a database to OSS.

oss_fdw parameters

Similar to other fdw interfaces, oss_fdw can encapsulate data stored on OSS (external data sources), allowing you to read files on OSS. The process is like reading data from a table. oss_fdw provides unique parameters used for connecting to and parsing file data on OSS.

  • Currently, oss_fdw can read and write the following file types in OSS: text/csv files and text/csv files in GZIP format.
  • The value of each parameter needs to be quoted and cannot contain any useless spaces.

CREATE SERVER parameters

  • ossendpoint: Address (host) used to access OSS from the intranet
  • id: OSS account ID
  • key: OSS account key
  • bucket: OSS bucket, assigned after an OSS account is created

The following parameters are related to error tolerance in import and export modes. If network connectivity is poor, you can adjust these parameters to facilitate successful imports and exports.

  • oss_connect_timeout: Connection expiration time, measured in seconds. Default value: 10s.
  • oss_dns_cache_timeout: DNS expiration time, measured in seconds. Default value: 60s.
  • oss_speed_limit: Minimum tolerable rate. Default value: 1,024 byte/s (1 Kbit/s).
  • oss_speed_time: Maximum tolerable time. Default value: 15s.

If the default parameter values are used, a timeout error occurs when the transmission rate is smaller than 1 Kbit/s for 15 consecutive seconds.


  • filepath: File name including a path on OSS.

    • A file name contains a path but not a bucket name.
    • This parameter matches multiple files in the corresponding path on OSS, and supports file loading to a database.
    • Files named in the format of filepath or filepath.x can be imported to a database. x in filepath.x must start from 1 and be consecutive, for example, filepath, filepath.1, filepath.2, filepath.3, and filepath.5.

      The first four files are matched and imported, but the file named filepath.5 is not.

  • dir: Virtual directory on OSS.

    • dir must end with a slash (/).
    • All files (excluding subfolders and files in subfolders) in the virtual directory indicated by dir are matched and imported to a database.
  • prefix: Prefix of the path in the data file. Regular expressions are not supported. You can set only one of the these parameters: prefix, filepath, and dir.
  • format: File format, which can only be CSV currently.
  • encoding: File data encoding format. It supports common PostgreSQL encoding formats, such as UTF-8.
  • parse_errors: Parsing in error tolerance mode. The errors that occur during the file parsing process are ignored by row.
  • delimiter: Delimiter specified for columns.
  • quote: Quote character for a specified file.
  • escape: Escape character for a specified file.
  • null: Used to nullify the column matching a specified string. For example, null 'test' is used to set the column whose value is 'test' to null.
  • force_not_null: Used to un-nullify the value of one or more columns. For example, force_not_null 'id' is used to set the values of the 'id' column to empty strings.
  • compressiontype: Used to set whether the file read or written on OSS is compressed and set the compression format. Value range:
    • none: Uncompressed (default value)
    • gzip: compressed gzip file
  • compressionlevel: Used to set the compression level of the compression format written to OSS, ranging from 1 to 9. The default value is 6.
  • filepath and dir need to be specified in the OPTIONS parameter.
  • Either filepath and dir must be specified, and they cannot be specified at the same time.
  • The export mode currently only supports virtual folders, that is, only dir is supported.

Export mode parameters for CREATE FOREIGN TABLE

oss_flush_block_size and oss_file_max_size are added for the export mode.

  • oss_flush_block_size: Buffer size for the data written to OSS at a time. Its default value is 32 MB, and the value range is 1 MB to 128 MB.
  • oss_file_max_size: Maximum file size for the data written to OSS (subsequent data is written in another file when the maximum file size is exceeded). Its default value is 1,024 MB, and the value range is 8 MB to 4,000 MB.
  • num_parallel_worker: The number of parallel compression threads in the compression mode in which the OSS data is written, ranging from 1 to 8. Its default value is 3.
Note oss_flush_block_size and oss_flush_block_size are invalid for the import mode.

Auxiliary function

FUNCTION oss_fdw_list_file (relname text, schema text DEFAULT 'public')

  • Used to obtain the name and size of the OSS file that an external table matches.
  • The unit of file size is byte.
select * from oss_fdw_list_file('t_oss');
              name | size    

 oss_test/test.gz. 1 | 739698350
 oss_test/test.gz. 2 | 739413041
 oss_test/test.gz. 3 | 739562048
(3 rows)

Auxiliary feature

oss_fdw.rds_read_one_file: In read mode, it is used to specify a file that matches the external table. Once it is set, the external table matches only one file that is set during data import.

For example, set oss_fdw.rds_read_one_file = ‘oss_test/example16.csv. 1’;

set oss_fdw.rds_read_one_file = 'oss_test/test.gz. 2';
select * from oss_fdw_list_file('t_oss');
              name | size    

  oss_test/test.gz. 2 | 739413041
(1 rows)

oss_fdw example

# (PostgreSQL) Create the plugin
create extension oss_fdw;  ----For PPAS, run: select rds_manage_extension('create','oss_fdw');
# Create a server instance  
     (host '' , id 'xxx', key 'xxx',bucket 'mybucket');
# Create an OSS external table
    (date text, time text, open float,
     high float, low float, volume int) 
     SERVER ossserver 
     OPTIONS ( filepath 'osstest/example.csv', delimiter ',' ,
         format 'csv', encoding 'utf8', PARSE_ERRORS '100');
# Create a table, to which data is loaded
create table example
        (date text, time text, open float,
         high float, low float, volume int);
# Load data from ossexample to example.
insert into example select * from ossexample;
# As you can see
# oss_fdw estimates the file size on OSS and formulates a query plan correctly.
explain insert into example select * from ossexample;
                             QUERY PLAN                              

 Insert on example (cost=0.00.. 1.60 rows=6 width=92)
   -> Foreign Scan on ossexample (cost=0.00.. 1.60 rows=6 width=92)
         Foreign OssFile: osstest/example.csv. 0
         Foreign OssFile Size: 728
(4 rows)
# Write the data in the example table to OSS.
insert into ossexample select * from example;
explain insert into ossexample select * from example;
                           QUERY PLAN

 Insert on ossexample  (cost=0.00..16.60 rows=660 width=92)
   ->  Seq Scan on example  (cost=0.00..16.60 rows=660 width=92)
(2 rows)

oss_fdw usage tips

  • oss_fdw is an external table plugin developed based on the PostgreSQL FOREIGN TABLE framework.
  • The data import performance is related to the PostgreSQL cluster resources (CPU I/O MEM MET) and OSS.
  • For expected data import performance, ossendpoint in ossprotocol must match the region where PostgreSQL is located in Alibaba Cloud. For more information, see the reference links at the end of this document.
  • If the error "oss endpoint userendpoint not in aliyun white list" is triggered during reading of SQL statements for external tables, use these endpoints. If the problem persists, submit a trouble ticket.

Error handling

When an import or export error occurs, the error log contains the following information:

  • code: HTTP status code of the erroneous request.
  • error_code: Error code returned by OSS.
  • error_msg: Error message provided by OSS.
  • req_id: UUID that identifies the request. If you cannot solve the problem, you can seek help from OSS development engineers by providing the req_id.

For more information about error types, see the reference links at the end of this document. Timeout errors can be handled using oss_ext parameters.

Hide ID and key

If ID and key parameters for CREATE SERVER are not encrypted, plaintext information is displayed using select * from pg_foreign_server, making the ID and key exposed. The symmetric encryption can be performed to hide the ID and key (use different keys of different instances for further protection of your information). However, to avoid incompatibility with old instances, you cannot use methods similar to GP to add a data type.

Encrypted information:

postgres=# select * from pg_foreign_server ;
  srvname  | srvowner | srvfdw | srvtype | srvversion | srvacl |                                                                              srvoptions

 ossserver |       10 |  16390 |         |            |        | {,id=MD5xxxxxxxx,key=MD5xxxxxxxx,bucket=067862}

The encrypted information is preceded by MD5 (total length: len%8==3). Therefore, encryption is not performed again when the exported data is imported. But you cannot create the key and ID preceded by MD5.