On Sep 23, 2012, at 6:32 PM, Tomasz Pala <[email protected]> wrote: > On Sun, Sep 23, 2012 at 18:17:38 -0400, Jeffrey Johnson wrote: > >>> Try running replicated postgresql master node on failing drive and share >>> your results! >> >> Why? > > Just try it. >
Pay me $100/hour and I will. >> The issue(s) involved with maintaining databases >> consistently with package manager upgrades are non-trivial >> to solve with a perl script like yours. > > My script does (well, should - it was 1-minute typing and might be > error-prone) exactly what shall be done. It doesn't alter any > database more than every other legitimate invocation, as it doesn't use > any hacks except reversing order of transactions performed. > In term of databases it's not rollback - but contrary to RDBMSes here this > doesn't matter; primary difference is that standalone database has > strictly specified and controlled I/O vectors, while rpm in properly > used system cannot track data, but metadata only; in *sql it's not normal > usage-scenario when someone replaces blob using filesystem tools, so the > assumption of data consistency is solid. > *sigh* You are so busy trolling me that you haven't bothered to look at what is implemented in RPM. For starters: 1) rpm-5.3.x+ embeds sqlite3 so that databases imports/exports are integrated with package management. There is no reason why postgresql cannot be implemented the same way, just that sqlite3 is a simpler API if/when attempting an embedding. 2) TPPM *uses* Berkeley DB ACID logs to extend to file system and scriptlet operations. Uts incoherent/inconsistent (and ignorant) to challeng me to upgrade a postgresql master server with packaging at the dame time you are claiming that a perl 1-liner is an adequate replacement for --rollback. >> So write a perl sc riot that permits upgrading postgresql >> masters now that you have solved --rollback with one line of perl. > > I ain't solved --rollback, just replaced it with something usable. > Good: You are still an ignorant troll. 73 de Jeff > -- > Tomasz Pala <[email protected]> > _______________________________________________ > pld-devel-en mailing list > [email protected] > http://lists.pld-linux.org/mailman/listinfo/pld-devel-en _______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
