From: | Zoltan Boszormenyi <zboszor(at)dunaweb(dot)hu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Is there a way to run heap_insert() AFTER ExecInsertIndexTuples() ? |
Date: | 2007-03-01 13:50:30 |
Message-ID: | 45E6DA26.6030309@dunaweb.hu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Zoltan Boszormenyi írta:
>> The cost I am thinking now is an extra heap_update()
>> after heap_insert() without generating the identity value
>> and inserting index tuples to indexes that doesn't
>> contain the identity column.
>
> And as far as I tested the current state, there is no cost
> if you don't use GENERATED or IDENTITY.
> The extra heap_update() would be performed only
> if you have an IDENTITY colum.
The modification I imagined is actually working:
- skip indexes using the identity columns
- do a simple_heap_update() after all other columns are
assigned and index tuples are inserted
- do ExecInsertIndexTuples() on indexes referencing
the IDENTITY column
However, I get warning messages like:
WARNING: detected write past chunk end in ExecutorState 0xaaff68
How can I prevent them?
Best regards,
Zoltán Böszörményi
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-03-01 13:51:43 | Re: COMMIT NOWAIT Performance Option |
Previous Message | Magnus Hagander | 2007-03-01 13:50:10 | Re: [HACKERS] urgent: upgraded to 8.2, getting kernel panics |