On Tue, Nov 16, 2021 at 5:43 PM Robert Creager wrote:
> One CPU is pegged, the data has been sent over STDIN, so Postgres is not
> waiting for more, there are no other queries running using this select:
So PostgreSQL is eating 100% CPU, with no value shown in
wait_event_type, and small numbers o
On Tue, Nov 16, 2021 at 04:43:25AM +, Robert Creager wrote:
> We’re executing the following copy to fill a table with approximately 5k
> records, then repeating for a total of 250k records. Normally, this copy
> executes < 1 second, with the entire set taking a couple of minutes. The
> prob
Ashkil Dighin writes:
> I suspect lock contention and performance issues with __int128. And I would
> like to check the performance by forcibly disabling int128(Maxalign16bytes)
> and enable like long long(maxlign 8bytes).
> Is it possible to disable int128 in PostgreSQL?
Sure, you can build wit
On Mon, Nov 15, 2021 at 8:57 AM Mladen Gogala
wrote:
>
> On 11/15/21 00:04, Pavel Stehule wrote:
>
>
> Hi
>
>
>> There is a CentOS8-stream version which solves the problem but I cannot
>> use that in the office. I will probably have to wait for another month
>> before OL8 has everything that I ne
On 11/15/21 00:04, Pavel Stehule wrote:
Hi
There is a CentOS8-stream version which solves the problem but I
cannot
use that in the office. I will probably have to wait for another
month
before OL8 has everything that I need in its repositories. Now, the
question is wha
Hi
I suspect lock contention and performance issues with __int128. And I would
like to check the performance by forcibly disabling int128(Maxalign16bytes)
and enable like long long(maxlign 8bytes).
Is it possible to disable int128 in PostgreSQL?
On Thursday, October 28, 2021, Andres Freund wrote
