| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: standbycheck was:(Re: [HACKERS] testing hot standby |
| Date: | 2010-05-01 16:56:31 |
| Message-ID: | 1272732991.4161.24016.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 2010-05-01 at 12:37 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> > On Sat, 2010-05-01 at 09:05 -0500, Jaime Casanova wrote:
> >> maybe we should be using the tables that exists in the regression
> >> database or adding hs_setup_primary in installcheck to prepare the
> >> regression database to run standbycheck in the standby server
>
> > That's part of the procedure already.
>
> Where is this test procedure documented?
In src/test/regress/standby_schedule
hs_standby_check.sql throws warning if not setup correctly.
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-05-01 17:12:40 | Re: standbycheck was:(Re: [HACKERS] testing hot standby |
| Previous Message | Tom Lane | 2010-05-01 16:37:25 | Re: standbycheck was:(Re: [HACKERS] testing hot standby |