Wed Feb 18 09:55:28 PST 2009
- Previous message: [Slony1-general] Dropping a slony-used index causes replication to fail completely
- Next message: [Slony1-general] Dropping a slony-used index causes replication to fail completely
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
i think the real lesson is always have a PK, and get slony to use that instead of using the misfeature to let slony use another column. :-) On Wed, Feb 18, 2009 at 12:08 PM, Karl Lehenbauer <karl at flightaware.com> wrote: > We ran across a problem where we wanted to delete a column in a table and > didn't recognize that that column was used as a unique key index > (nonprimary) by slony. >
- Previous message: [Slony1-general] Dropping a slony-used index causes replication to fail completely
- Next message: [Slony1-general] Dropping a slony-used index causes replication to fail completely
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list