Dear Mr Alexander,
I was checking the archives today and to my shock, I did not find my
reply to your previous question which was almost two weeks ago.
I apologise for the inconvenience, I have however replied within an
hour but apparently, it did not go through.
On Thu, Apr 6, 2017 at 4:18 PM, Mark Rofail <markm.rof...@gmail.com> wrote:
> Hello Mr Alexander,
> From my understanding, the main issue occurs whenever any UPDATE or
> DELETE statement is executed on the PK table,
> this triggers a referential integrity check on the FK table. In the
> previous patches, this was done by performing a sequential scan.
> To improve performance I propose that we index the FK column, and in
> my point of view the most suitable index would be the GIN index since
> it is targeted for composite items.
> However, to move forward with this approach, we have to be sure that
> the comparison semantics offered by GIN indexes satisfy our needs for
> the referential integrity check.
> This approach was proposed by Tom Lane:
> I believe this can be accomplished by better understanding the GIN
> index implementation in postgreSQL, including its operators.
> This is the best to the knowledge I gained during the application
> period. I would like to investigate it further and would be delighted
> to hear your input regarding the matter,
> Best Regards,
> Mark Moheb
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: