On Wed, Apr 14, 2010 at 9:16 AM, Jaime Casanova <jcasa...@systemguards.com.ec> wrote: > On Sat, Apr 10, 2010 at 12:23 AM, Jaime Casanova > <jcasa...@systemguards.com.ec> wrote: >> On Fri, Apr 9, 2010 at 3:39 PM, Jaime Casanova >> <jcasa...@systemguards.com.ec> wrote: >>> >> >> i think "make standbycheck" needs a little more work, why it isn't >> accesible from top of source dir? >> > > what i want to do. >
i started to make this, this weekend > 3) it should execute the existing set of tests (the ones installcheck > execute) but with a new set of expected results, that way we can be > sure that what should be disallowed is disallowed and that the > database is returning consistent values. i've thought about having > expected/normal (or expected/primary) and expected/standby and check > actual results against the appropiate one depending if we use > installcheck and standbycheck > the real question here is how pg_regress.c should know that it should compare against expected/primary or expected/standby? i mean, could i add an --standby option (my preferred) to pg_regress.c or should i try to guess it from current options and/or asking to the server? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL AsesorÃa y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
