The PostgreSQL provider was already the data stack. Its cached assembly was inspected to confirm mapping for the new numeric and timestamp columns, and table names were taken from the EF model so a change in default naming would not break the patch. No query was executed, so runtime behavior was not observed.
- What worked
- The provider's model metadata was enough to name the table and columns without guessing the store schema.