On 07/23/2013 12:52 PM, Tom Lane wrote:
> Craig Ringer writes:
>>> Showing that I'm still very much learning this area myself, a bit more
>>> looking around found:
>>> http://www.postgresql.org/docs/current/static/querytree.html
>>> which makes it clear that the range table for the query will cont
Craig Ringer writes:
>> Showing that I'm still very much learning this area myself, a bit more
>> looking around found:
>> http://www.postgresql.org/docs/current/static/querytree.html
>> which makes it clear that the range table for the query will contain
>> what you want. I suspect you'll need to
On 07/23/2013 11:41 AM, Craig Ringer wrote:
> On 07/23/2013 11:24 AM, Craig Ringer wrote:
>> On 07/21/2013 10:42 PM, Миша Тюрин wrote:
>>>
>>> hi, list, again. the next proposal into auto explain. one would be happy if
>>> could set list of target tables and indexes. sometimes it is very hard to
On 07/23/2013 11:24 AM, Craig Ringer wrote:
> On 07/21/2013 10:42 PM, Миша Тюрин wrote:
>>
>> hi, list, again. the next proposal into auto explain. one would be happy if
>> could set list of target tables and indexes. sometimes it is very hard to
>> detect who is using your indexes. but turn tota
On 07/21/2013 10:42 PM, Миша Тюрин wrote:
>
> hi, list, again. the next proposal into auto explain. one would be happy if
> could set list of target tables and indexes. sometimes it is very hard to
> detect who is using your indexes. but turn total logging on under thousands
> transactions per
hi, list, again. the next proposal into auto explain. one would be happy if
could set list of target tables and indexes. sometimes it is very hard to
detect who is using your indexes. but turn total logging on under thousands
transactions per seconds is not seems like nice idea couse size of re
