Prev: [HACKERS] [Fwd: [BUGS] build error: strlcat/strlcpy used from heimdal libroken.so]
Next: shared_buffers documentation
From: Jaime Casanova on 14 Apr 2010 10:16
On Sat, Apr 10, 2010 at 12:23 AM, Jaime Casanova
<jcasanov(a)systemguards.com.ec> wrote:
> On Fri, Apr 9, 2010 at 3:39 PM, Jaime Casanova
> <jcasanov(a)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.

1) make standbycheck should be accesible from top source dirs
2) it should use an existing regression database on an already
configured standby server (no need of the hs_primary_setup.sql)
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

comments? i will start this the weekend...

--
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(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: [HACKERS] [Fwd: [BUGS] build error: strlcat/strlcpy used from heimdal libroken.so]
Next: shared_buffers documentation