1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
2
Can you:
- Verify that the VACUUM command is executing successfully after each MERGE operation?
- Verify that it's actually deleting old snapshots and associated data files?
- Look at the size and nature of the updates you're making every hour? If each update is adding a significant amount of data, this could contribute to the rapid growth of the table.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
Thank you very much for your suggestion.
SELECT * FROM "my_table$snapshots
query returns a single row with following content.SELECT * FROM "my_table$files";
returns 308 rows. Unfortunately I don't know how to check if any of this files associated with an old snapshot.Could you verify if versioning is enabled on your bucket? If so, this might be contributing to the increase in size. You can check more about Versioning workflows.
Bucket Versioning is disabled.