Regardless, if slonik is the interface to the stored procedures that is 
distributed as part of Slony, shouldn't its limitations be noted and 
eventually addressed?

I'm happy to play a limited role in the development process, as long as 
I can actually contribute rather than getting in over my head in terms 
of Slony code.

-tfo

On Jul 27, 2004, at 9:24 AM, Christopher Browne wrote:

>> I just figured I would mention this as a possible limitation. The
>> workaround will be to set things up in stages, I guess, but is there
>> anything that can be done to configure slony to avoid the stack
>> overflow?
>
> [Aside: I suspect you meant "to configure slonik to avoid the stack
> overflow"...]
>
> One way would be to not use slonik, but rather to directly use the
> plpgsql function that is used to add tables to the set