sql >> Database teknologi >  >> RDS >> PostgreSQL

En rå PostgreSQL-forespørgsel hænger, når den udføres med TypeOrm

Efter en fejlfindingssession fandt vi ud af, at forespørgslen blev låst, fordi en anden forbindelse forsøgte at opdatere en relateret ressource (en post i en users tabel med en fremmednøgle fra user_images_image ) for en anden transaktion i den samme metode, begge afventer, at dens resultater kan forpligtes.

Ved at bruge den samme forbindelse endte vi med den rigtige adfærd.

Det fandt vi ud af ved at bruge låseovervågningsforespørgslen fra dokumenterne :

SELECT blocked_locks.pid     AS blocked_pid,
         blocked_activity.usename  AS blocked_user,
         blocking_locks.pid     AS blocking_pid,
         blocking_activity.usename AS blocking_user,
         blocked_activity.query    AS blocked_statement,
         blocking_activity.query   AS current_statement_in_blocking_process,
         blocked_activity.application_name AS blocked_application,
         blocking_activity.application_name AS blocking_application
   FROM  pg_catalog.pg_locks         blocked_locks
    JOIN pg_catalog.pg_stat_activity blocked_activity  ON blocked_activity.pid = blocked_locks.pid
    JOIN pg_catalog.pg_locks         blocking_locks 
        ON blocking_locks.locktype = blocked_locks.locktype
        AND blocking_locks.DATABASE IS NOT DISTINCT FROM blocked_locks.DATABASE
        AND blocking_locks.relation IS NOT DISTINCT FROM blocked_locks.relation
        AND blocking_locks.page IS NOT DISTINCT FROM blocked_locks.page
        AND blocking_locks.tuple IS NOT DISTINCT FROM blocked_locks.tuple
        AND blocking_locks.virtualxid IS NOT DISTINCT FROM blocked_locks.virtualxid
        AND blocking_locks.transactionid IS NOT DISTINCT FROM blocked_locks.transactionid
        AND blocking_locks.classid IS NOT DISTINCT FROM blocked_locks.classid
        AND blocking_locks.objid IS NOT DISTINCT FROM blocked_locks.objid
        AND blocking_locks.objsubid IS NOT DISTINCT FROM blocked_locks.objsubid
        AND blocking_locks.pid != blocked_locks.pid
 
    JOIN pg_catalog.pg_stat_activity blocking_activity ON blocking_activity.pid = blocking_locks.pid
   WHERE NOT blocked_locks.GRANTED;



  1. Strengsammenkædning med en nul ser ud til at annullere hele strengen - er det den ønskede adfærd i Postgres?

  2. Bemærk brugere, der kører SQL Server 2008 og SQL Server 2008 R2

  3. PostgreSQL:Ufølsom streng sammenligning

  4. Hvordan lader man en bruger indsætte hvor som helst på en liste?