如何修复AWS Elastic Beanstalk部署Django项目时的PostgreSQL版本错误？

Hey there, let's fix that PostgreSQL version mismatch issue on AWS Elastic Beanstalk (EB) for your Django project. I've run into similar problems before, so here's a step-by-step breakdown of the most common fixes:

1. First, confirm Django-PostgreSQL compatibility #

First things first: make sure your Django version supports the PostgreSQL version you're trying to use. For example:

• Django 4.2 works with PostgreSQL 10–16
• Django 3.2 supports PostgreSQL 9.6–14
• Django 2.2 works with PostgreSQL 9.5–12

Check your requirements.txt for your Django version, then cross-reference it with the official Django docs to get the valid PG version range.

2. Adjust EB's built-in PostgreSQL version (if using EB-managed RDS) #

If your EB environment uses a managed PostgreSQL RDS instance, you can override the default version with an EB config file:

• Create an .ebextensions folder in your project root if it doesn't exist
• Inside it, make a file named postgres_version.config with this content:

option_settings:
  aws:rds:dbinstance:
    DBEngineVersion: 14  # Replace with your compatible version (e.g., 12, 15)

• Deploy the changes with eb deploy

3. Update your Docker PostgreSQL image (if using Docker deployment) #

Since you're using Docker, the most likely culprit is a mismatched PG version in your Docker setup:

• Open your Dockerfile or docker-compose.yml
• If you're pulling a PostgreSQL base image, update the tag to match your compatible version. For example, change FROM postgres:11 to FROM postgres:14
• Double-check your Django settings.py database config to ensure there are no hardcoded version-specific options that might cause conflicts:

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.postgresql',
        'NAME': os.environ.get('DB_NAME'),
        'USER': os.environ.get('DB_USER'),
        'PASSWORD': os.environ.get('DB_PASSWORD'),
        'HOST': os.environ.get('DB_HOST'),
        'PORT': os.environ.get('DB_PORT'),
        # Avoid version-specific options unless absolutely necessary
    }
}

4. Fix your psycopg2 version (the PostgreSQL driver for Django) #

Psycopg2 needs to be compatible with both your Django and PostgreSQL versions. Update your requirements.txt to specify a compatible version:

psycopg2-binary>=2.9.0  # Works with PG 10–16 and most modern Django versions

Using psycopg2-binary is recommended for deployment since it avoids compilation issues on EB.

5. Test locally first to avoid deployment headaches #

Before pushing to EB, verify your setup works locally with the correct PG version:

• Use Docker Compose to spin up a PostgreSQL container matching your target version
• Run python manage.py migrate and test your app to ensure no version-related errors pop up
• Once local tests pass, deploy to EB again with eb deploy

If you're still stuck, pull the EB logs with eb logs to get the exact error message—this will help pinpoint if it's a driver issue, database connection problem, or something else.

内容的提问来源于stack exchange，提问作者Nouveau