Hi Askhil
PostgreSQL utilizes lightweight locks(LWLocks) to synchronize and control
access to the buffer content. A process acquires an LWLock in a shared
mode to read from the buffer and an exclusive mode to write to the buffer.
Therefore, while holding an exclusive lock, a process prevents ot
On Wed, Nov 17, 2021 at 11:51 AM Thomas Munro wrote:
> It's the right output format, but isn't /pid == '$PID'/ only going to
> match one single process called "postgres"? Maybe /execname ==
> "postgres"/ to catch them all?
Oh, duh, it's the top CPU one. Makes sense. Never mind :-)
On Wed, Nov 17, 2021 at 11:40 AM Robert Creager
wrote:
> Presuming this is the type of output you are expecting:
>
> CPU IDFUNCTION:NAME
> 0 58709:tick-10s
>
>
> postgres`AtEOXact_LargeObject+0x11
> postgres`CommitTrans
On Nov 15, 2021, at 10:50 PM, Thomas Munro
mailto:thomas.mu...@gmail.com>> wrote:
This message originated outside your organization.
On Tue, Nov 16, 2021 at 5:43 PM Robert Creager
mailto:robe...@spectralogic.com>> wrote:
One CPU is pegged, the data has been sent over STDIN, so Postgres is not
On Nov 15, 2021, at 10:29 PM, Justin Pryzby
mailto:pry...@telsasoft.com>> wrote:
This message originated outside your organization.
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 repeat
Yes, currently focusing affects queries as well.
In meanwhile on analysis(hardware level) and sample examples noticed
1. GCC performance better than Clang on int128 .
2. Clang performance better than GCC on long long
the reference example
https://stackoverflow.com/questions/63029428/why-is-int128
