Sat Jun 22 15:10:39 PDT 2013
- Previous message: [Slony1-general] Slony replication has stopped replicating
- Next message: [Slony1-general] Slony replication has stopped replicating
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Jun 22, 2013 at 2:27 PM, Jan Wieck <JanWieck at yahoo.com> wrote: > On 06/22/13 16:56, Bambi Bellows wrote: >> LOL. Thanks Jan. No, I inherited these systems, and upgrading is not really an option for the database... I am, however, trying to find where the log files are. They aren't in the /opt/logs/postgres directory, and they aren't in the postgres logs directory. I have two sudo finds running, but, so far, no luck. Gotta say, haven't been having the best of luck so far on anything slony-related. > > Slony related? > > I would say the whole thing you inherited is a complete mess and Slony > is a casualty of that. There is nothing so far that I can see could be > blamed on Slony. Only a grossly outdated and unmanaged server setup. > > Sorry to be so blunt, but I just don't tolerate it when Slony or > PostgreSQL are blamed for server admin negligence and incompetence. > > This is apparently not your fault, but your predecessor's fault. So > don't take it personal. Yeah when I'm handed a grand mess like this I just tell the bosses you can either let me fix it the way it needs to be fixed, or watch it break over and over. Your choice, but I'm not getting up at 2am to fix things you didn't let me fix right.
- Previous message: [Slony1-general] Slony replication has stopped replicating
- Next message: [Slony1-general] Slony replication has stopped replicating
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list