Do not ignore column-restricted INSERT privileges

[strk]

See GH-28835

[strk]

NOTE: based on PR GH-57802

[github-actions]

🪟 Windows builds ready!

Windows builds of this PR are available for testing here. Debug symbols for this build are available here.

(Built from commit a244a19)

[strk]

This is now ready for review and has unit test.
Writing the test revealed another bug (GH-57871) but fix of that one is not addressed by this PR, will file a separate one.

[github-actions]

The QGIS project highly values your contribution and would love to see this work merged! Unfortunately this PR has not had any activity in the last 14 days and is being automatically marked as "stale". If you think this pull request should be merged, please check

• that all unit tests are passing

• that all comments by reviewers have been addressed

• that there is enough information for reviewers, in particular

  • link to any issues which this pull request fixes

  • add a description of workflows which this pull request fixes

  • add screenshots if applicable

• that you have written unit tests where possible
  In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this pull request.
  If there is no further activity on this pull request, it will be closed in a week.

[rouault]

Maintaining PostgreSQL < 8.4 code paths looks like self inflicted pain at that point, given it has been long unsupported.

[strk]

Agreed. but it's better done in an ad-hoc PR

[qgis-bot]

The backport to queued_ltr_backports failed:

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

stderr

error: could not apply a244a19d9f7... Fix editability of tables with column-limited insert privilege
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 src/providers/postgres/qgspostgresprovider.cpp
CONFLICT (content): Merge conflict in src/providers/postgres/qgspostgresprovider.cpp
Auto-merging tests/src/python/test_provider_postgres.py

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-queued_ltr_backports queued_ltr_backports
# Navigate to the new working tree
cd .worktrees/backport-queued_ltr_backports
# Create a new branch
git switch --create backport-57810-to-queued_ltr_backports
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick a244a19d9f7b7fea580ca6bca413eb047479cbe0
# Push it to GitHub
git push --set-upstream origin backport-57810-to-queued_ltr_backports
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-queued_ltr_backports

Then, create a pull request where the base branch is queued_ltr_backports and the compare/head branch is backport-57810-to-queued_ltr_backports.