Lukas Fittl

@Corion The general approach taken is that code is extracted using LLVM/clang (plus a Ruby helper script), see https://github.com/lfittl/libpg_query/blob/10-latest/scripts/extract_source.rb That means the code that gets extracted is partially dependent on...

@Corion Nice, thanks for sharing! Its a priority for me to make progress on this, however there is a few other things on my plate too unfortunately. I'll update here...

@akeeman Not yet - thanks for checking! I'm curious, whats your use case for the library on Windows?

@amhuhn2 Nothing to report yet, but thanks for the additional context of your use case - that is helpful to know. I *may* be able to take some time to...

@daisuke-yoshimoto No updates at this point - Windows support is definitely doable, but I (and the team at pganalyze) have our hands full with other things. PRs are of course...

@heysinghal @404shades Its still something I'd like to support eventually, but its not a high priority at this point (and there is no ETA for supporting it). The main challenge...

@merqurio The most important part is the extract_source script: https://github.com/lfittl/libpg_query/blob/10-latest/scripts/extract_source.rb Typically what I would do for a new Postgres version is to run that and then work through any compilation...

@merqurio Interesting - yes, please feel free to keep updating this issue, if we can adjust the scripts slightly to accommodate this case, that would be fine I think.

@merqurio Nice, well done! Very happy to see that this actually worked :)

@merqurio Good question - do you have a copy of your work available somewhere? It probably makes sense to keep the generated source tree separate (as that would differ between...