Thu May 26 12:03:16 PDT 2016
- Previous message: [Slony1-general] removing old slony triggers
- Next message: [Slony1-general] Slony with postgresql replication?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
You have to go through each table and drop all of the slony triggers Dave Cramer On 26 May 2016 at 15:01, Mike James <mike.james at clutch.com> wrote: > I was trying to delete the unused slony replication cluster and of course, > it hung up and I ended up blocking our prod db for a bit. Still coming down > from that one. What would the manual removal look like (pls remember I'm > not a PG dba)? > > thanks > > > > [image: Clutch Holdings, LLC] <http://www.clutch.com> Mike James | > Manager of Infrastructure > 267.419.6400, ext 204 | mike.james at clutch.com > 201 S Maple St. | Suite 250 | Ambler, PA 19002 > Clutch.com <http://www.clutch.com> | Twitter > <https://twitter.com/clutchsuccess> | LinkedIn > <https://www.linkedin.com/company/2837209> | YouTube > <https://www.youtube.com/user/clutchsuccess> | Clutch Support Center > <http://clientsupport.clutch.com/> > > The only end to end consumer management platform that empowers > consumer-focused businesses to identify, target, message, and engage their > best customers. > > On Thu, May 26, 2016 at 11:17 AM, Dave Cramer <davecramer at gmail.com> > wrote: > >> Yes, safe to drop the schema. Although I have had instances where it >> won't drop cleanly. In which case you will have to do it manually >> >> Dave Cramer >> >> On 26 May 2016 at 11:15, Mike James <mike.james at clutch.com> wrote: >> >>> I attached to the db with pgAdmin and when I tried to open the slony >>> replication object I got this popup message >>> >>> ERROR: relation "_clients_report_orig.sl_nodelock" does not exist >>> LINE 1: SELECT nl_backendpid FROM _clients_report_orig.sl_nod... >>> >>> Is it safe to go ahead and delete this unused cluster object? >>> >>> >>> >>> [image: Clutch Holdings, LLC] <http://www.clutch.com> Mike James | >>> Manager of Infrastructure >>> 267.419.6400, ext 204 | mike.james at clutch.com >>> 201 S Maple St. | Suite 250 | Ambler, PA 19002 >>> Clutch.com <http://www.clutch.com> | Twitter >>> <https://twitter.com/clutchsuccess> | LinkedIn >>> <https://www.linkedin.com/company/2837209> | YouTube >>> <https://www.youtube.com/user/clutchsuccess> | Clutch Support Center >>> <http://clientsupport.clutch.com/> >>> >>> The only end to end consumer management platform that empowers >>> consumer-focused businesses to identify, target, message, and engage their >>> best customers. >>> >>> On Thu, May 19, 2016 at 3:43 PM, Steve Singer <steve at ssinger.info> >>> wrote: >>> >>>> On 05/19/2016 03:26 PM, Mike James wrote: >>>> >>>>> Hi, Steve. I believe all of the triggers / schema were created with >>>>> slony 2.2.1. Also we're currently on postgresql 9.3.5. >>>>> >>>>> >>>> I think you should be able to just drop the other slony schema's with >>>> cascade and it should clean everything up. >>>> >>>> >>>> >>>> Mike >>>>> >>>>> Clutch Holdings, LLC <http://www.clutch.com> Mike James | >>>>> Manager of >>>>> Infrastructure >>>>> 267.419.6400, ext 204 | mike.james at clutch.com <mailto: >>>>> mike.james at clutch.com> >>>>> 201 S Maple St. | Suite 250 | Ambler, PA 19002 >>>>> Clutch.com <http://www.clutch.com> | Twitter >>>>> <https://twitter.com/clutchsuccess> | LinkedIn >>>>> <https://www.linkedin.com/company/2837209> | YouTube >>>>> <https://www.youtube.com/user/clutchsuccess> | Clutch Support Center >>>>> <http://clientsupport.clutch.com/> >>>>> >>>>> The only end to end consumer management platform that empowers >>>>> consumer-focused businesses to identify, target, message, and engage >>>>> their best customers. >>>>> >>>>> >>>>> On Thu, May 19, 2016 at 2:27 PM, Steve Singer <steve at ssinger.info >>>>> <mailto:steve at ssinger.info>> wrote: >>>>> >>>>> On 05/17/2016 02:59 PM, Mike James wrote: >>>>> >>>>> Hi, all. Due to some changes in our slony schema over the >>>>> years, >>>>> in our >>>>> database I now see three slony schemas. Our current replication >>>>> set only >>>>> uses the most recent one. (slony 2.2.1 and PG 9.3) >>>>> >>>>> In the database when I "select * from pg_trigger; " I see some >>>>> triggers >>>>> from the older, unused schemas, particularly _logtrigger, >>>>> _truncatetrigger have tgenabled = O. >>>>> >>>>> _denyaccess and _truncatedeny are disabled (tgenabled = D) >>>>> >>>>> How do I safely remove these triggers and delete the unused >>>>> slony >>>>> schemas? This maybe a simple question - but I'd rather not >>>>> take the >>>>> chance with the production database. Thanks, >>>>> >>>>> >>>>> What version of slony is are the old schema's based on? >>>>> Depending on the version this makes a difference on how you would >>>>> remove them. >>>>> >>>>> Steve >>>>> >>>>> >>>>> >>>>> Mike >>>>> Clutch Holdings, LLC <http://www.clutch.com> Mike >>>>> James | Manager of >>>>> Infrastructure >>>>> 267.419.6400, ext 204 <tel:267.419.6400%2C%20ext%20204> | >>>>> mike.james at clutch.com <mailto:mike.james at clutch.com> >>>>> <mailto:mike.james at clutch.com <mailto:mike.james at clutch.com>> >>>>> 201 S Maple St. | Suite 250 | Ambler, PA 19002 >>>>> Clutch.com <http://www.clutch.com> | Twitter >>>>> <https://twitter.com/clutchsuccess> | LinkedIn >>>>> <https://www.linkedin.com/company/2837209> | YouTube >>>>> <https://www.youtube.com/user/clutchsuccess> | Clutch Support >>>>> Center >>>>> <http://clientsupport.clutch.com/> >>>>> >>>>> The only end to end consumer management platform that empowers >>>>> consumer-focused businesses to identify, target, message, and >>>>> engage >>>>> their best customers. >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Slony1-general mailing list >>>>> Slony1-general at lists.slony.info >>>>> <mailto:Slony1-general at lists.slony.info> >>>>> http://lists.slony.info/mailman/listinfo/slony1-general >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Slony1-general mailing list >>>>> Slony1-general at lists.slony.info >>>>> http://lists.slony.info/mailman/listinfo/slony1-general >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Slony1-general mailing list >>> Slony1-general at lists.slony.info >>> http://lists.slony.info/mailman/listinfo/slony1-general >>> >>> >> > > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20160526/b6cb2201/attachment-0001.htm
- Previous message: [Slony1-general] removing old slony triggers
- Next message: [Slony1-general] Slony with postgresql replication?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list