JayCeeJr

This would be great, looks like it has been sitting a while. As far as s3 goes we could utilize the ETag to verify if the backend file has changed.

I have the same issue, once you get past the first level of nesting `POST` and `PUT` return the parent_pk key error. Have you found a workaround @cerahmed

I am having the same issue in CentOS 7.1 ``` root@db0 /tmp/PostgreSQL-Temporal # make cp temporal.sql.in sql/temporal--0.7.1.sql sed 's,MODULE_PATHNAME,$libdir/temporal,g' temporal.sql.in >temporal.sql gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4...

We had some legacy stuff using this version, we modified our code to use the native syntax in the latest Postgres. A prime example of technical debt :).