public inbox for [email protected]  
help / color / mirror / Atom feed
Savepoint and Releasepoint in Logs
2+ messages / 2 participants
[nested] [flat]

* Savepoint and Releasepoint in Logs
@ 2016-06-17 15:19 [email protected]
  2016-06-19 16:55 ` Re: Savepoint and Releasepoint in Logs Jeff Janes <[email protected]>
  0 siblings, 1 reply; 2+ messages in thread

From: [email protected] @ 2016-06-17 15:19 UTC (permalink / raw)
  To: pgsql-performance; +Cc: [email protected]

Hi ,

I am connecting to PostgreSQL 9.4 via an ODBC driver on Windows machine from MS VBA application. I am facing huge performance issues while inserting data continuously. On analysing the logs , there were around 90000 statements related to Save Points and Release Points.

duration: 2.000 ms
2016-06-17 12:45:02 BST LOG:  statement: RELEASE _EXEC_SVP_1018CCF8
2016-06-17 12:45:02 BST LOG:  duration: 1.000 ms
2016-06-17 12:45:05 BST LOG:  statement: SAVEPOINT _EXEC_SVP_186EB5C8
2016-06-17 12:45:05 BST LOG:  duration: 0.000 ms

I am guessing these statements are causing an overhead while inserting records in to the table. Could you please let me know if I need to change any configuration settings to avoid creating any save points as the transaction is handled in the application.

Thanks

Regards,
Eisha Shetty
ACCENTURE | UK-NEWCASTLE
* +44 7741587433
* [email protected]<mailto:[email protected]>
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.Accenture means Accenture (UK) Limited (registered number 4757301), registered in England and Wales with registered address at 30 Fenchurch Street, London EC3M 3BD.






^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Savepoint and Releasepoint in Logs
  2016-06-17 15:19 Savepoint and Releasepoint in Logs [email protected]
@ 2016-06-19 16:55 ` Jeff Janes <[email protected]>
  0 siblings, 0 replies; 2+ messages in thread

From: Jeff Janes @ 2016-06-19 16:55 UTC (permalink / raw)
  To: [email protected]; +Cc: pgsql-performance; [email protected]

On Fri, Jun 17, 2016 at 8:19 AM,  <[email protected]> wrote:
> Hi ,
>
> I am connecting to PostgreSQL 9.4 via an ODBC driver on Windows machine from
> MS VBA application. I am facing huge performance issues while inserting data
> continuously. On analysing the logs , there were around 90000 statements
> related to Save Points and Release Points.
>
>
>
> duration: 2.000 ms
>
> 2016-06-17 12:45:02 BST LOG:  statement: RELEASE _EXEC_SVP_1018CCF8
>
> 2016-06-17 12:45:02 BST LOG:  duration: 1.000 ms
>
> 2016-06-17 12:45:05 BST LOG:  statement: SAVEPOINT _EXEC_SVP_186EB5C8
>
> 2016-06-17 12:45:05 BST LOG:  duration: 0.000 ms
>
>
>
> I am guessing these statements are causing an overhead while inserting
> records in to the table.


The fact that there is 3 seconds between the release of one savepoint
the start of the next suggests that your client, not the server, is
the dominant bottleneck.

Cheers,

Jeff


-- 
Sent via pgsql-performance mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance




^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2016-06-19 16:55 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2016-06-17 15:19 Savepoint and Releasepoint in Logs [email protected]
2016-06-19 16:55 ` Jeff Janes <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox