Prev: [HACKERS] improve plpgsql's EXECUTE 'select into' message with a hint
Next: recovery_connections cannot start
From: Simon Riggs on 1 May 2010 11:16
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.

We need something better for the future, though not sure if there's any
small tweaks worth making for 9.0 right now. Let's start making wider
plans for next release.

--
Simon Riggs www.2ndQuadrant.com


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Tom Lane on 1 May 2010 12:37
Simon Riggs <simon(a)2ndQuadrant.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?

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Simon Riggs on 1 May 2010 12:56
On Sat, 2010-05-01 at 12:37 -0400, Tom Lane wrote:
> Simon Riggs <simon(a)2ndQuadrant.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


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Tom Lane on 1 May 2010 13:12
Simon Riggs <simon(a)2ndQuadrant.com> writes:
> On Sat, 2010-05-01 at 12:37 -0400, Tom Lane wrote:
>> Where is this test procedure documented?

> In src/test/regress/standby_schedule

That's a good way to ensure nobody knows it's there :-(

If you want users to run this, document it in cookbook fashion in
doc/src/sgml/regress.sgml

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Simon Riggs on 1 May 2010 13:36
On Sat, 2010-05-01 at 13:12 -0400, Tom Lane wrote:
> Simon Riggs <simon(a)2ndQuadrant.com> writes:
> > On Sat, 2010-05-01 at 12:37 -0400, Tom Lane wrote:
> >> Where is this test procedure documented?
>
> > In src/test/regress/standby_schedule
>
> That's a good way to ensure nobody knows it's there :-(
>
> If you want users to run this, document it in cookbook fashion in
> doc/src/sgml/regress.sgml

OK

--
Simon Riggs www.2ndQuadrant.com


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: [HACKERS] improve plpgsql's EXECUTE 'select into' message with a hint
Next: recovery_connections cannot start