Михаил

> Please add the following code to Makefile of sqlite_fdw. After that, you can execute `make check` with PostGIS. Thanks, @son-phamngoc , but this is not enough. Please read the...

@son-phamngoc , current code works with both PostGIS and `bytea` data in PostgreSQL. Please note, SpatiaLite GIS `blob` doesn't accept any data without SRID. Now I am writing diagnostics and...

@son-phamngoc , now this PR contains universal code for both PostGIS data types and `bytea` domains and big test datasets. There is no problems with PostGIS compilation, but there are...

> Please wait for a few days @son-phamngoc , no problems, I am also studying `make install` configurations and anyway construction of CI solution will not fast.

@son-phamngoc , any perspectives to see PostGIS installation? I have found this GNU coding standards fragment, but not from PostGIS `configure` script: ``` # Installation directory options. # These are...

> ``` > make ENABLE_GIS=1 > ``` Thanks, @son-phamngoc ! This is compile mode I want and planned. Unfortunately I know to few to transfer this flag to `.c` files....

> Please ask @t-kataym if you are ready and want to start reviewing. Thanks, @son-phamngoc ! I have done. Also I have [already tested branch](https://github.com/mkgrgis/sqlite_fdw/tree/journal_mode) where changes also doesn't intersect...

Also added new `UPSERT` syntax, see https://sqlite.org/releaselog/3_35_0.html During drafting I have seen, we need to increase SQLite version for `RETURNING` support, 3.34.0 now.

@t-kataym , if a new release is yet planned, I am ready to present `RETURNING` C infrastructure aligned with the newest `postgres_fdw` or even initial `INSERT ... RETURNING` and `UPDATE...

Thanks for clarification, @t-kataym! I am ready to rebase existed PRs. What about testing of 2-3 obsolete PostgreSQL versions until this doesn't make a C code harder? As we can...