dabda64152
Some fields of the sinfo struct are modified within PG_TRY and then referenced within PG_CATCH, so as with recent patch to async.c, "volatile" is necessary for strict POSIX compliance; and that propagates to a couple of subroutines as well as materializeQueryResult() itself. I think the risk of actual issues here is probably higher than in async.c, because storeQueryResult() is likely to get inlined into materializeQueryResult(), leaving the compiler free to conclude that its stores into sinfo fields are dead code. |
||
|---|---|---|
| .. | ||
| expected | ||
| input | ||
| output | ||
| sql | ||
| .gitignore | ||
| Makefile | ||
| dblink--1.0--1.1.sql | ||
| dblink--1.1.sql | ||
| dblink--unpackaged--1.0.sql | ||
| dblink.c | ||
| dblink.control | ||
| dblink.h | ||
| pg_service.conf | ||