Send processed data from Unstructured to PostgreSQL.

The requirements are as follows.

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.

  • 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:

  • 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.

To create or change a PostgreSQL destination connector, see the following examples.

Replace the preceding placeholders as follows:

  • <name> (required) - A unique name for this connector.
  • <host> (required) - The host name.
  • <database> (required) - The name of the database.
  • <port> (required) - The port number.
  • <username> (required) - The username.
  • <password> (required) - The user’s password.
  • <table-name> (required) - The name of the table in the database.
  • <batch-size> - The maximum number of rows to transmit at a time. The default is 100 if not otherwise specified.
  • <id-column> (required, source connector only) - The name of the ID column in the table.
  • For fields (source connector only), set one or more <field> values, with each value representing the name of a column to process (including the specified <id-column> column). The default is all columns if not otherwise specified.

To change a connector, replace <connector-id> with the source connector’s unique ID. To get this ID, see List source connectors.

Was this page helpful?

PineconeQdrant