PostgreSQL 11? #48
PostgreSQL 11? #48
Comments
Hello, |
@za-arthur make USE_PGXS=1 |
Try |
@levin222 , can you try the solution from #27 (comment)? |
@za-arthur my system is Ubuntu 16.04 after sudo apt-get install systemtap-sdt-dev root@vps01:~/rum# make USE_PGXS=1 gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -g -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -pie -fno-omit-frame-pointer -fPIC -I. -I./ -I/usr/include/postgresql/11/server -I/usr/include/postgresql/internal -I/usr/include/x86_64-linux-gnu -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2 -I/usr/include/mit-krb5 -c -o src/rumsort.o src/rumsort.c |
apt install postgresql 11 I try in 2 vps get the same error |
@levin222 , did you install |
FWIW, I get the same error on Kubuntu-cosmic;
|
Ok. Thank you! I'll try to understand what happens here. |
So it was because of renames of structures and functions in I pushed a commit which fixes this. I'll ask maintainers of |
I wrote to the PostgreSQL mailing list. So will wait: |
1.3.1 works with 11.1, but not with 10.6:
|
Hm, interesting. It seems REL_10_6 didn't get those renames, but REL_11_1 got. Maybe REL_10_7 will have different names in rbtree.h, so it is necessary to handle 10.6 and future 10.7 differently. |
Handle it differently for PostgreSQL 10.6 and 10.7.
Fwiw, if you are pushing out an update, tag it as 1.3.2, 1.3.1 has already been uploaded to Debian. |
Yes, I pushed recently tag 1.3.2. It was fixed there. |
I just checked the PG git tree, 10.7 will indeed have the renames. The renames were meant to be part of 11.2, but due to the "emergency" disabling of the recheck_on_update optimizations, 11.1 got re-tagged so that commit slipped in. Duh. |
Yeah, understood. It is good that the problem was solved! |
|
Hello!
I have the following error:
My pg_config:
The text was updated successfully, but these errors were encountered: