Re: performance of first exec of prepared statement

2020-04-17 Thread Rob Sargent
> On Apr 17, 2020, at 7:34 AM, Ted Toth wrote: > >  > > >> On Fri, Apr 17, 2020 at 8:28 AM Ted Toth wrote: >> >> >>> On Thu, Apr 16, 2020 at 8:09 PM Rob Sargent wrote: >>> On 4/16/20 6:15 PM, Adrian Klaver wrote: >>> > On 4/16/20 4:59 PM, Ted Toth wrote: >>> >> >>> >> >>> >> On Thu, Apr

Re: performance of first exec of prepared statement

2020-04-17 Thread Ted Toth
On Fri, Apr 17, 2020 at 8:28 AM Ted Toth wrote: > > > On Thu, Apr 16, 2020 at 8:09 PM Rob Sargent wrote: > >> On 4/16/20 6:15 PM, Adrian Klaver wrote: >> > On 4/16/20 4:59 PM, Ted Toth wrote: >> >> >> >> >> >> On Thu, Apr 16, 2020 at 6:29 PM Ted Toth > >> > wrote: >> >>

Re: performance of first exec of prepared statement

2020-04-17 Thread Ted Toth
On Thu, Apr 16, 2020 at 8:09 PM Rob Sargent wrote: > On 4/16/20 6:15 PM, Adrian Klaver wrote: > > On 4/16/20 4:59 PM, Ted Toth wrote: > >> > >> > >> On Thu, Apr 16, 2020 at 6:29 PM Ted Toth >> > wrote: > >> > >> I've noticed that the first exec of an INSERT prepared

Re: performance of first exec of prepared statement

2020-04-16 Thread Rob Sargent
On 4/16/20 6:15 PM, Adrian Klaver wrote: On 4/16/20 4:59 PM, Ted Toth wrote: On Thu, Apr 16, 2020 at 6:29 PM Ted Toth > wrote:     I've noticed that the first exec of an INSERT prepared statement     takes ~5 time longer (I'm using libpq in C and wrapping the calls t

Re: performance of first exec of prepared statement

2020-04-16 Thread Adrian Klaver
On 4/16/20 4:59 PM, Ted Toth wrote: On Thu, Apr 16, 2020 at 6:29 PM Ted Toth > wrote: I've noticed that the first exec of an INSERT prepared statement takes ~5 time longer (I'm using libpq in C and wrapping the calls to time them) then subsequent exec's is

Re: performance of first exec of prepared statement

2020-04-16 Thread Ted Toth
On Thu, Apr 16, 2020 at 6:29 PM Ted Toth wrote: > I've noticed that the first exec of an INSERT prepared statement takes ~5 > time longer (I'm using libpq in C and wrapping the calls to time them) then > subsequent exec's is this the expected behavior and if so is there any > thing I can do to mi