> ## Documentation Index
> Fetch the complete documentation index at: https://unstructured-53-docs-243-plugins.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# PostgreSQL
If you're new to Unstructured, read this note first.
Before you can create a source connector, you must first [sign up for Unstructured](https://platform.unstructured.io).
After you sign up, the [Unstructured user interface](/ui/overview) (UI) appears, which you use to create the source connector.
After you create the source connector, add it along with a
[destination connector](/ui/destinations/overview) to a [workflow](/ui/workflows). Then run the worklow as a
[job](/ui/jobs). To learn how, try out the [hands-on UI quickstart](/ui/quickstart) or watch the 4-minute
[video tutorial](https://www.youtube.com/watch?v=Wn2FfHT6H-o).
You can also create source connectors with the Unstructured API.
[Learn how](/api-reference/workflow/sources/overview).
If you need help, reach out to the [community](https://short.unstructured.io/pzw05l7) on Slack, or
[contact us](https://unstructured.io/contact) directly.
You are now ready to start creating a source connector! Keep reading to learn how.
Ingest your files into Unstructured from PostgreSQL.
The requirements are as follows.
* For the [Unstructured UI](/ui/overview) or the [Unstructured API](/api-reference/overview), local PostgreSQL installations are not supported.
* For [Unstructured Ingest](/ingestion/overview), local and non-local PostgreSQL installations are supported.
The following video shows how to set up [Amazon RDS for PostgreSQL](https://aws.amazon.com/rds/postgresql/):
The following video shows how to set up [Azure Database for PostgreSQL](https://azure.microsoft.com/products/postgresql):
* A PostgreSQL instance.
* [Create an Amazon RDS for PostgreSQL instance](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_GettingStarted.CreatingConnecting.PostgreSQL.html).
* [Create an Azure Database for PostgreSQL server](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-deploy-on-azure-free-account).
* [Install PostgreSQL locally](https://www.postgresql.org/docs/current/tutorial-install.html).
* The host name and port number for the instance.
* For Amazon RDS for PostgreSQL, learn how to [get the host name and port number](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ConnectToPostgreSQLInstance.html#postgresql-endpoint).
* For Azure Database for PostgreSQL, learn how to [get the host](https://learn.microsoft.com/azure/postgresql/flexible-server/quickstart-create-server#get-the-connection-information). 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](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](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.RDSSecurityGroups.html) or
[Azure Database for PostgreSQL](https://learn.microsoft.com/azure/postgresql/flexible-server/how-to-manage-firewall-portal#create-a-firewall-rule-after-server-is-created).
For Amazon RDS for PostgreSQL, Amazon recommends that you set the instance's **Public access** setting to **No** by default, as this
approach is more secure. This means that no
resources can connect to the instance outside of the instance's associated Virtual Private Cloud (VPC) without extra configuration.
[Learn more](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.Hiding).
[Access an Amazon RDS instance in a VPC](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.Scenarios.html).
If you must enable public access, set the instance's **Public access** setting to **Yes**, and then adjust the instance's related
security group to allow this access.
[Learn how](https://repost.aws/en/questions/QUxemKa9u5TV6CmLiO-r5prg/lost-public-access-to-aws-rds-postgresql-instance).
[Troubleshoot issues with connecting to Amazon RDS instances](https://repost.aws/knowledge-center/rds-connectivity-instance-subnet-vpc).
* 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](https://www.postgresql.org/docs/current/tutorial-createdb.html).
* For other installation types, see your PostgreSQL provider's documentation.
* A table in the database. Learn how to [create a table](https://www.postgresql.org/docs/current/tutorial-table.html).
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:
```sql PostgreSQL theme={null}
CREATE TABLE elements (
id UUID PRIMARY KEY,
record_id VARCHAR,
element_id VARCHAR,
text TEXT,
embeddings DECIMAL [],
parent_id VARCHAR,
page_number INTEGER,
is_continuation BOOLEAN,
orig_elements TEXT,
partitioner_type VARCHAR
);
```
```sql PostgreSQL with pgvector theme={null}
CREATE EXTENSION vector;
CREATE TABLE elements (
id UUID PRIMARY KEY,
record_id VARCHAR,
element_id VARCHAR,
text TEXT,
embeddings vector(3072),
parent_id VARCHAR,
page_number INTEGER,
is_continuation BOOLEAN,
orig_elements TEXT,
partitioner_type VARCHAR
);
```
See also:
* [CREATE TABLE](https://www.postgresql.org/docs/current/sql-createtable.html) for PostgreSQL
* [CREATE TABLE](https://github.com/pgvector/pgvector) for PostrgreSQL with pgvector
* [Unstructured document elements and metadata](/api-reference/partition/document-elements)
The following video shows how to use the `psql` utility to connect to PostgreSQL, list databases, and list and create tables:
* A user in the database, and a password for the user.
* For Amazon RDS for PostgreSQL, learn how to [create a user](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.PostgreSQL.CommonDBATasks.Roles.html).
* For Azure Database for PostgreSQL, learn how to [create a user](https://learn.microsoft.com/azure/postgresql/flexible-server/how-to-create-users).
* For local PostgreSQL installations, learn how to [create a user](https://www.postgresql.org/docs/current/sql-createuser.html).
* 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](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.PostgreSQL.CommonDBATasks.Access.html).
* For Azure Database for PostgreSQL, learn how to [control user access](https://www.postgresql.org/docs/current/sql-createuser.html).
* For local PostgreSQL installations, learn how to [give database access to a user](https://www.postgresql.org/docs/current/sql-grant.html).
* For other installation types, see your PostgreSQL provider's documentation.
To create the source connector:
1. On the sidebar, click **Connectors**.
2. Click **Sources**.
3. Cick **New** or **Create Connector**.
4. Give the connector some unique **Name**.
5. In the **Provider** area, click **PostgreSQL**.
6. Click **Continue**.
7. Follow the on-screen instructions to fill in the fields as described later on this page.
8. Click **Save and Test**.
Fill in the following fields:
* **Name** (*required*): A unique name for this connector.
* **Host** (*required*): The host name of the target PostgreSQL instance.
* **DB Name** (*required*): The name of the target database on the instance.
* **Port** (*required*): The port number on the instance.
* **Username** (*required*): The name of the target user with the appropriate access to the instance.
* **Password** (*required*): The password for the user.
* **Table Name** (*required*): The name of the target 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.
* **Columns** (*required*, source connector only): A comma separated list of column names to process (including the specified **ID Column** column). The default is all columns if not otherwise specified.