Михаил

@lamdn1409 , now we have only problem for lower versions of PostgreSQL which is in not successfully tests. Some `rc = SQLITE_ROW` algorithm branch is active instead of common behaviour....

@lamdn1409 , please check first review comments again. I think most of them should be resolved.

Thanks for 2nd review, @lamdn1409! Let's summarise current problems: - [ ] different behaviour for PostgreSQL 14- and PostgreSQL 15+ - [ ] void `RETURNING` results https://github.com/pgspider/sqlite_fdw/pull/107#discussion_r1901432047 - [ ]...

@lamdn1409 , I have a plan to separate this PR into 2 PRs: 1. Add C code infrastructure for `RETURNING` support * Align naming to `postgres_fdw` * Add formal `extra/returning`...

@devrimgunduz , after 2025-04 there was no activity in any [pgspider](https://github.com/pgspider) repository. I can merge all new features with the same CI and PostgreSQL 18 support in my fork. Will...

I am on FDW vacations, @devrimgunduz , but there is a plan to release PG18 support in my fork near 2025-10-20.

Hello, @devrimgunduz! I have successfully merged all of new features and adopted code to compilable for PG18. Now I have [some difference](https://github.com/mkgrgis/sqlite_fdw/actions/runs/18154487792/job/51671295808) in PG18 tests, but cannot decide if this...

@t-kataym, could you please plan review of this ready PR by pgspider team?

All your comments have been checked, @son-phamngoc ! Please ensure now this PR is normal. I'll squash all commits if all is good before merging.

@son-phamngoc, look like all of the problems are resolved. Please confirm current implementation and start 3rd round of review.