* Hugh Williams
>
> Both log_enable 2 & 3, enable row by row auto commit which avoid deadlocks, 2
> then has transaction logging disabled and 3 has logging enabled so I don’t
> see how you are expecting both approaches to be combined ? It is the row y
> row auto-commit that makes both approac
Hi Lars,
Both log_enable 2 & 3, enable row by row auto commit which avoid deadlocks, 2
then has transaction logging disabled and 3 has logging enabled so I don’t see
how you are expecting both approaches to be combined ? It is the row y row
auto-commit that makes both approaches slower than if
* Hugh Williams
>
> When renaming, deleting or performing other such operations on Large graphs
> the key is to set “log_enable(3.1)” before hand such that the operation runs
> in row-autocommit mode avoiding a transaction being created in memory that
> consumes it all for large graphs, as de
Hi
When renaming, deleting or performing other such operations on Large graphs the
key is to set “log_enable(3.1)” before hand such that the operation runs in
row-autocommit mode avoiding a transaction being created in memory that
consumes it all for large graphs, as detailed at:
htt
Hi,
I experienced the same for big graphs. Not only for renaming, but also
for deletion. In my experience it helped to not use the GUI, but the
iSQL shell.
I never tried it for renaming, only for deletion, but perhaps this helps
you too. This would be the code:
UPDATE DB.DBA.RDF_QUAD TABLE O
Hi there,
I'm using a Virtuoso OS 06.01.3127 running on linux. If I try to
rename a graph from conductor the only
result I get is a complete crash of the instance resulting a in a
termination of the virtuoso-t process.
any idea on how fix/work around this?
all the best,
--
Davide Palmisano
ht
