On Mon, 03 Nov 2008 11:04:45 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> Ivan Sergio Borgonovo <[EMAIL PROTECTED]> writes:
> > maintenance_work_mem is still untouched. What would be a good
> > value to start from?
> GIN index build time is *very* sensitive to maintenance_work_mem.
> Try cranking
Ivan Sergio Borgonovo <[EMAIL PROTECTED]> writes:
> maintenance_work_mem is still untouched. What would be a good value
> to start from?
GIN index build time is *very* sensitive to maintenance_work_mem.
Try cranking it up to a couple hundred megabytes and see if that
helps.
Also, if you're on 8.2
On Mon, 3 Nov 2008, Ivan Sergio Borgonovo wrote:
I'm looking for a bit more guidance on gin index creation.
The process:
- vaccum analyze.
- start a transaction that:
- drop the triggers to update a tsvector
- drop the index on the tsvector
- fill several tables
- update the tsvector in a table
On Mon, 3 Nov 2008 16:45:35 +0100
Ivan Sergio Borgonovo <[EMAIL PROTECTED]> wrote:
Forgot to add that top say postgresql is using 100% CPU and 15%
memory.
> I'm looking for a bit more guidance on gin index creation.
>
> The process:
> - vaccum analyze.
> - start a transaction that:
> - drop the
I'm looking for a bit more guidance on gin index creation.
The process:
- vaccum analyze.
- start a transaction that:
- drop the triggers to update a tsvector
- drop the index on the tsvector
- fill several tables
- update the tsvector in a table with ~800K records
- recreate the gin index
- commi
