Re: [PERFORM] Savepoint and Releasepoint in Logs

[Jeff Janes]

On Fri, Jun 17, 2016 at 8:19 AM,   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 9 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 (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

Re: [PERFORM] Index not used

[meike . talbach]

> ​Or, better, persuade the app to label the value "

​

public.push_guid
​" since that is the column's type​...a type you haven't defined for us.  If you get to add explicit casts this should be easy...but I'm not familiar with the framework you are using.

 

 

push_guid was a CHARACTER(36) column. I ended up converting it to CHARACTER VARYING(36).

Index is now being used and performance is as expected.

 

Thanks a lot

Meike