Re: Entities created in one query not available in another in extended protocol - Mailing list pgsql-hackers

From Sehrope Sarkuni
Subject Re: Entities created in one query not available in another in extended protocol
Date
Msg-id CAH7T-aq7oc9h1iGCq-xEV=tD40RSEz1eHTn-xQTjNdPdLYoW9w@mail.gmail.com
Whole thread Raw
In response to Re: Entities created in one query not available in another in extended protocol  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
The JDBC driver tries to handle this by estimating how much data has been buffered. It mainly comes up when executing batch INSERTS as a large number of statements may be sent to the backend prior to reading back any results.

There's a nice write up of the potential deadlock and the driver's logic to avoid it here:



Regards,
-- Sehrope Sarkuni
Founder & CEO | JackDB, Inc. | https://www.jackdb.com/

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Further issues with jsonb semantics, documentation
Next
From: Steve Kehlet
Date:
Subject: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1