On Fri, 12 Jan 2007, Dun wrote:
> Steve Singer wrote:
>> What we have found much more painful is adding columns (or any other ALTER
>> table) command to tables that are already being replicated. In the current
>> version of slony this requires obtain an exclusive lock on all replicated
>> tables in all sets. This essentially requires an outage/maintaince window
>> to avoid deadlock.
>
> I thought that for execute script slonik requires an exclusive lock on all
> replicated tables /in the same set/.
> (http://linuxfinances.info/info/ddlchanges.html)
That section of the manual could use some clarification.
Read a few paragraphs down to the note arrow:
Actually, as of version 1.1.5 and later, this is NOT TRUE. The danger of
someone making DDL changes that crosses replication sets seems
sufficiently palpable that slon(1) has been changed to lock ALL
replicated tables,whether they are in the specified replication set or
not.
http://linuxfinances.info/info/stmtddlscript.html is a bit more clear on the
subject.
>
> Regards
>
> MP
>
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
