![]() ![]() Hi enelson, thanks for posting in the Lucid community! Apologies for the frustration you've experienced, and thanks for sharing the details surrounding your use case and what you've tried so far. Manually updating a diagram just lets human errors creep in over time. I want to find an automated way to load the index info into a diagram so that I have a diagram that I can trust, and that my team can trust. Ideally, this would be done on the ERD diagram, but if the index information for all the tables could be displayed in any other kind of diagram, please tell me how. However, I am looking for another way to display the index information for each table. I've gone so far as to reverse engineer the format of the data in the import file. I have read the information about importing data from a database several times - and it does not mention anything about including a table's index information on the ERD diagram. If that is going to be your response, then be warned that it is not a helpful response. Yes, I know that index info is not usually part of an ERD diagram. Now I want to add index info to the ERD diagram. After 4 months of intermittent effort, the diagram is readable. The result was an accurate but unusable because of all the overlapping lines showing the FK relationships among the tables. This means that after a volume is created from a snapshot, there is no need to wait for all of the data to transfer from Amazon S3 to your EBS volume before your attached instance can start accessing the volume and all its data.I used LucidChart's ability to import data from my PostGres database into LucidChart to create an ERD diagram. New volumes created from existing EBS snapshots load lazily in the background. So, in summary, RDS snapshot restore will have a performance lull after a fresh restore. Then I ran the create index and it finished blazing fast. In my case, I just did whole table select for the offending table to sort of "pre-pull" the data from the initial restore. I had never hit this issue before, but I've never needed to work with such a large set of data right after a restore before. Apparently it's normal for the instance to be slow after a fresh restore. Timings were gathered after an RDS snapshot restore. I've checked max_parallel and experimented with things like ALTER TABLE email_records SET (parallel_workers = #) but nothing seems to make a difference. The dev hosts are restored with a fresh clone of prod db nightly, so there is no discrepancy in the number of rows. ![]() ![]() I've checked all the normal stuff: CPU load (plenty free in all cases), Memory (plenty free in all cases). On the RDS host: db=> CREATE INDEX idx_email_records_created ON email_records(created_at) On the local linux dev box: db=> CREATE INDEX idx_email_records_created ON email_records(created_at) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |