Mon Aug 13 23:34:52 PDT 2007
- Previous message: [Slony1-general] Slony locking
- Next message: [Slony1-general] cannot drop tables from schema after dropping tables from replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 2007-08-13 at 14:42 -0400, Jan Wieck wrote: > On 8/10/2007 11:04 AM, Simon Riggs wrote: > > Can I just check my understanding? > > > > Slony single threads access to the log tables indirectly, by making the > > log triggers do a LOCK TABLE on sl_event in EXCLUSIVE mode. > > > > So we don't actually do LOCK TABLE on sl_log in EXCLUSIVE mode, but that > > is the overall effect? > > Where does the log trigger do that? It should not! > > What does lock sl_event exclusively is the code that creates events, in > order to guarantee that events commit in the ev_seqno order and nothing > else. OK, thanks. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com
- Previous message: [Slony1-general] Slony locking
- Next message: [Slony1-general] cannot drop tables from schema after dropping tables from replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list