I don't remember, to be honest. ALTER TABLE ... VALIDATE CONSTRAINT was
really fast, though.
Having a supporting index (which Pg does
not automatically create) is vital, of course.
On 5/25/23 23:16, Sengottaiyan T wrote:
Thanks Ron.
While enabling the constraint (valid constraint) after initial data import, will it scan all the table data or the validation will happen for new rows inserted after that point)?
If I read your email correctly, I see two options
- Apply FK constraints *after* initial data load.
- Load parent data before child data
(You can create the FKs ahead of time, but use the NOT VALID clause; then, after data is loaded do ALTER TABLE ... VALIDATE CONSTRAINT.)
On 5/25/23 06:30, Sengottaiyan T wrote:
Is there an option to set novalidate constraints in postgres? In my source Sybase DB, table structures are not defined properly (only primary keys exist and no foreign key) - I'm making necessary changes on target Postgres DB (created tables, identifying relationship between table columns with respective team). After creating proper structure on target, the next step is to load data - I'm sure there will be a lot of errors during initial data load (no parent record found). How to handle it?
Team,
Need some help regarding Open Source tools for DB migration (from SYBASE to PostgreSQL) with real time CDC. Along with this, is there any possibility to migrate other objects (like Triggers, Stored Procedures and Functions) to PostgreSQL?
Thanks,
Senko
--
Born in Arizona, moved to Babylonia.
--
Born in Arizona, moved to Babylonia.
