> Just because Postgres itself allows it doesn't mean that every piece of
> software working with Postgres must be aware of this, does it?
Possibly.

But it is too bad to completely break the replication on a syntax error in
DDL script, I suppose.
We have spent more than 3 hours to recover from this error (re-createing the
origin and all subscribers from scratch).

On 8/30/07, Christopher Browne <cbbrowne at ca.afilias.info> wrote:
>
> Jan Wieck wrote:
> > On 8/29/2007 2:52 PM, Dmitry Koterov wrote:
> >> And much worse - seems such DDL with comments breaks the whole
> >> replication (fortunately I have run it on a test server, not in
> >> production).
> >> I watched sl_event table on a subscriber and noticed that the whole
> >> DDL (with comments included) are passed and saved in the subscriber.
> >
> > Where in the ANSI SQL standard does it allow -- comments nested inside
> > of /* ... */ comments?
> >
> > Just because Postgres itself allows it doesn't mean that every piece
> > of software working with Postgres must be aware of this, does it?
> >
> I new have a revision to address the /* */ style comments, and something
> reasonably tortuous to test them.
>
> I'm not going to put that in the 1.2 branch, though.
>
> I don't think DDL scripts are a good place to put entrants for the "most
> obfuscated PostgreSQL comments contest."
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070830/=
938c5389/attachment.htm