latot

other note, I had in the project symbols that collide, I have excluded them, because the project just was not compiling but I other error, not like this one, still...

That can be completely by true, the reason I get confused is that: ```rust #[pg_extern] pub fn init() { unsafe { postgis_sys::bindings::pg_install_lwgeom_handlers(); } } ``` Right, that code works, the...

@workingjubilee this could be interesting, look at this: ``` Rebuilding pgrx_embed, in debug mode, for SQL generation with features pg16 warning: profiles for the non root package will be ignored,...

Hi! yes, actually I tried that a few mins ago, give the same problem. Rn from my limitated knowlodge, seems the linker is trying to solve the symbols that should...

I can doc some thing and show you the project if want to see it, I have the feeling you know about postgis, I has been able to run and...

I can avoid to think pgrx has something to do, in last tests I found this, the only way to get the error is using the combination of the function...

@workingjubilee I has been able to get a good point/clue of this happens, seems to be a collision between the bindings and pgrx: ```rust #[pg_extern] fn some_call_to_pg_internal() { unsafe {...

I'm playing/testing move postgis functions to rust, so I made them available to I can start moving one by one. I need access to a lot of internal functions, and...

Hi! no, I don't see nothing like that in the example project. Other projects (out of pgrx) do not request what is wrote here: https://github.com/pgcentralfoundation/pgrx/blob/develop/docs/src/extension/install.md pgrx seems to mount its...

Hi, thx for the answer! would be nice write that here. https://github.com/pgcentralfoundation/pgrx/tree/develop/pgrx-examples/shmem I think is better make that things explicit, when we are starting there is a lot of new...