Tag Info

New answers tagged

1

Is the autovac "to prevent wraparound" (as reported in pg_stat_activity)? If so, PostgreSQL considers that an emergency and refuses to yield the lock. Which is rather unfortunate in this case, as once you drop the table the situation will be resolved. But it doesn't know why you want the lock.


0

If no delete or update happened, autovacuum shouldn't process the table, per autovacuum_analyze_threshold. See Automatic Vacuuming for the relevant configuration parameters. You may set log_autovacuum_min_duration to zero to help figure out what's being autovacuumed. In any case, it is possible to completely disable autovacuum for a particular table, with: ...


0

If You use Linux you should list processes with ps aux and find Autovacuum process. Then just kill it(autovacuum should be working as another process if it's turned on).


12

The behaviour did change between SQL Server 2008 R2 and SQL Server 2012. The 2008 R2 implementation was inconsistent with the documented 'relaxed FIFO' semantics: Locks are granted in a relaxed first-in, first-out (FIFO) fashion. Although the order is not strict FIFO, it preserves desirable properties such as avoiding starvation and works to reduce ...


0

The whole point of snapshot is to provide a point in time copy of the articles involved in replication. It does it when generating the snapshot files from the publisher by locking the tables until the snapshot is finished for that particular article. You should plan to reinitialize during less activity time of your server. Is there anyway to do this ...


1

From the MySQL Documentation The type of read varies for selects in clauses like INSERT INTO ... SELECT, UPDATE ... (SELECT), and CREATE TABLE ... SELECT that do not specify FOR UPDATE or LOCK IN SHARE MODE: By default, InnoDB uses stronger locks and the SELECT part acts like READ COMMITTED, where each consistent read, even within the same ...


0

Thanks to jynus for advising on working with general log, the problem has been solved! As in most of the cases, the error was quite simple, here is the description: On certain occasions, a function was invoked, that performed the following: Lock several tables in the DB Do its queries Send a message to chat with the results Unlock tables The message to ...



Top 50 recent answers are included