-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ECP-8691] Excessive Database Usage in adyen_payment_response & sales_order_payment #2578
Comments
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, |
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 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 |
Is there any update on this task? |
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
The text was updated successfully, but these errors were encountered: