Ana Hobden

@xitep It's been too long for me to remember. :P I'm sorry. Maybe it's better just to not do this then.

There are a couple raft implementations floating around including one inside of tikv.

Can you merge with this repo's `prepare-for-new-type-mapping` and ping me on discord when you do? :)

Hmmm I think if you built the extesion with the `pg_test` feature on you could do like `cargo pgx run --features pg_test` then presumably you could run the generated test...

I'm a bit confused here, you're running `cargo pgx install` inside a `build.rs`? You can do `Command.new("cargo-pgx").args(["pgx", "install"]).env_remove("PROFILE")` if you really want.

@TimeToogo `cargo pgx install` is intended to use release by default, you'd need to do `cargo pgx install --debug` for debug.

I think it's safe to remove this and I am not entirely sure it is intended. I think we could merge this. :)

`cargo pgx install` defaults to release, but should be able to be toggled down to debug with `cargo pgx install --debug`. The user is reporting because their own crate's `build.rs`...

@workingjubilee I think it could be billed as a *trans*piler. :smirk:

Would you believe I clicked the wrong link in Rustdoc? Sorry.