Index with new opclass not used for sorting

2019-06-21 Thread Ancoron Luciferis
Hi, I am creating a new operator class for version 1 UUID's with an extension and thought I was almost done by implementing everything including SortSupport and creating a new opclass as follows: CREATE OPERATOR CLASS uuid_timestamp_ops FOR TYPE uuid USING btree AS OPERATOR1

Re: Index with new opclass not used for sorting

2019-06-21 Thread Ancoron Luciferis
On 21/06/2019 15:36, Tom Lane wrote: > Ancoron Luciferis writes: >> I am creating a new operator class for version 1 UUID's with an >> extension and thought I was almost done by implementing everything >> including SortSupport and creating a new opclass as follows: &

Re: Kubernetes, cgroups v2 and OOM killer - how to avoid?

2025-04-08 Thread Ancoron Luciferis
On 2025-04-07 15:21, Joe Conway wrote: On 4/5/25 07:53, Ancoron Luciferis wrote: I've been investigating this topic every now and then but to this day have not come to a setup that consistently leads to a PostgreSQL backend process receiving an allocation error instead of being k

Kubernetes, cgroups v2 and OOM killer - how to avoid?

2025-04-07 Thread Ancoron Luciferis
Hi, I've been investigating this topic every now and then but to this day have not come to a setup that consistently leads to a PostgreSQL backend process receiving an allocation error instead of being killed externally by the OOM killer. Why this is a problem for me? Because while applicati