Shout out to grapeseed oil
Yup. Just under a 501c3 to help ensure pgrx outlives us. Huge thanks to TCDI (www.tcdi.com) for continuing to fund development.
Y'all have built something cool. I'm excited to see where it goes from here. If there's anything the pgrx team can do to help, just let us know.
If you build it, they'll come. The only limit is yourself!
Nice deck, Ryan! And thanks for the mentions. ;)
I think maybe what you’re really looking for are the files here: https://github.com/pgcentralfoundation/pgrx/tree/c2eac033856... Those are the internals we currently expose as unsafe “sys” bindings. As we/contributors…
I don’t think we even expose the TableAM APIs? They are incredibly hard to generate bindings for from the C headers — lots of inline functions and complex #define macros. We have an ambitious goal with pgrx and it’s…
Thank you. I’ll pass this on to the team.
If you’re aware of bugs that fall within plrust’s domain we’d appreciate any and all reports via GitHub!
Always nice to see pgx being used in the wild! Awesome work.
I don’t pay any attention to what the cloud providers are doing. I have no control over them so….. eh. ZDB is still alive and well but I have a real job now too.
I can definitely reword that if it's confusing.
> Doing so would require ElasticSearch to reach consensus on every read/write ZomboDB only requires that ES have a view of its index that's consistent with the active Postgres transaction snapshot. ZDB handles this by…
I wonder what the ZomboDB developers are up to now? What great text-search-in-postgres things could they be secretly working on?
https://github.com/zombodb/pgx/releases/tag/v0.0.7 !boom!
I'd be inclined to agree. That said, it'd be easy to prototype with pgx, assuming that compression library exists in the Rust ecosystem too?
I've noodled the idea of a pl/pg_rust, but the whole "Cargo.toml" and downloading dependencies from the internet seems bad. I see what you're saying about no_std tho. Could be doable.
That is interesting. pgx does a lot of that too, but for only pg10/11/12. And then it post-processes the bindings and builds a "common.rs" for symbols that are identical across versions. That way you can target all…
blush
Sure! Top is Postgres, bottom is pgx, after running each 5 times... test=# SELECT count(*) FROM (SELECT generate_series(1, 10000000)) s; count ---------- 10000000 (1 row) Time: 399.630 ms test=# SELECT count(*) FROM…
Yes there is. It's not documented/example'd yet tho. There's a derive macro called #[derive(PostgresType)]. Combine that with serde's Serialize, Deserialize, and you're gtg. I'm going to be working on more docs and…
Fair. With pgx, however, Rust "panic!"s are translated into standard Postgres "ERROR"s, such that instead of crashing, only the current transaction aborts. So while you're pretty much correct in general, pgx handles it…
That's a great question, and one probably best answered over on pgx's GitHub page. But! I plan on adding a command to "cargo-pgx" to package up the extension for you into a directory structure (or tarball, maybe). The…
One more follow-up... The top one is pgx, the bottom is Postgres. So there's a little room for improvement here with pgx, but that's okay for a v0.0.3 release. test=# select count(*) from srf.generate_series(1,…
Thank you! If you decide to jump into it, definitely let us know any pain points you have. It takes a bit of time to work out the kinks in a thing like this.
Shout out to grapeseed oil
Yup. Just under a 501c3 to help ensure pgrx outlives us. Huge thanks to TCDI (www.tcdi.com) for continuing to fund development.
Y'all have built something cool. I'm excited to see where it goes from here. If there's anything the pgrx team can do to help, just let us know.
If you build it, they'll come. The only limit is yourself!
Nice deck, Ryan! And thanks for the mentions. ;)
I think maybe what you’re really looking for are the files here: https://github.com/pgcentralfoundation/pgrx/tree/c2eac033856... Those are the internals we currently expose as unsafe “sys” bindings. As we/contributors…
I don’t think we even expose the TableAM APIs? They are incredibly hard to generate bindings for from the C headers — lots of inline functions and complex #define macros. We have an ambitious goal with pgrx and it’s…
Thank you. I’ll pass this on to the team.
If you’re aware of bugs that fall within plrust’s domain we’d appreciate any and all reports via GitHub!
Always nice to see pgx being used in the wild! Awesome work.
I don’t pay any attention to what the cloud providers are doing. I have no control over them so….. eh. ZDB is still alive and well but I have a real job now too.
I can definitely reword that if it's confusing.
> Doing so would require ElasticSearch to reach consensus on every read/write ZomboDB only requires that ES have a view of its index that's consistent with the active Postgres transaction snapshot. ZDB handles this by…
I wonder what the ZomboDB developers are up to now? What great text-search-in-postgres things could they be secretly working on?
https://github.com/zombodb/pgx/releases/tag/v0.0.7 !boom!
I'd be inclined to agree. That said, it'd be easy to prototype with pgx, assuming that compression library exists in the Rust ecosystem too?
I've noodled the idea of a pl/pg_rust, but the whole "Cargo.toml" and downloading dependencies from the internet seems bad. I see what you're saying about no_std tho. Could be doable.
That is interesting. pgx does a lot of that too, but for only pg10/11/12. And then it post-processes the bindings and builds a "common.rs" for symbols that are identical across versions. That way you can target all…
blush
Sure! Top is Postgres, bottom is pgx, after running each 5 times... test=# SELECT count(*) FROM (SELECT generate_series(1, 10000000)) s; count ---------- 10000000 (1 row) Time: 399.630 ms test=# SELECT count(*) FROM…
Yes there is. It's not documented/example'd yet tho. There's a derive macro called #[derive(PostgresType)]. Combine that with serde's Serialize, Deserialize, and you're gtg. I'm going to be working on more docs and…
Fair. With pgx, however, Rust "panic!"s are translated into standard Postgres "ERROR"s, such that instead of crashing, only the current transaction aborts. So while you're pretty much correct in general, pgx handles it…
That's a great question, and one probably best answered over on pgx's GitHub page. But! I plan on adding a command to "cargo-pgx" to package up the extension for you into a directory structure (or tarball, maybe). The…
One more follow-up... The top one is pgx, the bottom is Postgres. So there's a little room for improvement here with pgx, but that's okay for a v0.0.3 release. test=# select count(*) from srf.generate_series(1,…
Thank you! If you decide to jump into it, definitely let us know any pain points you have. It takes a bit of time to work out the kinks in a thing like this.