[ECP-8691] Excessive Database Usage in adyen_payment_response & sales_order_payment

[SamJUK]

Hi, doing some store maintenance, we've identified the adyen_payment_response & sales_order_payment tables are taking up over 40% of the used DB space.
With the order payment table, Adyen orders seem to have an excessive additional_information payload in comparison to other gateways.

Is there any configuration / documented processes that will help reduce this?

Thanks
Sam

[candemiralp]

Hello @SamJUK,

Thank you for raising this issue. We already have an investigation ticket about this issue. I've linked the ticket to your Github issue. Once we've completed the investigation, you will be informed.

Best regards,
Can

[karmdip-magneto]

Hello @candemiralp,

We're also facing the same issue in our project. I was wondering will it be okay to delete the old records from the table adyen_payment_response if these records are not being used anywhere and just logging the response?

I can see the data from the table is being used in some cases such as at the success page showing the button to complete the payment, etc. I haven't reviewed the whole extension but can you please let me know what is the actual purpose of this table in Magento 2, and do we need to keep the adyen_payment_response table records for the orders that are already completed?