November 2007 Archives by thread
- Messages sorted by: [ subject ] [ author ] [ date ]
- More info on this list...
Starting: Mon Nov 12 13:11:12 PDT 2007
Ending: Fri Nov 30 20:51:06 PDT 2007
Messages: 33
- [Slony1-bugs] Slony 1.2.10: Deadlock on slave during execute script Jeff Frost
- [Slony1-bugs] Slony 1.2.10: Deadlock on slave during execute script Jeff Frost
- [Slony1-bugs] Slony 1.2.10: Deadlock on slave during execute script Jeff Frost
- [Slony1-bugs] [Bug 8] New: SLON_DATA_FETCH_SIZE set too low slony1-bugs at lists.slony.info
- [Slony1-bugs] installation problem Lahcen AIT ALI
- [Slony1-bugs] [Bug 9] New: Revise documentation to indicate new trigger handling slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 10] New: Create a CANCEL SUBSCRIPTION command slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 11] New: duplicate_node.sh slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 12] New: Add tests to test_slony_state scripts slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 13] New: Change Slony-I to use PGXS slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 14] New: Pull lexer from psql slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 15] New: Set up some form of constraint on length of cluster name slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 15] Set up some form of constraint on length of cluster name slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 15] Set up some form of constraint on length of cluster name slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 15] Set up some form of constraint on length of cluster name slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 15] Set up some form of constraint on length of cluster name slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 15] Set up some form of constraint on length of cluster name slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 16] New: Change in function typenameTypeId() in PG 8.3 to have 3 args slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 16] Change in function typenameTypeId() in PG 8.3 to have 3 args slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 16] Change in function typenameTypeId() in PG 8.3 to have 3 args slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 16] Change in function typenameTypeId() in PG 8.3 to have 3 args slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 16] Change in function typenameTypeId() in PG 8.3 to have 3 args slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 17] New: slony doesn't build with a 'virtual' postgresql installation done with DESTDIR slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 17] slony doesn't build with a 'virtual' postgresql installation done with DESTDIR slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 17] slony doesn't build with a 'virtual' postgresql installation done with DESTDIR slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 18] New: Patch to shorten "attkind" on logtrigger functions slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 19] New: fresh schema for a logshipped node - keeping triggers out slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 19] fresh schema for a logshipped node - keeping triggers out slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 20] New: CANCEL SUBSCRIPTION, CANCEL TABLE slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 20] CANCEL SUBSCRIPTION, CANCEL TABLE slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 21] New: slon should report all configuration values in logs upon startup slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 21] slon should report all configuration values in logs upon startup slony1-bugs at lists.slony.info
- [Slony1-bugs] [Bug 22] New: Change in function typenameTypeId() in PG 8.3 to have 3 args slony1-bugs at lists.slony.info
Last message date:
Fri Nov 30 20:51:06 PDT 2007
Archived on: Thu Sep 25 08:15:22 PDT 2008
- Messages sorted by: [ subject ] [ author ] [ date ]
- More info on this list...
This archive was generated by Pipermail 0.09 (Mailman edition).