Re: Add a hook to allow modification of the ldapbindpasswd

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add a hook to allow modification of the ldapbindpasswd
Date: 2023-03-07 14:32:40
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2023-03-06 Mo 15:16, Gregory Stark (as CFM) wrote:
> The CFBot says this patch is failing but I find it hard to believe
> this is related to this patch...
> 2023-03-05 20:56:58.705 UTC [33902][client backend]
> [pg_regress/btree_index][18/750:0] STATEMENT: ALTER INDEX
> btree_part_idx ALTER COLUMN id SET (n_distinct=100);
> 2023-03-05 20:56:58.709 UTC [33902][client backend]
> [pg_regress/btree_index][:0] LOG: disconnection: session time:
> 0:00:02.287 user=postgres database=regression host=[local]
> 2023-03-05 20:56:58.710 UTC [33889][client backend]
> [pg_regress/join][:0] LOG: disconnection: session time: 0:00:02.289
> user=postgres database=regression host=[local]
> 2023-03-05 20:56:58.749 UTC [33045][postmaster] LOG: server process
> (PID 33898) was terminated by signal 6: Abort trap
> 2023-03-05 20:56:58.749 UTC [33045][postmaster] DETAIL: Failed
> process was running: SELECT * FROM writetest;
> 2023-03-05 20:56:58.749 UTC [33045][postmaster] LOG: terminating any
> other active server processes

Yeah. It says it's fine now. Neither of the two recent failures look
like they have anything to do with this.



Andrew Dunstan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mikhail Gribkov 2023-03-07 15:02:17 Re: GUC for temporarily disabling event triggers
Previous Message Maxim Orlov 2023-03-07 14:06:43 Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15)