PG: fix ogr2ogr scenarios to PostgreSQL when there are several input …

[rouault]

…layer names like schema_name.layer_name (3.9.0 regression)

Fixes #10311

[rouault]

The backport to release/3.9 failed:

The process '/usr/bin/git' failed with exit code 1

stderr

error: could not apply 01d25df6f1... PG: fix ogr2ogr scenarios to PostgreSQL when there are several input layer names like schema_name.layer_name (3.9.0 regression)
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config advice.mergeConflict false"

stdout

Auto-merging autotest/ogr/ogr_pg.py
CONFLICT (content): Merge conflict in autotest/ogr/ogr_pg.py
Auto-merging ogr/ogrsf_frmts/pg/ogrpgdatasource.cpp

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release/3.9 release/3.9
# Navigate to the new working tree
cd .worktrees/backport-release/3.9
# Create a new branch
git switch --create backport-10327-to-release/3.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 01d25df6f1cae57a6b83c1bd88e63e78a239730a
# Push it to GitHub
git push --set-upstream origin backport-10327-to-release/3.9
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/3.9

Then, create a pull request where the base branch is release/3.9 and the compare/head branch is backport-10327-to-release/3.9.

[rouault]

backported in #10371