On 8/12/22 18:26, Mark Murawski wrote:
On 8/12/22 18:11, Mark Murawski wrote:
On 8/4/22 15:10, demerphq wrote:
On Thu, 4 Aug 2022 at 17:04, Mark Murawski
wrote:
On 8/4/22 02:50, demerphq wrote:
On Thu, 4 Aug 2022 at 01:58, Mark Murawski
wrote:
I'm still not ge
On 8/12/22 18:11, Mark Murawski wrote:
On 8/4/22 15:10, demerphq wrote:
On Thu, 4 Aug 2022 at 17:04, Mark Murawski
wrote:
On 8/4/22 02:50, demerphq wrote:
On Thu, 4 Aug 2022 at 01:58, Mark Murawski
wrote:
I'm still not getting something... if I want to fi
On 8/4/22 15:10, demerphq wrote:
On Thu, 4 Aug 2022 at 17:04, Mark Murawski
wrote:
On 8/4/22 02:50, demerphq wrote:
On Thu, 4 Aug 2022 at 01:58, Mark Murawski
wrote:
I'm still not getting something... if I want to fix the
code-as-is and do
On 8/4/22 02:50, demerphq wrote:
On Thu, 4 Aug 2022 at 01:58, Mark Murawski
wrote:
I'm still not getting something... if I want to fix the code-as-is
and do this:
FNsv = get_sv("main::_FN", GV_ADD);
if (!FNsv)
ereport(ERRO
On 7/27/22 13:20, demerphq wrote:
A general rule of thumb however is that any item you create yourself
which is not "owned by perl" by being attached to some data structure
it exposes is your problem to deal with. So for instance this:
FNsv = get_sv("main::_FN", GV_ADD);
is getting you
On 7/27/22 13:20, demerphq wrote:
On Wed, 27 Jul 2022 at 17:46, Mark Murawski
wrote:
Hi All!
I'm working on a new feature for plperl in postgresql to populate
some
metadata in main::_FN for running plperl functions from postgres sql.
I've snipped out some
