Christopher Browne wrote:
>>Correct. So either subscribing an empty set must be disabled, or that
>>problem caught in slon. Seems I'll have to modify the event queue
>>manually.
> 
> 
> It's a bit harder than that...  One could use SET MOVE TABLE or SET
> DROP TABLE to empty out a set.
> 
> But certainly adding an advisory notice that subscribing an empty set
> is a bad idea would be a reasonable thing to do.
> 
> FYI, the problem is where there are no tables.  Having sequences
> doesn't help :-(.

Why is it a problem to catch the no-table-in-subscription case in slon 
and skip that offending cursor, or refuse to subscribe such a set?

Regards,
Andreas