Anybody had a chance to look at the proposed patch?
Honza
On Tue, May 11, 2021 at 11:31 PM Honza Horak wrote:
> I missed Tom already started the thread, so just passing the other mail
> with a patch proposal here:
>
>
> https://www.postgresql.org/message-id/CA%2BHKMWPk0bMUvwV7x
I missed Tom already started the thread, so just passing the other mail
with a patch proposal here:
https://www.postgresql.org/message-id/CA%2BHKMWPk0bMUvwV7x4pYxbtNMCVvpBVi%3Do%3DS96MFYTr_WKZ7UA%40mail.gmail.com
Honza
On 5/11/21 6:13 PM, Tom Lane wrote:
$SUBJECT was discovered in Fedora 35 p
;
-- Make sure we don't get a "current transaction is aborted" error
SELECT 1 as test;
The attached patch makes the traceback look the same in Python 3.10 and
also in earlier versions.
Regards,
Honza
From dc0bbf61345c64d8ea261b85513611d9e7fc5606 Mon Sep 17 00:00:00 2001
From:
On 4/22/21 6:35 PM, Tom Stellard wrote:
On 4/21/21 6:40 AM, Honza Horak wrote:
On 3/19/21 8:15 PM, Tom Lane wrote:
Andres Freund writes:
I think the error above comes from a "mismatch" between the clang used
to compile bitcode, and the LLVM version linked to. Normally we're
so
On 3/19/21 8:15 PM, Tom Lane wrote:
Andres Freund writes:
I think the error above comes from a "mismatch" between the clang used
to compile bitcode, and the LLVM version linked to. Normally we're
somewhat tolerant of differences between the two, but there was an ABI
change at some point, leadin
On 4/14/21 7:55 PM, Tom Lane wrote:
Honza Horak writes:
I'm trying to understand what is happening in the following bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1935301
The upgrade process makes it a bit more difficult, but it seems to boil
down to this problem -- even
Hello hackers,
I'm trying to understand what is happening in the following bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1935301
The upgrade process makes it a bit more difficult, but it seems to boil
down to this problem -- even when pg_ctl gets clear guidance where to
find datadir
