PostgreSQL

Batch process all your records to store structured outputs in a PostgreSQL schema.

Insert query is currently limited to append.

The requirements are as follows.

• For the Unstructured Platform, local PostgreSQL installations are not supported.
• For Unstructured Ingest, local and non-local PostgreSQL installations are supported.

The following video shows how to set up Amazon RDS for PostgreSQL:

The following video shows how to set up Azure Database for PostgreSQL:

• A PostgreSQL instance.

  • Create an Amazon RDS for PostgreSQL instance.
  • Create an Azure Database for PostgreSQL server.
  • Install PostgreSQL locally.

• The host name and port number for the instance.

  • For Amazon RDS for PostgreSQL, learn how to get the host name and port number.
  • For Azure Database for PostgreSQL, learn how to get the host. The port number is 5432.
  • For local PostgreSQL installations, these values are in the postgresql.conf file’s listen_addresses and port settings. This file should be on the same machine as the instance. These values might also already be set as environment variables named PGHOST and PGPORT on the same machine as the instance.
  • For other installation types, see your PostgreSQL provider’s documentation.

• Depending on your network security requirements, you might need to allow access to your instance only from specific IP addresses.

  To get Unstructured’s IP address ranges, go to https://assets.p6m.u10d.net/publicitems/ip-prefixes.json and allow all of the ip_prefix fields’ values that are listed.

  These IP address ranges are subject to change. You can always find the latest ones in the preceding file.

  To learn how to allow these IP address ranges, see your PostgreSQL provider’s documentation, for example with Amazon RDS for PostgreSQL or Azure Database for PostgreSQL.

• A database in the instance.

  • For Amazon RDS for PostgreSQL and Azure Database for PostgreSQL, the default database name is postgres unless a custom database name was specified during the instance creation process.
  • For local PostgreSQL installations, learn how to create a database.
  • For other installation types, see your PostgreSQL provider’s documentation.

• A table in the database. Learn how to create a table.

  The table’s schema must match the schema of the documents that Unstructured produces. Unstructured cannot provide a schema that is guaranteed to work in all circumstances. This is because these schemas will vary based on your source files’ types; how you want Unstructured to partition, chunk, and generate embeddings; any custom post-processing code that you run; and other factors.

  You can adapt the following table schema example for your own needs:

  See also:

  • CREATE TABLE for PostgreSQL
  • CREATE TABLE for PostrgreSQL with pgvector
  • Unstructured document elements and metadata

• A user in the database, and a password for the user.

  • For Amazon RDS for PostgreSQL, learn how to create a user.
  • For Azure Database for PostgreSQL, learn how to create a user.
  • For local PostgreSQL installations, learn how to create a user.
  • For other installation types, see your PostgreSQL provider’s documentation.

• Database access for the user.

  • For Amazon RDS for PostgreSQL, learn how to control user access.
  • For Azure Database for PostgreSQL, learn how to control user access.
  • For local PostgreSQL installations, learn how to give database access to a user.
  • For other installation types, see your PostgreSQL provider’s documentation.

The PostgreSQL connector dependencies:

pip install "unstructured-ingest[postgres]"

You might also need to install additional dependencies, depending on your needs. Learn more.

The following environment variables:

• PGHOST - The host name, represented by --host (CLI) or host (Python).
• PGPORT - The port number, represented by --port (CLI) or port (Python).
• PGUSER - The username, represented by --username (CLI) or username (Python).
• PGPASSWORD - The user’s password, represented by --password (CLI) or password (Python).
• PGDATABASE - The name of the database, represented by --database (CLI) or database (Python).

Now call the Unstructured Ingest CLI or the Unstructured Ingest Python library. The source connector can be any of the ones supported. This example uses the local source connector:

This example sends files to Unstructured API services for processing by default. To process files locally instead, see the instructions at the end of this page.

For the Unstructured Ingest CLI and the Unstructured Ingest Python library, you can use the --partition-by-api option (CLI) or partition_by_api (Python) parameter to specify where files are processed:

• To do local file processing, omit --partition-by-api (CLI) or partition_by_api (Python), or explicitly specify partition_by_api=False (Python).

  Local file processing does not use an Unstructured API key or API URL, so you can also omit the following, if they appear:

  • --api-key $UNSTRUCTURED_API_KEY (CLI) or api_key=os.getenv("UNSTRUCTURED_API_KEY") (Python)
  • --partition-endpoint $UNSTRUCTURED_API_URL (CLI) or partition_endpoint=os.getenv("UNSTRUCTURED_API_URL") (Python)
  • The environment variables UNSTRUCTURED_API_KEY and UNSTRUCTURED_API_URL

• To send files to Unstructured API services for processing, specify --partition-by-api (CLI) or partition_by_api=True (Python).

  Unstructured API services also requires an Unstructured API key and API URL, by adding the following:

  • --api-key $UNSTRUCTURED_API_KEY (CLI) or api_key=os.getenv("UNSTRUCTURED_API_KEY") (Python)
  • --partition-endpoint $UNSTRUCTURED_API_URL (CLI) or partition_endpoint=os.getenv("UNSTRUCTURED_API_URL") (Python)
  • The environment variables UNSTRUCTURED_API_KEY and UNSTRUCTURED_API_URL, representing your API key and API URL, respectively.

  Get an API key and API URL.