From: | "Erik Rijkers" <er(at)xs4all(dot)nl> |
---|---|
To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
Cc: | obartunov(at)gmail(dot)com, "David Wheeler" <david(at)justatheory(dot)com>, "Pgsql Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: nested hstore patch |
Date: | 2014-01-14 00:18:17 |
Message-ID: | 4115fddf0fe371918711ed47e05eba1e.squirrel@webmail.xs4all.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, January 13, 2014 18:30, Andrew Dunstan wrote:
>
>
> On 01/13/2014 11:16 AM, Oleg Bartunov wrote:
>> Andrew,
>>
>> did you run perl script ? Actually, I found, that operator table needs
>> to be fixed.
>>
>
> No. My build machine doesn't actually have DBD::Pg installed. Can you
> send me a patch if you don't want to push it yourself, or maybe Erik can
> send a pacth top adjust the table.
>
> [ nested_hstore_and_jsonb-2.patch ]
( centos 6.5, gcc 4.8.2. )
The patch applies & compiles with warnings (see below).
The opr_sanity test fails during make check: regression.diffs attached.
Also attached are changes to hstore.sgml, to operator + functions table, plus some typos.
Thanks,
Erik Rijkers
make
jsonfuncs.c: In function each_object_field_end_jsonb:
jsonfuncs.c:1328:7: warning: assignment from incompatible pointer type [enabled by default]
val = DatumGetPointer(DirectFunctionCall1(jsonb_in, CStringGetDatum(cstr)));
^
jsonfuncs.c: In function elements_array_element_end_jsonb:
jsonfuncs.c:1530:8: warning: assignment from incompatible pointer type [enabled by default]
jbval = DatumGetPointer(DirectFunctionCall1(jsonb_in, CStringGetDatum(cstr)));
^
make contrib:
hstore_io.c: In function array_to_hstore:
hstore_io.c:1694:30: warning: result may be used uninitialized in this function [-Wmaybe-uninitialized]
PG_RETURN_POINTER(hstoreDump(result));
Attachment | Content-Type | Size |
---|---|---|
regression.diffs | application/octet-stream | 2.1 KB |
hstore.sgml.20140114.diff | text/x-patch | 6.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2014-01-14 00:20:36 | Re: plpgsql.consistent_into |
Previous Message | Florian Pflug | 2014-01-14 00:16:44 | Re: plpgsql.consistent_into |