On Fri, 26 Jan 2024 at 22:22, Jelte Fennema-Nio wrote:
>
> On Fri, 26 Jan 2024 at 13:11, Alvaro Herrera wrote:
> > I wonder, would it make sense to put all these new functions in a
> > separate file fe-cancel.c?
>
>
> Okay I tried doing that. I think the end result is indeed quite nice,
> having
so 27. 1. 2024 v 10:24 odesílatel Jelte Fennema-Nio
napsal:
> On Sat, 27 Jan 2024 at 08:35, Pavel Stehule
> wrote:
> > Until now, it is not possible to disable reporting. So clients can
> expect so reporting is workable.
>
> Sure, so if we leave the default as is that's fine. It's not as if
> th
On 1/26/24 15:39, Robert Haas wrote:
> On Wed, Jan 24, 2024 at 12:46 PM Tomas Vondra
> wrote:
>> I did try to explain how this works (and why) in a couple places:
>>
>> 1) the commit message
>> 2) reorderbuffer header comment
>> 3) ReorderBufferSequenceIsTransactional comment (and nearby)
>>
>> It
Buildfarm member caiman has been failing build for a couple weeks now.
The reason turns out to be that recent libxml2 has decided to throw
a "const" into the signature required for custom error handlers.
(API compatibility? What's that?)
I don't mind adopting the "const" --- it's a good idea in i
=?utf-8?Q?Micha=C5=82_K=C5=82eczek?= writes:
> On 27 Jan 2024, at 15:43, Tom Lane wrote:
>> Which FreeBSD version? Which krb5 package version?
>> Is this x86_64, or something else?
> Right, sorry:
> 1. X86_64
> 2. FreeBSD 13.2 (It is in a TrueNAS Jail if it makes any difference)
> 3. krb5-1.21
On Sat, Jan 27, 2024 at 11:00:01AM +0300, Alexander Lakhin wrote:
> 24.01.2024 20:46, Robert Haas wrote:
>> This is weird. There's a little more detail in the log file,
>> regress_log_002_blocks, e.g. from the first failure you linked:
>>
>> [11:18:20.683](96.787s) # before insert, summarized TLI
> On 27 Jan 2024, at 15:43, Tom Lane wrote:
>
> =?utf-8?Q?Micha=C5=82_K=C5=82eczek?= writes:
>> I am trying to use GSSAPI (Kerberos auth) on FreeBSD.
>
>> After several attempts I was able to build PostgreSQL 16 from FreeBSD ports
>> with GSSAPI support. The steps were:
>> 1. Uninstall Heim
=?utf-8?Q?Micha=C5=82_K=C5=82eczek?= writes:
> I am trying to use GSSAPI (Kerberos auth) on FreeBSD.
> After several attempts I was able to build PostgreSQL 16 from FreeBSD ports
> with GSSAPI support. The steps were:
> 1. Uninstall Heimdal
> 2. Install krb5 (MIT Kerberos)
> 3. Build Pg with GSS
Hi All,
I am trying to use GSSAPI (Kerberos auth) on FreeBSD.
After several attempts I was able to build PostgreSQL 16 from FreeBSD ports
with GSSAPI support. The steps were:
1. Uninstall Heimdal
2. Install krb5 (MIT Kerberos)
3. Build Pg with GSSAPI support
I configured pg_hba.conf to require
On Sat, 27 Jan 2024 at 08:35, Pavel Stehule wrote:
> Until now, it is not possible to disable reporting. So clients can expect so
> reporting is workable.
Sure, so if we leave the default as is that's fine. It's not as if
this GUC would be changed without the client knowing, the client would
be
On Sat, Jan 27, 2024 at 1:04 AM Jeff Davis wrote:
>
> All of these things are functionally equivalent -- the same thing is
> happening at the end. This is just a discussion about API style and how
> that will interact with hypothetical callers that don't exist today.
> And it can also be easily ch
24.01.2024 20:46, Robert Haas wrote:
This is weird. There's a little more detail in the log file,
regress_log_002_blocks, e.g. from the first failure you linked:
[11:18:20.683](96.787s) # before insert, summarized TLI 1 through 0/14E09D0
[11:18:21.188](0.505s) # after insert, summarized TLI 1 th
12 matches
Mail list logo
