Dmitry Dolgov <9erthali...@gmail.com> writes:
> Thanks for checking this out. Here is the updated version with applied
> changes. The tests were failing due to injection_points library
> apparently linking something twice, triggering a duplication error I
> didn't expect. Since apparently it can ha
> On Sun, Mar 23, 2025 at 06:21:33PM GMT, Tom Lane wrote:
>
> FWIW, I think the 0004 patch is about to be mostly obsoleted by
> Andrei's proposal at [1]. To the extent that it's not obsoleted,
> I question whether it's something we want at all, given the ground
> rule that unprivileged users are n
> On Thu, Jan 02, 2025 at 10:36:48AM GMT, jian he wrote:
> hi.
> https://cirrus-ci.com/github/postgresql-cfbot/postgresql/cf%2F5318
> shows lots of failures, but it doesn't seem to tell you about doc build
> failure.
Thanks for checking this out. Here is the updated version with applied
changes.
On 2025-01-02 10:36:48 +0800, jian he wrote:
> https://cirrus-ci.com/github/postgresql-cfbot/postgresql/cf%2F5318
> shows lots of failures, but it doesn't seem to tell you about doc build
> failure.
It does:
https://cirrus-ci.com/task/6472750665039872?logs=docs_build#L0
[15:26:26.443] time make -
hi.
https://cirrus-ci.com/github/postgresql-cfbot/postgresql/cf%2F5318
shows lots of failures, but it doesn't seem to tell you about doc build failure.
+
+ pg_system_versions
+
+
+ pg_system_versions
+
+
should change to
+
otherwise cannot build doc.
+
+ pg_system_versions Colum
> On Mon, Oct 07, 2024 at 11:26:41AM GMT, Dmitry Dolgov wrote:
> > On Sun, Oct 06, 2024 at 12:01:29PM GMT, Joe Conway wrote:
> > I'm not sure why ICU is "Compile Time" rather than "Run Time" when it is not
> > statically linked.
>
> It reports U_UNICODE_VERSION at compile time. It's not necessarily
Joe Conway writes:
> On 10/16/24 08:47, Peter Eisentraut wrote:
>> That way, you can get this information without having to start a server
>> instance. (Maybe you can't start a server instance because it just
>> crashed because of some library version issue ...)
> While it is also useful to be a
On 10/16/24 08:47, Peter Eisentraut wrote:
On 06.10.24 17:36, Dmitry Dolgov wrote:
Based on the feedback in [1], here is my attempt at implementing system
views for versions reporting. It adds pg_system_versions for showing
things like core version, compiler, LLVM, etc, and pg_system_libraries
On 06.10.24 17:36, Dmitry Dolgov wrote:
Based on the feedback in [1], here is my attempt at implementing system
views for versions reporting. It adds pg_system_versions for showing
things like core version, compiler, LLVM, etc, and pg_system_libraries
for showing linked shared objects.
Is a
> On Sun, Oct 06, 2024 at 12:01:29PM GMT, Joe Conway wrote:
> On 10/6/24 11:36, Dmitry Dolgov wrote:
> > Hi,
> >
> > Based on the feedback in [1], here is my attempt at implementing system
> > views for versions reporting. It adds pg_system_versions for showin
Joe Conway writes:
> I think it would be nice to include a sha256 hash (or something similar)
> of the libraries as well, so that they can be checked against known good
> values.
That seems well outside the charter of this patch. Also, how would
we even get that information? A typical applica
On 10/6/24 11:36, Dmitry Dolgov wrote:
Hi,
Based on the feedback in [1], here is my attempt at implementing system
views for versions reporting. It adds pg_system_versions for showing
things like core version, compiler, LLVM, etc, and pg_system_libraries
for showing linked shared objects. I
Hi,
Based on the feedback in [1], here is my attempt at implementing system
views for versions reporting. It adds pg_system_versions for showing
things like core version, compiler, LLVM, etc, and pg_system_libraries
for showing linked shared objects. I think everyone has ageed that the
first was
13 matches
Mail list logo
