-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MB Search relies on Postgres 9.3+ for to_json (so PGXL and Greenplum are out of luck) #49
Comments
my two cents: not hard. On Tue, Sep 22, 2015 at 6:03 PM alldefector [email protected]
|
OK, I managed to install the backport on PGXL, with the help of these posts: Steps:
|
@alldefector Awesome! I had to sometimes do a |
Btw the SQL produced by MB for loading into ES can be seen with: mindbender hack jqDDlog '"has_spouse_candidates" | relationByName | sqlForRelationNestingAssociated' <(ddlog export-schema app.ddlog) Just replace the first |
Is there any progress on solving this for greenplum? |
Not yet...
However, I think it may not be reliable with long values (when I tried half a year ago). Any help to improve it is much appreciated :) |
Learned from @netj that MB Search works only with Postgresql 9.3 (and not PGXL or Greenplum) because it uses the
to_json
function.How hard is it to drop the requirement for
to_json
? Or at least ship a basic version of it. E.g., the following could be used to patch PGXL:http://www.pgxn.org/dist/json_enhancements/doc/json_enhancements.html
https://bitbucket.org/IVC-Inc/json_enhancements/overview
The text was updated successfully, but these errors were encountered: