Alvaro Herrera writes:
> Yeah, as I recall the only thing the get_new_node thingy does is assign
> a nonconflicting port number to each instance, and make sure the
> instances are all teared down at END. I don't remember now why didn't
> we just do the port check in the constructor, but we messed
Victor Wagner wrote:
> Hi hackers!
>
> I've encountered need to extend functionality of PostgresNode class
> from the TAP test framework. What I want can easily be done via perl
> object inheritation.
>
> But documentation in the PostgresNode.pm recommends to use get_new_node
> function rather t
Hi hackers!
I've encountered need to extend functionality of PostgresNode class
from the TAP test framework. What I want can easily be done via perl
object inheritation.
But documentation in the PostgresNode.pm recommends to use get_new_node
function rather than call PostgresNode constructor dir
