On 9/24/24 09:52, Andres Freund wrote:
Hi,
On 2024-09-24 13:53:49 +0100, Alastair Turner wrote:
Since the build and runtime versions may differ for some things like llvm,
libxml2 and the interpreters behind some of the PLs, it may be valuable to
expand the view and show two values - a build tim
Hi,
On 2024-09-24 13:53:49 +0100, Alastair Turner wrote:
> Since the build and runtime versions may differ for some things like llvm,
> libxml2 and the interpreters behind some of the PLs, it may be valuable to
> expand the view and show two values - a build time (or configure time)
> value and a
On Mon, 23 Sept 2024 at 19:45, Tom Lane wrote:
...
> Maybe another idea could be a new system view?
>
> => select * from pg_system_version;
> property | value
>
> core version | 18.1
> architecture | x86_64-pc-linux-gnu
> word size
> On Mon, Sep 23, 2024 at 02:45:18PM GMT, Tom Lane wrote:
> Maybe another idea could be a new system view?
>
> => select * from pg_system_version;
> property | value
>
> core version | 18.1
> architecture | x86_64-pc-linux-gnu
> word
Dmitry Dolgov <9erthali...@gmail.com> writes:
> On Sun, Sep 22, 2024 at 01:15:54PM GMT, Dmitry Dolgov wrote:
>> About a new function, I think that the llvm runtime version has to be
>> shown in some form by pgsql_version. The idea is to skip an emails
>> exchange like "here is the bug report" -> "c
> On Sun, Sep 22, 2024 at 01:15:54PM GMT, Dmitry Dolgov wrote:
> > On Sat, Sep 21, 2024 at 05:25:30PM GMT, Tom Lane wrote:
> >
> > Is there a way to get the llvm library's version at run time? If so
> > we could consider building a new function to return that.
>
> Yes, there is a C api LLVMGetVers
> On Sat, Sep 21, 2024 at 05:25:30PM GMT, Tom Lane wrote:
>
> Is there a way to get the llvm library's version at run time? If so
> we could consider building a new function to return that.
Yes, there is a C api LLVMGetVersion to get the major, minor and patch
numbers. The jit provider could be e
Dmitry Dolgov <9erthali...@gmail.com> writes:
> In many jit related bug reports, one of the first questions is often
> "which llvm version is used". How about adding it into the
> PG_VERSION_STR, similar to the gcc version?
I'm pretty down on this idea as presented, first because our version
strin
st 21. 8. 2024 v 12:20 odesÃlatel Dmitry Dolgov <9erthali...@gmail.com>
napsal:
> In many jit related bug reports, one of the first questions is often
> "which llvm version is used". How about adding it into the
> PG_VERSION_STR, similar to the gcc version?
>
+1
Pave
