i'm trying to find an explanation for a strange behavior happening on postgres from a vbnet application.
1) vbnet windows form application
2) postgres 9.6 on win7 with raid5 (default installation so VACUUM on for all tables)
3) npgsql 3.1.9
4) a table with 250 rows and a unique index on the field used in the where clause of the update statement
5) Un update inside a transaction
the strange behavior is that this update:
UPDATE work.wip_pallets SET
WPAL_DATA_INI = value ,
STAZ_ID = value,
WPAL_PRESENZA_CEPA = value,
WPAL_SCARTO = value
WHERE CEPA_CODICE =filter value;
normally runs in 0 or less than 50ms but in some occasion it takes 400ms or more! Randomly (?)
The update have to run to store the start time of an operation and is supposed to fire at a frequence that could
be less then 1s but it is not predictable (it could take longer).
Anyone experienced the same?
It is normally?
Do you have some actions that i can try to make in order to identify a problem?
If possible i can provide some others information if required.
... sorry for my english ....