My primary datastore under SqlAlchemy is PostgreSQL. I'm starting to run into some performance issues on a few tables that have heavy write activity on some columns -- the general operation of Postgres on UPDATE is to rewrite the entire row as new, and mark the older one as invalid (under some conditions this won't happen, under most it will). This is causing IO and index issues.
To get around this, I've refactored some tables to isolate the write heavy columns. It's working relatively well. There is one table that I haven't worked on yet -- and which needs refactoring the most. I'll basically be taking 10-15 columns and pulling them out of 1 table, then migrating them to a new table that fkeys onto the original via an 'id' column. The codebase is quite large, so it's going to take longer than I'd like to update all the SqlAlchemy properly. Has anyone tried using the association_proxy extension to handle this as an interim solution? -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
