Re: How batch processing works

On Thu, Sep 19, 2024 at 1:31 AM Lok P wrote: > Hello, > Saw multiple threads around the same , so I want some clarification. As we > know row by row is slow by slow processing , so in heavy write systems(say > the client app is in Java) , people asked to do DMLS in batches rather in a > row by ro

How batch processing works

Hello, Saw multiple threads around the same , so I want some clarification. As we know row by row is slow by slow processing , so in heavy write systems(say the client app is in Java) , people asked to do DMLS in batches rather in a row by row fashion to minimize the chatting or context switches be

Re: CREATE DATABASE command concurrency

Hi, In PostgreSQL, it's safe to run CREATE DATABASE at the same time from different places. If two commands try to create the same database, one will succeed, and the other will safely fail without causing any problems or incomplete database creation. On Wed, 18 Sept 2024 at 19:08, Wizard Brony w

Re: IO related waits

On 9/18/24 1:40 PM, veem v wrote: You were spot on. When we turned off the "auto commit" we started seeing less number of commits as per the number of batches. However we also started seeing deadlock issues. We have foreign key relationships between the tables and during t

Re: IO related waits

On Thu, 19 Sept 2024 at 02:01, veem v wrote: > > On Wed, 18 Sept 2024 at 05:07, Adrian Klaver > wrote: > >> On 9/17/24 12:34, veem v wrote: >> > >> >> It does if autocommit is set in the client, that is common to other >> databases also: >> >> https://dev.mysql.com/doc/refman/8.4/en/commit.html

Re: IO related waits

On Wed, 18 Sept 2024 at 05:07, Adrian Klaver wrote: > On 9/17/24 12:34, veem v wrote: > > > > It does if autocommit is set in the client, that is common to other > databases also: > > https://dev.mysql.com/doc/refman/8.4/en/commit.html > > > https://docs.oracle.com/en/database/oracle/developer-to

Re: CREATE DATABASE command concurrency

Christophe Pettus writes: >> On Sep 17, 2024, at 14:52, Wizard Brony wrote: >> What are the concurrency guarantees of the CREATE DATABASE command? For >> example, is the CREATE DATABASE command safe to be called concurrently such >> that one command succeeds and the other reliably fails without

Re: load fom csv

On 9/18/24 06:29, Rob Sargent wrote: On Sep 18, 2024, at 6:39 AM, Andy Hartman wrote:  psql -h $pgServer -d $pgDatabase -U $pgUser -c $copyCommand I'm wondering if it's waiting on P/w ? In a previous post I suggested: " To work through this you need to try what I call the crawl/walk/run

Re: CREATE DATABASE command concurrency

> On Sep 17, 2024, at 14:52, Wizard Brony wrote: > > What are the concurrency guarantees of the CREATE DATABASE command? For > example, is the CREATE DATABASE command safe to be called concurrently such > that one command succeeds and the other reliably fails without corruption? The concern

CREATE DATABASE command concurrency

What are the concurrency guarantees of the CREATE DATABASE command? For example, is the CREATE DATABASE command safe to be called concurrently such that one command succeeds and the other reliably fails without corruption?

Re: load fom csv

On Sep 18, 2024, at 6:39 AM, Andy Hartman wrote:psql -h $pgServer -d $pgDatabase -U $pgUser -c $copyCommand I'm wondering if it's waiting on P/w ?Thanks.Very likely.  Can you show the authentication mechanisms used (pg_hba)?On Tue, Sep 17, 2024 at 7:10 PM Andy Hartman wr

Re: load fom csv

psql -h $pgServer -d $pgDatabase -U $pgUser -c $copyCommand I'm wondering if it's waiting on P/w ? Thanks. On Tue, Sep 17, 2024 at 7:10 PM Andy Hartman wrote: > I'll echo vars and see if something looks strange. > > THanks. > > On Tue, Sep 17, 2024 at 3:46 PM Rob Sargent wrote: > >> >> >> > O