Thanks Kevin, greatly appreciated. I think i'll make a lot of use of this...
Andy
===
I know, it looks complicated, but in a production system, this will be
fast with minimal downtime (only during the final locking swap).
Cheers,
Kevin
___
On 10/21/2010 7:24 AM, lplateandy wrote:
The doc says "It also takes an exclusive lock on the specific index being
processed, which will block reads that attempt to use that index."
Does that mean that i'm not really any better off as the spatial index is
really the critical means controlling th
On 21 October 2010 07:24, lplateandy wrote:
>
> Hi Mike,
>
> OK - that's really useful. Does that only work for 9 or does it just happen
> you're pointing to the 9 document?
>
> The doc says "It also takes an exclusive lock on the specific index being
> processed, which will block reads that attem
Hi Mike,
OK - that's really useful. Does that only work for 9 or does it just happen
you're pointing to the 9 document?
The doc says "It also takes an exclusive lock on the specific index being
processed, which will block reads that attempt to use that index."
Does that mean that i'm not really
On 21 October 2010 04:38, lplateandy wrote:
> Of course, even better would be a way to reindex whilst a database is in use
> but i'm under the impression that this is not possible at the moment?
If you DROP/CREATE your index then reads are blocked. But if you use
REINDEX then only writes are bloc
Hi,
I realise this is probably a very basic question but if anyone could point
me in the right direction i'd be very grateful.
I have a database which is just my data table and "geometry columns" and
"spatial_ref_sys" tables.
The data is of a significant volume with periodic updates which take
