Did16 wrote
> Hi
> The SQL is not executed from a trigger.
> Here is an extract of my log file :
>>>
>
> 2019-03-01 14:53:37 CET [24803]: [129-1] [3686]
> user=pgbd_preint_sg2,db=pgbd_preint_sg2 LOG: process 24803 still waiting
> for ShareLock on transaction 3711 after 1000.476 ms
>
> 2019-03-01 14:53:37 CET [24803]: [130-1] [3686]
> user=pgbd_preint_sg2,db=pgbd_preint_sg2 DETAIL: Process holding the lock:
> 24786. Wait queue: 24803.
>
> 2019-03-01 14:53:37 CET [24803]: [131-1] [3686]
> user=pgbd_preint_sg2,db=pgbd_preint_sg2 CONTEXT: while rechecking updated
> tuple (3,33) in relation "t_shared_liste_valeurs"
>
> 2019-03-01 14:53:37 CET [24803]: [132-1] [3686]
> user=pgbd_preint_sg2,db=pgbd_preint_sg2 STATEMENT: update
> t_shared_liste_valeurs set deletion_date=$1, deletion_login=$2,
> modification_date=$3, modification_login=$4, administrable=$5, libelle=$6,
> niveau=$7 where code=$8
>
> <<
>
> After a fresh db restart, the result is the same : no content of Bind
> variables in the log file.
>
> Best Regards
>
> Didier ROS
> Expertise SGBD
> EDF - DTEO - DSIT - IT DMA
> Département Solutions Groupe
> Groupe Performance Applicative
> 32 avenue Pablo Picasso
> 92000 NANTERRE
OK, In case of a trigger or any pl/pgsql program I would have tryed to write
the content of bind variables using RAISE command or someting similar before
executing the UPDATE command.
But your log is now much more explicit: you where waiting on a LOCK ...
Regards
PAscal
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html