Hi Adrian ,
We have the below output. What we need to change.
bash-4.2$ ora2pg -c ora2pg.bidder.conf -t SHOW_ENCODING
Current encoding settings that will be used by Ora2Pg:
Oracle NLS_LANG AMERICAN_AMERICA.AL32UTF8
Oracle NLS_NCHAR AL32UTF8
Oracle NLS_TIMESTAMP_FORMAT YY
王若楠 wrote:
> I want to find a way to reduce the lock waiting and improve the
> performance.
You either have to make the transactions shorter, or you let the
different clients modify different rows, so that they don't lock each
other.
That concurrent writers on the same data lock each other is
una
hello,Laurenz Albe
Yes, pg_locks is only an item that does not get a lock in the view. The test data is 300 warehouses connections, and the CPU is only about 60%. I think the lock becomes a performance bottleneck at this time. I want to find a way to reduce the lock waiting and improve the perform
王若楠 wrote:
> We used benchmarksql 4.1.0 to test the performance of PG12 beta TPCC.
> We found performance bottlenecks on lock transactionid.
You included an attachment with results from the "pg_locks" view
where "granted" is FALSE for all entries.
I'll assume that these are not *all* the entries
