On 02/24/2018 12:27 AM, l...@laurent-hasson.com wrote:
> Hello
>
>
>
> I work with a large and wide table (about 300 million rows, about 50
> columns), and from time to time, we get business requirements to make
> some modifications. But sometimes, it’s just some plain mistake. This
> has happe
Dave Cramer writes:
> Have a query:
> explain analyze SELECT minion_id FROM mob_player_mob_118 WHERE player_id =
> 55351078;
> Index Only Scan using mob_player_mob_118_pkey on mob_player_mob_118
> (cost=0.44..117887.06 rows=4623076 width=4) (actual time=0.062..3716.105
> rows=4625123 loops=1)
I
Have a query:
explain analyze SELECT minion_id FROM mob_player_mob_118 WHERE player_id =
55351078;
QUERY PLAN
-
Index Only Scan usi
2018-03-02 15:29 GMT+01:00 Pavel Stehule :
>
>
> 2018-03-02 14:49 GMT+01:00 Nandakumar M :
>
>> Hi,
>>
>> https://heapanalytics.com/blog/engineering/running-10-millio
>> n-postgresql-indexes-in-production
>>
>> From the link shared above, it looks like what Meenatchi has done should
>> work.
>>
>
2018-03-02 14:49 GMT+01:00 Nandakumar M :
> Hi,
>
> https://heapanalytics.com/blog/engineering/running-10-
> million-postgresql-indexes-in-production
>
> From the link shared above, it looks like what Meenatchi has done should
> work.
>
It can be different situation, there are not specified index
Hi,
https://heapanalytics.com/blog/engineering/running-10-million-postgresql-indexes-in-production
>From the link shared above, it looks like what Meenatchi has done should work.
Do the conditions on the partial index and query match exactly? (
greater than / greater than equals mismatch maybe?)
