Greg Sabino Mullane

We need to do our own parsing regardless, in the same way the arrays are done now. Whether or how to involve JSON::XS is somewhat secondary at the moment.

That sounds nice in theory, but I'm not sure how that would work in practice. The conversions happen in the Perl XS code, and involve low-level transformations of textual representations...

One of the problems is when and how does DBD::Pg search for custom types? On startup? As a special user-invoked function? As they are detected? (ideal, but too late).

We recently cleared up some problems with PQclear - could you see if a newer DBD::Pg clears it up for you? Anything >= version 3.10.3

I tried implementing this recently, but ran into a number of compilation issues with the new files. Will try again someday, but anyone else is welcome to take a stab...

Anyone want to take another pass at this? I'm still having issues, but maybe you two (@mtyson01 @machack666) will have better luck?

Anyone have ideas on this? I do not have a OSX system to test this out on. My internet investigation seems to reveal that disabling System Integrity Protection is not...

Update the README but unsure of what else to do. Give Makefile.PL a lot of brains so it detects the error and creates a wrapper shell script with the correct...

The pgbackrest lines do not parse because they do not respect log_line_prefix and just write their own format, which is a little rude. For now, --skip_non-parsed is indeed the best...

It is hard to tell from this if the problem is with Ora2Pg or DBD::Pg. Are you sure DBD::Pg is installed? See if this outputs anything: `perl -M5.01 -MDBD::Pg -e...