> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/quickstarts-1/jobs/ingestion/cdc-sources/postgresql.md).

# PostgreSQL

{% hint style="info" %}
**Prerequisites**

Ensure you have a connection to your [PostgreSQL](/content/reference-1/sql-commands/connections/create-connection/postgresql.md) database and that it has been enabled for CDC. 

For more information, please read the guide to [Enable CDC on PostgreSQL](/content/how-to-guides-1/connectors/enable-cdc/postgresql.md). 
{% endhint %}

## Create a CDC job that reads from your database

You can create a job to ingest your data from PostgreSQL into a staging table in the data lake. 

**Jump to**

* [Ingest to the data lake](#ingest-to-the-data-lake)
* [Job options](#job-options)

### Ingest to the data lake

After completing the prerequisites, you can create your staging tables. The example below creates a table without defining columns or data types, as this will be inferred automatically by Upsolver, though you can define columns if required:

```sql
CREATE TABLE default_glue_catalog.upsolver_samples.orders_raw_data()
    PARTITIONED BY $event_date;
```

Upsolver recommends partitioning by the system column `$event_date` or another date column within the data in order to optimize your query performance.

Next, you can create an ingestion job as follows:

```sql
CREATE JOB load_orders_raw_data_from_postgres
      PUBLICATION_NAME = 'sample'
AS COPY FROM POSTGRES upsolver_postgres_samples 
INTO default_glue_catalog.upsolver_samples.orders_raw_data;
```

{% hint style="warning" %}
Note that multiple ingestion jobs can write to the same table, resulting in a final table that contains a `UNION ALL` of all data copied into that table. This means that any duplicate rows that are written are not removed and the columns list may expand if new columns are detected.

This may not be your intended behavior, so ensure you are writing to the correct table before running your job.
{% endhint %}

### Job options

The example above only uses a small subset of all job options available when reading from PostgreSQL. Depending on your use case, you may want to configure a different set of options.  

Transformations can be applied to your ingestion job to correct issues, exclude columns, or mask data before it lands in the target. Furthermore, you can use expectations to define data quality rules on your data stream and take appropriate action. 

## Alter a job that reads from PostgreSQL

Some job options are considered mutable, enabling you to run a SQL command to alter an existing ingestion job rather than create a new job. 

For example, take the job we created earlier:

```sql
CREATE JOB load_orders_raw_data_from_postgres
      PUBLICATION_NAME = 'sample'
AS COPY FROM POSTGRES upsolver_postgres_samples 
INTO default_glue_catalog.upsolver_samples.orders_raw_data;
```

If you want to keep the job as is, but only change the cluster that is running the job, execute the following command:

```sql
ALTER JOB load_orders_raw_data_from_postgres 
    SET COMPUTE_CLUSTER = my_new_cluster;
```

Note that some options such as `COMPRESSION` cannot be altered once the connection has been created.

## Drop a job that reads from PostgreSQL

If you no longer need a job, you can easily drop it using the following SQL command: 

```sql
DROP JOB load_orders_raw_data_from_postgres;
```

***

{% hint style="success" %}
**Learn More**

Please see the SQL command reference for [PostgreSQL](/content/reference-1/sql-commands/jobs/create-job/ingestion/postgresql.md) for full details of the available job options and further examples.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://upsolver.gitbook.io/content/quickstarts-1/jobs/ingestion/cdc-sources/postgresql.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.