Re: Triggers and locks

Newsgroups	comp.databases.ingres
Date	2023-09-12 07:41 -0700
References	<757cd439-a568-4385-ad7e-b1bb6bf12a97n@googlegroups.com> <udpevj$1h2jo$1@dont-email.me>
Message-ID	<950fbce7-29e4-4990-bdfd-4c919f3d12e2n@googlegroups.com> (permalink)
Subject	Re: Triggers and locks
From	G Jones <geraint.jones@ndph.ox.ac.uk>

Show all headers | View raw

Perhaps partitioning the 'spider' table would help, so your concurrent rule-fired inserts are acting on multiple physical tables rather than just one.
(It's a less effective approach if spider has secondary indexes though, those can't be partitioned so a single index spans all partitions of the base table).

Back to comp.databases.ingres | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Triggers and locks Fabrizio Di Renzo <fabrizio.direnzo@bucap.it> - 2023-09-12 02:40 -0700
  Re: Triggers and locks Roy Hann <specially@processed.almost.meat> - 2023-09-12 10:36 +0000
    Re: Triggers and locks G Jones <geraint.jones@ndph.ox.ac.uk> - 2023-09-12 07:41 -0700
  Re: Triggers and locks Paul White <shift7solutions@gmail.com> - 2023-09-12 22:03 -0700
    Re: Triggers and locks Fabrizio Di Renzo <fabrizio.direnzo@bucap.it> - 2023-09-12 23:53 -0700
      Re: Triggers and locks Roy Hann <specially@processed.almost.meat> - 2023-09-13 08:54 +0000

csiph-web