On 02/04/2012 01:52, Martin Gregorie wrote:
> BTW, why use document_chunks when a text field can hold megabytes,
> especially if they will be concatenated to form a complete document
> which is then edited as a whole item and before being split into chunks
> and saved back to the database?
... b
Correction interpolated - see below
On Mon, 2012-04-02 at 00:22 +0100, Martin Gregorie wrote:
> On Mon, 2012-04-02 at 00:38 +0200, Ivan Voras wrote:
> > Hi,
> >
> > I have documents which are divided into chunks, so that the (ordered)
> > concatenation of chunks make the whole document. Each of t
On Mon, 2012-04-02 at 00:38 +0200, Ivan Voras wrote:
> Hi,
>
> I have documents which are divided into chunks, so that the (ordered)
> concatenation of chunks make the whole document. Each of the chunks may
> be edited separately and past versions of the chunks need to be kept.
>
> The structure
2012/4/2 Ondrej Ivanič :
> Hi,
>
> On 2 April 2012 08:38, Ivan Voras wrote:
>> db=> set enable_seqscan to off;
>
>
>
>>
>> This huge cost of 100 which appeared out of nowhere in the
>> EXPLAIN output and the seq scan worry me - where did that come from?
>
> It is not possible to disable s
Hi,
On 2 April 2012 08:38, Ivan Voras wrote:
> db=> set enable_seqscan to off;
>
> This huge cost of 100 which appeared out of nowhere in the
> EXPLAIN output and the seq scan worry me - where did that come from?
It is not possible to disable seq scan completely. The "enable_seqscan
