On 20 April 2014 02:21, Torsten Wrote:
> Hi,
>
> an index can be INVALID (pg_index.indisvalid=false).
>
> I want to temporarily disable an index so that it won't be used to
> access data but will still be updated.
>
> Can I simply set pg_index.indisvalid=false and later turn it true again?
I
On Apr 20, 2014 4:21 AM, "Torsten Förtsch" wrote:
>
> On 20/04/14 12:08, Thomas Kellerer wrote:
> >> Example:
> >>
> >> btree (fmb_id, action_type)
> >> btree (fmb_id)
> >>
> [...]
> >
> > Btw: in the above example the second one is definitely not needed.
> > Any query that uses the seco
On 20/04/14 12:08, Thomas Kellerer wrote:
>> Example:
>>
>> btree (fmb_id, action_type)
>> btree (fmb_id)
>>
[...]
>
> Btw: in the above example the second one is definitely not needed.
> Any query that uses the second one (single column) can also use the
> first one.
I know.
But the s
Torsten Förtsch wrote on 20.04.2014 10:09:
The problem is I have a number of indexes in a large system that are
very similar. And I suspect some of them are superfluous.
Example:
btree (fmb_id, action_type)
btree (fmb_id)
Action_type in this case is one out of a handful of values (sh
On 20/04/14 20:09, Torsten Förtsch wrote:
On 20/04/14 03:02, Sergey Konoplev wrote:
Thanks for you reply.
an index can be INVALID (pg_index.indisvalid=false).
I want to temporarily disable an index so that it won't be used to
access data but will still be updated.
Can I simply set pg_index.i
On 20/04/14 03:02, Sergey Konoplev wrote:
Thanks for you reply.
>> an index can be INVALID (pg_index.indisvalid=false).
>>
>> I want to temporarily disable an index so that it won't be used to
>> access data but will still be updated.
>>
>> Can I simply set pg_index.indisvalid=false and later tur
On Apr 19, 2014 1:53 PM, "Torsten Förtsch" wrote:
>
> Hi,
>
> an index can be INVALID (pg_index.indisvalid=false).
>
> I want to temporarily disable an index so that it won't be used to
> access data but will still be updated.
>
> Can I simply set pg_index.indisvalid=false and later turn it true a
