From d1c461f529b9774c47056e71a232e06a1629cacd Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Wed, 23 Apr 2025 12:08:02 +0000 Subject: [PATCH] Add information about patching extension sources to README Co-Authored-By: alexeymasterov@neon.tech --- docker-compose/ext-src/README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docker-compose/ext-src/README.md b/docker-compose/ext-src/README.md index 088578640a..0364ce3c5d 100644 --- a/docker-compose/ext-src/README.md +++ b/docker-compose/ext-src/README.md @@ -83,3 +83,11 @@ To add a new extension for testing: - If neither exists, it will try to run `make installcheck` - `test-upgrade.sh` is only needed if you want to test upgrade scenarios 3. Update the list of extensions in the `test_extensions_upgrade.sh` script if needed for upgrade testing + +### Patching Extension Sources + +If you need to patch the extension sources: + +1. Place the patch file in the extension's directory +2. Apply the patch in the appropriate script (`test-upgrade.sh`, `neon-test.sh`, `regular-test.sh`, or `Makefile`) +3. The patch will be applied during the testing process