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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Amazon Aurora PostgreSQL support (required changes provided) #1791
Comments
Hey @gaplo917. Thanks for the issue submission. At the moment, we mostly run in GCP (we're agnostic on most areas, but there are a few ties to GCP). That said, we want to move the codebase in a modular place where you could have your own implementation of of each component (in this case, you could write your own snapshotter from scratch and just inject it at compile time). For the moment, it's unlikely that we'll support other infrastructure, but we will open the capabilities for anyone to build on top in the near future. |
thankss |
@EmilLuta Thank you for the prompt reply. The modular structure sounds promising and I can imagine that it's a huge chunk of workload that will take time. Would you mind if I leave this FR open, so if others encounter the same issue, they are able to find it in the issues list? |
I believe it's discoverable even as closed, but let's keep it open as it's not been addressed. Thanks @gaplo917! |
good nice work |
lfg |
馃専 Feature Request
Support Amazon Aurora PostgreSQL (Standards and Serverless V2) on AWS.
馃摑 Description
Aurora PostgreSQL usually is a drop-in replacement for PostgreSQL but unfortunately not in this case. When I tried to initial the stack, it fails
After deep dive into the source code, I found the following codes that check replication lag
https://github.com/matter-labs/zksync-era/blob/main/core/lib/dal/src/system_dal.rs#L20-L39
Aurora PostgreSQL use underlying architecture that does not use WAL to do replication. It doesn't have the
pg_last_wal_receive_lsn
,pg_last_wal_replay_lsn
,pg_last_xact_replay_timestamp
pg functions. Thus, it throwsSQLSTATE 0A000 feature_not_supported
exception.I think there are two potential options to support Aurora PostgreSQL and I could provide the PR once the community come into agreement.
Option 1.
Add a new feature flag and using conditional statement to switch the replication lag query
Option 2.
Automatically handle fallback case using pg function. Create a sql file to create the function automatcially before checking the replication lag,
modify the codes https://github.com/matter-labs/zksync-era/blob/main/core/lib/dal/src/system_dal.rs#L28-L34 to
馃 Rationale
Aurora PostgreSQL provides serverless infrastructure that able to near-instant autoscale vertically on compute, memory, and IOPS.
The text was updated successfully, but these errors were encountered: