• 

  LOCK TABLE can harm your database's health - Cybertec

  

  cybertec-postgresql.com

  How LOCK TABLE Can Harm Your Database's Health — Frequent use of LOCK TABLE could harm your database when it conflicts with autovacuuming: “If you use LOCK on a table frequently, there is a good chance that autovacuum will never be able to successfully process that table.”

  autovacuum concurrency lock table bloat

  1

Appears in lists (1)

• Issue 296 - Don't let locking block Postgres's autovacuum

More like this (3)

• 

  Locks in PostgreSQL

  

  habr.com

  Locks in PostgreSQL A series about Postgres locks. This part is about dead lock, object-level locks...

  Locks in PostgreSQL A series about Postgres locks. This part is about dead lock, object-level locks and predicate locks.

  • Read

  
• 

  insert-only tables are autovacuumed in PostgreSQL v13 - Cybertec

  

  cybertec-postgresql.com

  Insert-Only Tables To Be Autovacuumed in Postgres 13 (But Why?) — Autovacuuming clears up dead tuples...

  Insert-Only Tables To Be Autovacuumed in Postgres 13 (But Why?) — Autovacuuming clears up dead tuples that are often left when updating or deleting data from tables, so why is autovacuuming for append-only tables a big deal in Postgres 13? Laurenz explains.

  • Read

  2
• Have An Eye On Locks Of PostgreSQL

  

  highgo.ca

  Have An Eye On Locks Of PostgreSQL The lock is an essential part of a database...

  Have An Eye On Locks Of PostgreSQL The lock is an essential part of a database system. In PostgreSQL, there are various locks, such as table lock, row lock, page lock, transaction lock, advisory lock, etc. Some of these locks are automatically added to complete the database functions during the operation of the database system, and some are manually added for the elements in PostgreSQL through some SQL commands.

  • Read