Wed Oct 8 12:07:36 PDT 2008
- Previous message: [Slony1-general] sanity check for all tables in a set
- Next message: [Slony1-general] sanity check for all tables in a set
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
no such column :). Here's the columns in pg_catalog.pg_class: relname | relnamespace | reltype | relowner | relam | relfilenode | reltablespace | relpages | reltuples | reltoastrelid | reltoastidxid | relhasindex | relisshared | relkind | relnatts | relchecks | reltriggers | relukeys | relfkeys | relrefs | relhasoids | relhaspkey | relhasrules | relhassubclass | relfrozenxid | relacl | reloptions the only one that seemed to really match with _slony.sl_table.tab_reloid was relfilenode. I have one table in my cluster that is not matching in that way, so I am wondering if it is hard and fast. The table seems to be replicating ok, but dunno what slony might puke out upon a move_set or something. Andrew Sullivan wrote: > On Wed, Oct 08, 2008 at 02:54:59PM -0400, Keisler Mark-QA4437 wrote: > >> so should _slony.sl_table.tab_reloid match >> pg_catalog.pg_class.relfilenode for each table in a replication set? >> > > pg_class.oid, I think. > > >> -----Original Message----- >> From: slony1-general-bounces at lists.slony.info >> [mailto:slony1-general-bounces at lists.slony.info] On Behalf Of Andrew >> Sullivan >> Sent: Thursday, October 02, 2008 10:35 AM >> To: slony1-general at lists.slony.info >> Subject: Re: [Slony1-general] sanity check for all tables in a set >> >> On Tue, Sep 30, 2008 at 02:27:08PM -0500, Mark Keisler wrote: >> >>> Someone deleted that table at some point and now I can't move the set >>> and I can't unsubscribe the set. It didn't seem like I could do >>> anything at this point besides manually strip out the cluster schema >>> and start over. So my first question is if there are any other >>> options at this point? >>> >> I don't think so. Re-educate your users not to drop things out from >> under you. No DDL! >> >> >>> Secondly, is there some sort of check that I can run periodically to >>> make sure a set is still intact so something like this doesn't bite me >>> >>> right when I need to move a set? >>> >> You can check the _slony.sl_tables and _slony.sl_sequence tables. >> >> A >> >> -- >> Andrew Sullivan >> ajs at commandprompt.com >> +1 503 667 4564 x104 >> http://www.commandprompt.com/ >> _______________________________________________ >> Slony1-general mailing list >> Slony1-general at lists.slony.info >> http://lists.slony.info/mailman/listinfo/slony1-general >> > > -- Mark Keisler Principal Software Engineer Motorola Open Source Technologies 630-329-2828
- Previous message: [Slony1-general] sanity check for all tables in a set
- Next message: [Slony1-general] sanity check for all tables in a set
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list