Qlik Stitch: Google Cloud SQL PostgreSQL Temporary File Size Exceeds “temp_file_limit”

[David_Apodaca]

This error occurs with the Google Cloud SQL PostgreSQL database integration and it displays as below in the extraction logs:

Fatal Error Occured - ERROR: temporary file size exceeds temp_file_limit 

Resolution

To resolve this issue, you need to increase the temp_file_limit parameter in your PostgreSQL configuration

Here are the steps to fix it:

1. Access your Google Cloud SQL instance settings.

2. Locate the database flags or parameters section.

3. Find the temp_file_limit flag and increase its value.

   • The value is specified in kilobytes (kB).

   • The default in PostgreSQL is -1, which means no limit. However, Cloud SQL may enforce a smaller custom value depending on your instance configuration.

4. If you’re unsure about the appropriate value, start by doubling the current limit and adjust as needed based on your workload. Increasing this limit allows larger queries to complete but may also increase storage usage, so monitor performance and disk space after making the change.

5. Save the changes.
   Updating database flags in Cloud SQL typically requires a restart of the instance for the new settings to take effect.

After modifying the temp_file_limit, restart your PostgreSQL instance (if required) and run an extraction in Stitch.

Cause 

The error message indicates that the temporary file size has exceeded the temp_file_limit in your Google Cloud SQL PostgreSQL database. This limit is set to control the maximum size of temporary files used during query execution.

Related Content

See Google’s documentation on configuring database flags here:
Configure database flags | cloud.google.com

Environment

Stitch