Valery Meleshkin comments

Results 26 comments of


                                            Valery Meleshkin

Discrepancies between two versions of the start_erl.data

Same here

Segmentation fault when running pgx schema under CentOS 7

> do you also get a segfault without `--release`? That might make the stack trace a lot better... Not much better, unfortunately (looks exactly the same to me): ``` #0...

Segmentation fault when running pgx schema under CentOS 7

I had to re-install `cargo-pgx` with `--debug` to get a better stacktrace: ``` #0 core::clone::impls::_$LT$impl$u20$core..clone..Clone$u20$for$u20$u64$GT$::clone::ha646e36ad2dd08c1 (self=0x7fac2f4bd048) at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/clone.rs:185 #1 0x000055a4793f22b7 in _$LT$std..collections..hash..map..RandomState$u20$as$u20$core..clone..Clone$GT$::clone::h3c0527dfc1747d34 ( self=0x7fac2f4bd048) at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/collections/hash/map.rs:2882 #2 0x000055a4794b2e75 in _$LT$hashbrown..map..HashMap$LT$K$C$V$C$S$GT$$u20$as$u20$core..clone..Clone$GT$::clone::hb2878e43a3667026...

Segmentation fault when running pgx schema under CentOS 7

@Hoverbear I'm not able to upgrade pgx to `0.4.5` within that container, I keep getting ``` error: there is no argument named `message` --> /home/builder/.cargo/registry/src/github.com-1ecc6299db9ec823/pgx-pg-sys-0.4.5/src/submodules/guard.rs:275:21 | 275 | Ok(format!("{message} at...

Segmentation fault when running pgx schema under CentOS 7

Thank you! Seems like it did the trick locally in Docker. Trying to figure out what's up with our CI.

Segmentation fault when running pgx schema under CentOS 7

Never mind, I missed passing the pg-version feature in one of the places. It's all good 👍🏼

Adding a flag that forces `CREATE OR REPLACE FUNCTION` statements

> LGTM. Much appreciated Thank you! Could you approve the workflow to run?

Adding a flag that forces `CREATE OR REPLACE FUNCTION` statements

> I have opened #683 which serves as an alternative solution to this problem. Thank you for addressing this! #683 is ever so slightly more work for us, but we'll...

Adding a flag that forces `CREATE OR REPLACE FUNCTION` statements

Closing in favor of #683

Adding a flag that forces `CREATE OR REPLACE FUNCTION` statements

> I don't want to create more work for you, truly! We just are inevitably going to get "so, how about something that lets me have one function CREATEd and...