https://wiki.postgresql.org/api.php?action=feedcontributions&user=Masonsharp&feedformat=atomPostgreSQL wiki - User contributions [en]2024-03-19T14:00:55ZUser contributionsMediaWiki 1.35.13https://wiki.postgresql.org/index.php?title=Pgcon2014PostgresXCmeeting&diff=22367Pgcon2014PostgresXCmeeting2014-05-16T00:45:23Z<p>Masonsharp: /* 9AM to 1PM */</p>
<hr />
<div>= PostgresXC Developer Meeting pgCon 2014 =<br />
<br />
Tuesday, May 20th<br />
<br />
9AM to 1PM<br />
<br />
Followed by [[PgCon2014ClusterSummit|Clustering Summit]] at 2PM<br />
<br />
University of Ottawa<br />
<br />
Room: Desmarais 10161<br />
<br />
'''Sponsored by NTT Open Source'''<br />
<br />
= PostgresXC Day =<br />
<br />
=== 9AM to 1PM ===<br />
<br />
Same room as clustering summit.<br />
<br />
Topics:<br />
<br />
* Postgres-XL Overview (Mason Sharp)<br />
<br />
=== 1PM to 2PM ===<br />
<br />
Lunch for those attending both the PostgresXC summit and the Clustering Summit<br />
<br />
=== 7PM to 9PM ===<br />
<br />
PostgresXC Demo + Pizza<br />
<br />
=== RSVP List ===<br />
<br />
RSVP if you plan to attend. Please RSVP for this and the Clustering Summit if you plan to attend both, and want lunch.<br />
<br />
# Koichi Suzuki<br />
# Josh Berkus<br />
# Mason Sharp<br />
# Bruce Momjian<br />
# Rafael Guembes<br />
# Ioana Danes (Canadian Bank Note)<br />
# Arthur Karton (Canadian Bank Note)<br />
# Jim Mlodgenski<br />
# Mark Linster<br />
# Zahid Iqbal<br />
# Ahsan Hadi<br />
# Hitoshi Hemmi<br />
<br />
[[Category:PostgreSQL Events]]<br />
<br />
[[Category:PGCon2014]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=PgCon2014ClusterSummit&diff=22366PgCon2014ClusterSummit2014-05-16T00:44:03Z<p>Masonsharp: </p>
<hr />
<div>= Clustering and Replication Developers Summit pgCon 2014 =<br />
<br />
Tuesday, May 20th<br />
<br />
2PM to 6PM<br />
<br />
Preceded by [[Pgcon2014PostgresXCmeeting|PostgresXC Meeting]] 9AM to 1PM<br />
<br />
Followed by the PostgresXC Pizza Demo at 7pm.<br />
<br />
University of Ottawa<br />
<br />
Room: Desmarais 10161 <br />
<br />
'''Sponsored by NTT Open Source'''<br />
<br />
=== Agenda ===<br />
<br />
==== 1:00PM to 2:00PM ====<br />
<br />
Box Lunches supplied for anyone coming for the whole day (PostgresXC + Clustering)<br />
<br />
==== 1:30PM to 2:00PM ====<br />
<br />
Please bring any last-minute agenda items to Josh Berkus at this time.<br />
<br />
==== 2:00PM to 2:45PM ====<br />
<br />
Introductions, and status reports from Replication/Clustering Projects:<br />
<br />
Status updates (please volunteer below if you can give an update):<br />
<br />
* pgPool II: <br />
* Postgres-XC: <br />
* Built-in Replication: <br />
* Postgres-XL:<br />
* Stado:<br />
* Bucardo: <br />
* LSR & BDR:<br />
* Slony<br />
<br />
If you are at the summit representing a specific replication or clustering tool, you should prepare a 1-3 minute summary of current progress and issues. If you want to use slides, please provide slides in PDF form to Josh Berkus by Friday, May 16.<br />
<br />
==== 2:45PM to 3:15PM ====<br />
<br />
Summary of Clustering API projects.<br />
<br />
Summit attendees who have been working on [[ClusterFeatures|core clustering features]] should give an update as to progress and current issues. Please present a 5-10 minute summary. Attendees may use their own laptops for slides, or give slides to Josh Berkus.<br />
<br />
Topics:<br />
<br />
* '''Serializable & Predicate locks on MM replication''':<br />
* '''Event Triggers''':<br />
* '''Exportable Snapshots''':<br />
* '''Planner/Parser Hooks''': <br />
* '''Logical Changeset Extraction''':<br />
* '''Foreign Data Wrappers''':<br />
<br />
==== 3:15PM to 3:45PM ====<br />
<br />
Break<br />
<br />
==== 3:45PM to 4:30PM ====<br />
<br />
Summary of Clustering API projects, continued.<br />
<br />
==== 4:30PM to 6:00PM ====<br />
<br />
Discussion of priorities, progress and ideas for core clustering projects and APIs.<br />
<br />
Goal of this discussion is to modify the list of core clustering features and get commitments for hackers to work on specific features. Also, to supply discussion items for the following day's Developer Meeting<br />
<br />
=== RSVP List ===<br />
<br />
# Josh Berkus<br />
# Koichi Suzuki<br />
# Tatsuo Ishii (SRA OSS)<br />
# Haruka Takatsuka (SRA OSS)<br />
# Yugo Nagata (SRA OSS)<br />
# Mason Sharp<br />
# Bruce Momjian<br />
# Chris Browne<br />
# David Wheeler<br />
# Moshe Jacobson (Nead Werx)<br />
# Chris Autry (Nead Werx)<br />
# Joe Conway<br />
# Ioana Danes (Canadian Bank Note)<br />
# Arthur Karton (Canadian Bank Note)<br />
# Steve Singer<br />
# Jan Wieck<br />
# Jim Mlodgenski<br />
# Vik Fearing<br />
# Marc Linster (EDB)<br />
# Ahsan Hadi (EDB)<br />
# Zahid Iqbal (EDB)<br />
# Etsuro Fujita (NTT OSS Center)<br />
# Amit Chapel<br />
# Krzysztof Nienartowicz (ESA)<br />
# Hitoshi Hemmi (NTT OSS Center)<br />
# Álvaro Hernández<br />
[[Category:PostgreSQL Events]]<br />
[[Category:PGCon2014]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=PGConf_NYC_2014_Talks&diff=22084PGConf NYC 2014 Talks2014-04-07T19:44:37Z<p>Masonsharp: /* Grand Ballroom Salon C */</p>
<hr />
<div>= PGConf NYC 2014 Talks =<br />
<br />
== Conference Website ==<br />
<br />
http://nyc.pgconf.us/2014<br />
<br />
== Talks: Thursday April 3, 2014 ==<br />
<br />
=== Keynotes ===<br />
<br />
[https://wiki.postgresql.org/images/9/9f/PostgreSQL_Keynote_-_GS.pdf Increase Enterprise PostgreSQL Adoption at Firms Like Goldman Sachs in Financial Services]<br />
<br />
=== Grand Ballroom Salon A&B ===<br />
<br />
[http://nbviewer.ipython.org/gist/nyamada/9946705 Using Postgres for append-only immutable data]<br />
<br />
=== Grand Ballroom Salon C ===<br />
[https://wiki.postgresql.org/wiki/File:Achieving_PCI_Compliace_PgConfNYC2014.pdf Achieving PCI compliance with Postgres]<br />
<br />
[http://snowman.net/slides/pgsecurity-pgconfnyc14_20140403.pdf Intro to PostgreSQL Security]<br />
<br />
[http://www.slideshare.net/mason_s/geographically-distributed-postgresql Geographically Distributed PostgreSQL]<br />
<br />
=== Empire Room ===<br />
[https://wiki.postgresql.org/wiki/File:Pgconfnyc2014_whenpgcantyoucan.pdf When PostgreSQL Can't, You Can]<br />
<br />
== Talks: Friday April 4, 2014 ==<br />
<br />
=== Keynotes ===<br />
<br />
=== Grand Ballroom Salon A&B ===<br />
[http://momjian.us/main/writings/pgsql/central.pdf Making Postgres Central in Your Data Center]<br />
<br />
=== Grand Ballroom Salon C ===<br />
<br />
=== Empire Room ===<br />
<br />
* [https://github.com/dwsteele/conference/releases/tag/release%2FDatabaseValidationAndVersioning-PGConfNYC2014 Database Validation and Versioning]<br />
* [http://www.joeconway.com/presentations/plr-PGConfNYC2014.pdf Easy Statistical Analysis in PostgreSQL with PL/R]<br />
* [http://www.slideshare.net/gavinmroy/integrating-postgresql-with-rabbitmq Integrating PostgreSQL with RabbitMQ]<br />
* [https://wiki.postgresql.org/wiki/File:Eav-pgconfnyc2014.pdf An Adventure in Data Modeling: The Entity-Attribute-Value Data Model]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=PgCon2014ClusterSummit&diff=21925PgCon2014ClusterSummit2014-03-07T02:35:02Z<p>Masonsharp: /* RSVP List */</p>
<hr />
<div>= Clustering and Replication Developers Summit pgCon 2013 =<br />
<br />
Tuesday, May 20th<br />
<br />
2PM to 6PM<br />
<br />
Preceded by [[Pgcon2014PostgresXCmeeting|PostgresXC Meeting]] 9AM to 1PM<br />
<br />
University of Ottawa<br />
<br />
Room: TBD<br />
<br />
'''Sponsored by NTT Open Source'''<br />
<br />
=== Agenda ===<br />
<br />
==== 1:00PM to 2:00PM ====<br />
<br />
Box Lunches supplied for anyone coming for the whole day (PostgresXC + Clustering)<br />
<br />
==== 1:30PM to 2:00PM ====<br />
<br />
Please bring any last-minute agenda items to Josh Berkus at this time.<br />
<br />
==== 2:00PM to 2:45PM ====<br />
<br />
Introductions, and status reports from Replication/Clustering Projects:<br />
<br />
Status updates (please volunteer below if you can give an update):<br />
<br />
* pgPoolII: <br />
* Postgres-XC: <br />
* Built-in Replication: <br />
* Stado:<br />
* Bucardo: <br />
* LSR & BDR:<br />
<br />
If you are at the summit representing a specific replication or clustering tool, you should prepare a 1-3 minute summary of current progress and issues. If you want to use slides, please provide slides in PDF form to Josh Berkus by Friday, May 16.<br />
<br />
==== 2:45PM to 3:15PM ====<br />
<br />
Summary of Clustering API projects.<br />
<br />
Summit attendees who have been working on [[ClusterFeatures|core clustering features]] should give an update as to progress and current issues. Please present a 5-10 minute summary. Attendees may use their own laptops for slides, or give slides to Josh Berkus.<br />
<br />
Topics:<br />
<br />
* '''Serializable & Predicate locks on MM replication''':<br />
* '''Event Triggers''':<br />
* '''Exportable Snapshots''':<br />
* '''Planner/Parser Hooks''': <br />
* '''Logical Changeset Extraction''':<br />
<br />
==== 3:15PM to 3:45PM ====<br />
<br />
Break<br />
<br />
==== 3:45PM to 4:30PM ====<br />
<br />
Summary of Clustering API projects, continued.<br />
<br />
==== 4:30PM to 6:00PM ====<br />
<br />
Discussion of priorities, progress and ideas for core clustering projects and APIs.<br />
<br />
Goal of this discussion is to modify the list of core clustering features and get commitments for hackers to work on specific features. Also, to supply discussion items for the following day's Developer Meeting<br />
<br />
=== RSVP List ===<br />
<br />
# Josh Berkus<br />
# Koichi Suzuki<br />
# Tatsuo Ishii (and 2 others from SRA OSS)<br />
# Mason Sharp<br />
<br />
[[Category:PostgreSQL Events]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=Pgcon2014PostgresXCmeeting&diff=21924Pgcon2014PostgresXCmeeting2014-03-07T02:34:05Z<p>Masonsharp: /* RSVP List */</p>
<hr />
<div>= PostgresXC Developer Meeting pgCon 2014 =<br />
<br />
Tuesday, May 20th<br />
<br />
9AM to 1PM<br />
<br />
Followed by [[PgCon2014ClusterSummit|Clustering Summit]] at 2PM<br />
<br />
University of Ottawa<br />
<br />
Room: TBD<br />
<br />
'''Sponsored by NTT Open Source'''<br />
<br />
= PostgresXC Day =<br />
<br />
=== 9AM to 1PM ===<br />
<br />
Same room as clustering summit.<br />
<br />
Topics:<br />
<br />
*<br />
<br />
=== 1PM to 2PM ===<br />
<br />
Lunch for those attending both the PostgresXC summit and the Clustering Summit<br />
<br />
=== 7PM to 9PM ===<br />
<br />
PostgresXC Demo + Pizza<br />
<br />
=== RSVP List ===<br />
<br />
RSVP if you plan to attend. Please RSVP for this and the Clustering Summit if you plan to attend both, and want lunch.<br />
<br />
# Koichi Suzuki<br />
# Josh Berkus<br />
# Mason Sharp<br />
<br />
[[Category:PostgreSQL Events]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=PgCon2013CanadaClusterSummit&diff=19400PgCon2013CanadaClusterSummit2013-04-21T13:28:09Z<p>Masonsharp: /* RSVP List */</p>
<hr />
<div>= Clustering and Replication Developers Summit pgCon 2013 = <br />
<br />
Tuesday, May 21st<br />
<br />
9:30AM to 2:30pm<br />
<br />
Followed by PostgresXC Summit 3pm to 6pm<br />
<br />
University of Ottawa<br />
<br />
Room TBD<br />
<br />
'''Sponsored by NTT Open Source'''<br />
<br />
=== Agenda ===<br />
<br />
==== 9AM to 9:30AM ====<br />
<br />
Seating and coffee. Please bring any last-minute agenda items to Josh Berkus at this time.<br />
<br />
==== 9:30AM to 10:15AM ====<br />
<br />
Introductions, and status reports from Replication/Clustering Projects:<br />
<br />
Status updates:<br />
<br />
* pgPoolII: Tatsuo Ishii<br />
* Postgres-XC: Koichi Suzuki<br />
* Built-in Replication: Simon Riggs<br />
* Stado: Mason Sharp<br />
<br />
If you are at the summit representing a specific replication or clustering tool, you should prepare a 1-3 minute summary of current progress and issues. If you want to use slides, please provide slides in PDF form to Josh Berkus by Friday, May 17.<br />
<br />
==== 10:15AM to 10:30 AM ====<br />
<br />
Break<br />
<br />
==== 10:30AM to 11:30AM ====<br />
<br />
Summary of Clustering API projects.<br />
<br />
Summit attendees who have been working on [[ClusterFeatures|core clustering features]] should give an update as to progress and current issues. Please present a 5-10 minute summary. Attendees may use their own laptops for slides, or give slides to Josh Berkus.<br />
<br />
Topics:<br />
<br />
* Event Triggers: <br />
* Exportable Snapshots:<br />
* <br />
<br />
==== 11:30AM to 12:30PM ====<br />
<br />
Discussion of priorities, progress and ideas for core clustering projects and APIs.<br />
<br />
Goal of this discussion is to modify the list of core clustering features and get commitments for hackers to work on specific features. Also, to supply discussion items for the following day's Developer Meeting<br />
<br />
==== 12:30PM to 1:30PM ====<br />
<br />
Lunch and follow-up discussion. Box lunches will be supplied.<br />
<br />
==== 1:30PM to 2:30PM ====<br />
<br />
Follow-up discussion. Consolidation of future clustering API goals and projects.<br />
<br />
=== RSVP List ===<br />
<br />
# Josh Berkus<br />
# Koichi Suzuki<br />
# Kevin Grittner<br />
# Jim Mlodgenski<br />
# Mason Sharp<br />
# Nikhil Sontakke<br />
# Steve Singer<br />
# Jan Wieck<br />
# David Wheeler<br />
# Ashutosh Bapat<br />
# Galy Lee<br />
<br />
= PostgresXC Day =<br />
<br />
=== 3pm to 6pm ===<br />
<br />
Same room as clustering summit.<br />
<br />
* Topics in Version 1.1<br />
* Roadmap toward version 1.2 and beyond<br />
* Development Issues<br />
* Experiences<br />
<br />
=== Extension on Wednesday and Saturday ===<br />
<br />
Informal open discussion on Postgres-XC feature and internal will be held at Koichi's hotel room on 22nd, Wednesday. Depending upon topics, similar discussion can be held on Saturday.<br />
<br />
=== RSVP List ===<br />
<br />
Please check if you can join. Add yourself in the list too.<br />
<br />
# Ahsan Hadi<br />
# Ashutosh Bapat<br />
# Hitoshi Hemmi<br />
# Koichi Suzuki<br />
# Tetsuo Sakata<br />
# Galy Lee<br />
# Mason Sharp<br />
# Jim Mlodgenski<br />
# Nikhil Sontakke<br />
[[Category:PostgreSQL Events]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=PGDay_NYC_2013_Talks&diff=19292PGDay NYC 2013 Talks2013-03-27T19:43:30Z<p>Masonsharp: /* Liberty Hall C */</p>
<hr />
<div>= PGDay NYC 2013 Talks =<br />
<br />
== Friday March 22nd, 2013 ==<br />
<br />
=== Liberty Hall C ===<br />
<br />
* [http://www.slideshare.net/davidfetter/ct-es-pastpresentfuturenycpgday20130322 CTEs: Past, Present and Future (David Fetter)]<br />
* [http://momjian.us/main/writings/pgsql/locking.pdf Understanding the Postgres Lock Manager (Bruce Momjian)]<br />
* [http://plv8-talk.herokuapp.com/ Embracing the Web with JSON and PLV8 (Will Leinweber)]<br />
* [https://speakerdeck.com/mbryzek/schema-evolutions-at-gilt-groupe Schema Evolutions at Gilt Groupe (Michael Bryzek)]<br />
* [http://www.slideshare.net/stormdb_cloud_database/postgres-xc-askeyvaluestorevsmongodb A Postgres-XC Distributed Key-Value Store (Mason Sharp)]<br />
<br />
=== Liberty Hall A ===<br />
<br />
* [[:File:PPCD.pdf|Postgres Plus Cloud Database (Dave Page)]]<br />
* [https://github.com/petere/logging-hooks-presentation Toward real-time log analysis (Peter Eisentraut)]<br />
<br />
[[Category:PostgreSQL Events]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=PgCon2011CanadaClusterSummit&diff=14398PgCon2011CanadaClusterSummit2011-05-18T19:22:33Z<p>Masonsharp: Minor corrections of project names</p>
<hr />
<div>== Clustering and Replication Developers Summit pgCon 2011==<br />
<br />
Tuesday, May 17th<br />
<br />
9:30AM to 5:15pm<br />
<br />
University of Ottawa<br />
<br />
Desmerais (DMS) 3105 (break out room: DMS 10161) (this is the same building the sessions are in)<br />
<br />
[http://www.pgcon.org/2011/maps.php Maps] for campus, building.<br />
<br />
'''Sponsored by NTT Open Source'''<br />
<br />
=== Agenda ===<br />
<br />
==== 9AM to 9:30AM ====<br />
<br />
Seating and coffee. Please bring any last-minute agenda items to Josh Berkus at this time.<br />
<br />
==== 9:30AM to 10:15AM ====<br />
<br />
Introductions, and status reports from Replication/Clustering Projects:<br />
<br />
Status updates:<br />
<br />
* Slony-I: Jan Wieck<br />
* pgPoolII: Tatsuo Ishii<br />
* Postgres-XC: Koichi Suzuki and Michael Paquier<br />
* GridSQL/Stado: Mason Sharp<br />
* Bucardo: Selena Deckelmann<br />
* SkyTools: Marko Kreen<br />
* Binary Replication: Simon Riggs<br />
* Mammoth Replication: Alexey Klyukin<br />
<br />
If you are at the summit representing a specific replication or clustering tool, you should prepare a 1-3 minute summary of current progress and issues. If you want to use slides, please provide slides in PDF form to Josh Berkus by Friday, May 13.<br />
<br />
==== 10:15AM to 10:30 AM ====<br />
<br />
Break<br />
<br />
==== 10:30AM to 11:00AM ====<br />
<br />
Summary of Clustering API projects.<br />
<br />
Summit attendees who have been working on [[ClusterFeatures|core clustering features]] should give an update as to progress and current issues. Please present a 2-3 minute summary. Attendees who wish to use slides should provide PDF slides to Josh Berkus by Friday May 13th.<br />
<br />
==== 11:00AM to 12:30PM ====<br />
<br />
Discussion of priorities, progress and ideas for core clustering projects and APIs.<br />
<br />
Goal of this discussion is to modify the list of core clustering features and get commitments for hackers to work on specific features. Also, to supply discussion items for the following day's Developer Meeting<br />
<br />
==== 12:30PM to 1:30PM ====<br />
<br />
Lunch. Box lunches will be supplied.<br />
<br />
==== 1:30 to 2:00 ====<br />
<br />
Breakout sessions scheduling session.<br />
<br />
==== 2:00 to 3:15 ==== <br />
<br />
Breakout sessions part I<br />
<br />
Summit attendees should break into affinity groups and discuss specific core features and APIs. Attendees should come back from breakout session with rough specifications and/or plans.<br />
<br />
==== 3:15 to 3:30 ====<br />
<br />
All attendees gather and deliver summary of breakout sessions.<br />
<br />
==== 3:30 to 3:45 ====<br />
<br />
Coffee Break<br />
<br />
==== 3:45 to 4:45 ====<br />
<br />
Breakout sessions II<br />
<br />
==== 4:45 to 5:15 ====<br />
<br />
Attendees gather and deliver summaries of 2nd breakout sessions.<br />
<br />
Conclusion of Summit.<br />
<br />
=== RSVP List ===<br />
<br />
# Josh Berkus<br />
# Andres Freund<br />
# Selena Deckelmann<br />
# Kevin Grittner<br />
# Dimitri Fontaine<br />
# Christopher Browne<br />
# Steve Singer<br />
# Marko Kreen<br />
# Jan Wieck<br />
# Tatsuo Ishii<br />
# Koichi Suzuki<br />
# Kevin Grittner<br />
# Andrew Dunstan<br />
# Jan Wieck<br />
# Fujii Masao<br />
# Ahsan Hadi<br />
# Michael Paquier<br />
# Jehan-Guillaume (ioguix) de Rorthais<br />
# Mason Sharp<br />
# Pavan Deolasee<br />
# Ghulam Abbas Butt<br />
# Sakata Tetsuo<br />
# Greg Smith [leaving before lunch]<br />
# Simon Riggs<br />
# Toshiro Kitagawa<br />
# Nozomi Anazai<br />
# Alexey Klyukin<br />
<br />
== List of Features ==<br />
<br />
* Export snapshots to other sessions<br />
** Postgres-XC team working on, planning to contribute next year<br />
** needs design discussion<br />
* Global conflict resolution and detection<br />
** Kevin Grittner to specify<br />
* API into the Parser / Parser as an independent module<br />
** Alvaro Herrera & Tatsuo Ishii & pgPool team<br />
* Start/stop archiving at runtime<br />
** Selena to find original patch<br />
* Function scan push-down<br />
** Postgres-XC team & SQL/MED<br />
* DDL trigger<br />
** Jan Wieck (design) & Dimitri (code)<br />
* Modification trigger into core<br />
** Jan Wieck & Marko Kreen to discuss during breakout session<br />
* Commit order of transactions<br />
** Andres & Kevin to decide feasibility<br />
* Dynamic shared memory allocation<br />
** take off the list, not clustering-specific and concerns also Postgres<br />
* XID feed<br />
** really part of exportable snapshots<br />
* SSI support for Hot Standby<br />
** Kevin & Simon<br />
* Commit Hooks<br />
** Simon Riggs to Spec<br />
** needed for updatable FDW<br />
* Lock Database - stops new connections to DB or new transactions<br />
** Postgres-XC only maybe, other projects may need it for dropping DB securely<br />
** Michael to create definition => [[Lock_database|Lock database definition]]<br />
<br />
==Minutes==<br />
<br />
==Status Updates by Project==<br />
<br />
===Slony: Jan Wieck===<br />
*Status of slony is improving. It is in beta for 2.1 and it has improvements all over the board.<br />
*Steve and Jan developed a clustertest framework that allows them to test the features of slony (moving sets, changing the shape of subscriptions, etc.) while the application is under load, checking consistency etc., Performance wise slony has always performed well when used as intended but an issue with backlog has been fixed for 2.1 and will be backpatched to 2.0. <br />
*On usability most people don't know how to use the wait for event command, Steve has worked on teaching slonik to automatically know when to wait. <br />
*Clustertest could be adapted to other projects. The transaction profiles are defined in Javascript along with the other governing scripts. It is available on github.<br />
<br />
===PGPoolII: Toshihiro Kitagawa===<br />
*PGPool has query based replication, load balancing, automatic failover and connection pooling. It is an OSS project managed by the pgpool global development group. Website, mailing list on pgfoundry. Pgpool II, pgpool admin, pgpool HA (heartbeat scripts). Version 3 is stable and 3.1 is under development. It has had streaming replication since verison 3.0. It dispatches write queries to the primary node and read queries to either node according to the load balanced wait. If a node goes down pgpool II an send all queries to the remaining node. 3.1 beta is hoping to be released soon.<br />
*New features in 3.1 (SQL parser was imported from postgresql 9.0), it can understand new syntax introduced in 9.0 such as 'create index with a name'. , follow master command directive can better support streaming replication. Call management facility, ability for pgadmin and PHPpgadmin to control pgpool. Can use regular expressions in white and black function lists (controls which functions pgpool thinks performs writes to the database). Ability to use syslog, ability to specify the lifetime of the system catalog cache.<br />
*Future plans: on in memory query cache (pgpool II already has a query cache) but it is not fast and does not have automatic invalidation (GSOC project to solve this). Ability to manage multiple pgpool II instances sharing the same database cluster this will require exchanging information.<br />
<br />
===GridSQL: Mason Sharp===<br />
<br />
*GridSQL enables grid capability for dw workloads. This was an EDB project, Mason and Jim have both left EDB. Jim has forked GridSQL to a new project called Stado. He stripped out some EDB specific code.<br />
*Working on adding PostGIS support. <br />
*It will benefit from unlogged tables in 91.<br />
He next wants to work on high availability and integrate with streaming replication.<br />
<br />
===Postgres-XC : Michael Paquier===<br />
*XC is a multi-master cluster based on Postgresql 9.0. Last release is 0.9.4 on March 2011. Major changes are that it is now BSD licensed so they could gather more people. Merged in code from 9.0.3 in. SQL support most of DDL, DML and SELECT single step queries (order by , limit, offset).<br />
*Regression tests looking for possible bugs and comparing with PostgreSQL. DBT-1 benchmark test 3.6 scale factor for 5 servers. <br />
*Next release is for June 2011 with support for session parameters, grant, revoke, group by data distribution extensions and single prepared sql/plpgsql queries. They will also add some HA features such as when a node crashes with a partially committed txn they will be able to clean up the txn. <br />
*A configurator and a cluster manager will also be provided to make setup easier. These are written in ruby.<br />
*Node reconnection features that allows you to reconnect to new GTM when it fails over, without losing live transactions. <br />
Also a standby transaction manager.<br />
*Plan is to release 1.0 in April 2012. Should include PITR ,temp tables, cross node operation optimizations and multi-step prepared statements.<br />
*Reviews, contributions and ideas are welcome.<br />
*License will be changed to PostgreSQL license<br />
<br />
===Bucardo (Selena Decklman)===<br />
*Bucardo is a multimaster replication system written in perl, trigger based. <br />
*Last week Greg released version 5 (alpha code) that takes away the two master restriction (you can have any numer of masters) it uses the listen/notify payload system, and has other changes.<br />
More work needs to be done to re-implement the sequence support so it works with many masters.<br />
<br />
===Skytools (Marko Kreen)===<br />
*They have not yet released a final version of 3.0 but Skype is using it live and they will/should release this to the public. <br />
*Skytools 2.1 has a generic queue that replication is built on top of. In 3 they have cascaded replication and to do this they implemented a generic cascaded queue. <br />
*In version 3 they have handlers/plugins that can be done to change things (ie table partitioning). They have implemented multi-master that will merge row updates from different databases. They were not trying to solve generic multi-master but more for having fast failover between masters.<br />
*It is not known yet if Skytools 3.1 will be available to public or not<br />
<br />
===Binary Replication (Simon Riggs)===<br />
*in 9.1 synchronous replication made it into core thanks to a lot of teamwork from a large number of people.<br />
*Something amazing happened in that after 400 posts of arguing on the configuration we ended up with a simple configuration that can be explained in less than 10 minutes (Josh).<br />
*A lot of the efforts over the last 7 years was to be able to get synchronous replication and by having transaction controlled replication we have something beyond what the big commercial players offer.<br />
*Repmgr is about to release the next version that has fully automated multi-node failover. They are using this in production for a few customers already.<br />
*There are already 2 systems in production using it (one in Finland)<br />
*Simon is thinking of turning his attention to more logical replication<br />
<br />
===Mammoth Replication===<br />
*They have suspended development efforts<br />
*It is a master slave binary replication system that is a fork of postsgresql.<br />
*It has master slave replication, failover. It has a master that accepts writes with a custom queue (a set of files, one file per txn) when the transactions come they get put into the queue and data is then extracted and sent to a middleman process that is responsible for communicating with slaves. *This process (MCP) forwards the data to the slaves. The slaves then restore the data from this queue. <br />
*They added system catalogs for storing replication data, these catalogs got replicated to the slaves as well. They added custom hooks into postgresql to collect this data. They do not require the nodes to be constantly online but can go offline and perform updates in batches. <br />
*Reliability vs performance tradeoffs made early in development: The mcp process became a single point of failure. Before suspending the project they were working on getting round-robin mcp processes.<br />
*They felt that 9.0 internal replication was pretty good and since they were maintaining a fork keeping up with the changes was a lot of work so they decided to suspend the project.<br />
The code is BSD licensed and is available in github<br />
<br />
===Note===<br />
*BSD license has been declared as different from PostgreSQL license. Even if content of each license is the same, the words used for each license are different, making it different (Josh, judgement decision on PostgreSQL license).<br />
*A a consequence, cluster products should have a PostgreSQL license and not a BSD one.<br />
<br />
==Status Updates by Project==<br />
<br />
Last year a set of clustering related features was discussed at [http://wiki.postgresql.org/wiki/ClusterFeatures]<br />
<br />
===Snapshot exports===<br />
We have a design, there was a patch floating around by Joachim Wieland but the patch was not general enough and was not committed to 9.1. The postgresql-xc team might be able to look at this in the future but so far they have not gotten to it. The consensus in the room was that this feature is needed for parallel queries and useful for binary replication systems. Joachim's patch uses a file for storing the snapshots and this might not work for exporting the snapshot list to a standby server.<br />
<br />
===Global Deadlock Information===<br />
The conclusion of the discussion in Japan was that it was unclear if they this was needed or if a timeout based approach would be sufficient. No one in the room has worked on this since then. A few people stated that there are other ways of resolving conflicts (depending on the system/architecture)<br />
<br />
===API into the parser===<br />
<br />
This was raised in the past and there was some opposition to making the parser code more complicated than it is now. A few people felt that exposing the parser API would require doing something other than the current grammar generated parser. This could be marketed as a parser simplification. Non core projects (phppgadmin, pgpool would like this). Other non postgresql projects are grabbing/reusing our existing parser. For most applications the raw parse isn't useful anyway it will have needed to pass through the catalog access (the rewritten parse tree). <br />
<br />
===Start/stop archiving at runtime===<br />
There are some optimizations that only work when archiving is off, so implementing this needs to make sure that any transactions using the optimizations are done before archiving is on. This just needs someone to do it<br />
<br />
===Function scan-push down===<br />
Parts of these are being worked on by postgresql-xc<br />
The EDB version of postgresql can do some of these things but that code is proprietary though some parts of this did get included in postgres-xc that is now BSD licensed.<br />
A GSOC student is working on some components of this<br />
<br />
===DDL Triggers===<br />
*Nothing beyond discussion/theory has happened on this.<br />
*The question remains where to hook this in, tcop would be logical but sometimes utility statement code does not go through here. There are also issues with cached query plans<br />
What would this receive as input arguments for it to be useful for triggers to do things?<br />
If the code were cleaned up so everything called tcop and then outFuncs were written for everything in the parse tree. <br />
*Jan has worked on the theory but has not made progress on implementation. <br />
<br />
===Modification trigger into core===<br />
*Skytools had tried implementing something that was function based on it was ugly<br />
PgQueue might be suitable as a generic queue<br />
<br />
===Exporting commit order of transactions===<br />
*Work on this has been given up on<br />
*With serializable transactions we might want to look at apparent order of execution not just order of commit<br />
*Would be valuable for replication as it could eliminate the need for "Syncs" (Slony) or "ticks" (Londiste)<br />
<br />
===Dynamic shared memory allocation===<br />
*No one in the room had looked at this. This seemed more appropriate to discuss at the postgresql developers meeting<br />
<br />
===XID Feed===<br />
*This is related to snapshot exporting.<br />
*If you want to share the same transaction context in a different node you need an XID feed to accomplish this. <br />
*Postgres-XC needs this but it might not be relevant to other projects<br />
<br />
==Breakout sessions==<br />
===DDL Triggers===<br />
<br />
Parse tree of utility statement.<br />
<br />
SELECT INTO does not create completion code.<br />
<br />
DDL Trigger needs to offer parse tree of utility statements. But parse tree is binary. ASCII string format might be better, but would need to implement it.<br />
<br />
Maybe just look add after data structure. Maybe have parameters on what would be output.<br />
<br />
Might need both before and after triggers.<br />
<br />
Simplest case is create table. Second is create partition, if its empty.<br />
<br />
Put triggers on schema and database level.<br />
<br />
Need to funnel everything through processutility.<br />
<br />
Some utility statements execute recursive processutility calls. Also multi-event statements.<br />
<br />
Need:<br />
* todo list of statements & other things which need clean access to processutility<br />
* backparsing of utility command<br />
* specification for triggers, trigger parameters.<br />
<br />
Triggers: want parameters like oid, statement, etc. to return certain things. Also want WHEN clauses.<br />
<br />
Need need attributes for triggers in order to do DDL triggers, and OLD and NEW etc. doesnt work. Maybe new system catalog.<br />
<br />
===Parser API===<br />
*3 or 4 use cases pgpool, Syntax colouring, people trying to determine if queries are read only, <br />
*output from the parser after rewrite (for pgpool case). Did not determine what the best output of the API is. Some set of rows specifying the type and position.<br />
*It is not at all clear what output pgpool would want, maybe the parse tree?<br />
*Do we need some sort of compatibility assurance for future version, they do not think that they need this and no promise of compatibility would be made</div>Masonsharphttps://wiki.postgresql.org/index.php?title=Postgres-XC-GSOC&diff=10233Postgres-XC-GSOC2010-03-15T14:35:01Z<p>Masonsharp: Postgres-2 -> Postgres-XC</p>
<hr />
<div>== Postgres-XC Google Summer of Code 2010 ==<br />
<br />
[[Postgres-XC]] (previously also known as Postgres-2) is applying for Google Summer of Code 2010.<br />
<br />
The idea list for contributions include:<br />
<br />
* Support for multiple coordinators. Secondary coordinators register with the primary coordinator. DDL (CREATE TABLE, etc.) goes first through primary coordinator, which synchronizes changes amongst the nodes. Long term we also allow for tracking if secondary coordinators are out of date, and for copying over catalog information to the secondaries.<br />
<br />
* Add support for cursors, first for forward only without ORDER BY.<br />
<br />
* Backup & Restore<br />
<br />
* Expand capability of pooler to handle session parameters.<br />
<br />
We prefer to focus on the first item, support for multiple coordinators<br />
<br />
<br />
[[Category:Replication]]<br />
[[Category:Clustering]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=Postgres-XC&diff=10186Postgres-XC2010-03-12T18:38:10Z<p>Masonsharp: /* Project Overview */</p>
<hr />
<div>== Project Overview ==<br />
<br />
Postgres-XC (eXtensible Cluster) is a multi-master write-scalable PostgreSQL cluster based on shared-nothing<br />
architecture, developed by NTT and EnterpriseDB.<br />
<br />
Features of PG-XC includes:<br />
<br />
# Write‐scalable PostgreSQL cluster<br />
#* More than 3.4 performance scalability with five servers, compared with pure PostgreSQL (DBT‐1)<br />
# Synchronous multi‐master configuration<br />
#* Any update to any master is visible from other masters immediately.<br />
# Table location transparent<br />
#* Can continue to use the same applications.<br />
#* No change in transaction handling.<br />
# Based upon PostgreSQL<br />
# Same API to Apps as PostgreSQL<br />
<br />
Introductory material for Postgres-XC can be found in <br />
[[media:Postgres-2_Write-Scalable_Cluster.pdf]].<br />
<br />
<br />
Postgres-XC was formerly known as Postgres-2, but the name was changed due to another project named Postgres-2 being developed by Simon Riggs.<br />
<br />
== Project Status ==<br />
<br />
Now under development.<br />
<br />
* Planned to be available in public by the end of March, 2010.<br />
<br />
== Project Contacts ==<br />
<br />
Developer: Koichi Suzuki, Mason Sharp, Pavan Deolasee, Andrei Martsinchyk, Michael Paquier<br />
<br />
Preferred method of contact: write to pgsql-cluster-hackers@postgresql.org.<br />
<br />
Website link: Not yet available.<br />
<br />
== Google Summer of Code 2010 ==<br />
<br />
We are applying for Google Summer of Code 2010, with the idea list here [[Postgres-XC-GSOC]]<br />
<br />
[[Category:Replication]]<br />
[[Category:Clustering]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=Postgres-XC-GSOC&diff=10185Postgres-XC-GSOC2010-03-12T14:19:04Z<p>Masonsharp: /* Postgres-XC Google Summer of Code 2010 */</p>
<hr />
<div>== Postgres-XC Google Summer of Code 2010 ==<br />
<br />
[[Postgres-2|Postgres-XC]] (previously also known as Postgres-2) is applying for Google Summer of Code 2010.<br />
<br />
The idea list for contributions include:<br />
<br />
* Support for multiple coordinators. Secondary coordinators register with the primary coordinator. DDL (CREATE TABLE, etc.) goes first through primary coordinator, which synchronizes changes amongst the nodes. Long term we also allow for tracking if secondary coordinators are out of date, and for copying over catalog information to the secondaries.<br />
<br />
* Add support for cursors, first for forward only without ORDER BY.<br />
<br />
* Backup & Restore<br />
<br />
* Expand capability of pooler to handle session parameters.<br />
<br />
We prefer to focus on the first item, support for multiple coordinators<br />
<br />
<br />
[[Category:Replication]]<br />
[[Category:Clustering]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=Postgres-2&diff=10184Postgres-22010-03-12T14:12:44Z<p>Masonsharp: </p>
<hr />
<div>== Project Overview ==<br />
<br />
This project has been renamed to [[Postgres-XC]], to avoid a naming conflict with another not-yet open project named Postgres-2 being developed by Simon Riggs. Please now refer to the [[Postgres-XC]] page.<br />
<br />
[[Category:Replication]]<br />
[[Category:Clustering]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=Postgres-XC&diff=10183Postgres-XC2010-03-12T14:10:49Z<p>Masonsharp: New page: == Project Overview == Postgres-XC (eXtensible Cluster) is a multi-master write-scalable PostgreSQL cluster based on shared-nothing architecture, developed by NTT and EnterpriseDB. Featu...</p>
<hr />
<div>== Project Overview ==<br />
<br />
Postgres-XC (eXtensible Cluster) is a multi-master write-scalable PostgreSQL cluster based on shared-nothing<br />
architecture, developed by NTT and EnterpriseDB.<br />
<br />
Features of PG-XC includes:<br />
<br />
# Write‐scalable PostgreSQL cluster<br />
#* More than 3.4 performance scalability with five servers, compared with pure PostgreSQL (DBT‐1)<br />
# Synchronous multi‐master configuration<br />
#* Any update to any master is visible from other masters immediately.<br />
# Table location transparent<br />
#* Can continue to use the same applications.<br />
#* No change in transaction handling.<br />
# Based upon PostgreSQL<br />
# Same API to Apps as PostgreSQL<br />
<br />
Introductory material for Postgres-XC can be found in <br />
[[media:Postgres-2_Write-Scalable_Cluster.pdf]].<br />
<br />
<br />
Postgres-XC was formerly known as Postgres-2, but the name was changed due to not-yet open project named Postgres-2 being developed by Simon Riggs.<br />
<br />
== Project Status ==<br />
<br />
Now under development.<br />
<br />
* Planned to be available in public by the end of March, 2010.<br />
<br />
== Project Contacts ==<br />
<br />
Developer: Koichi Suzuki, Mason Sharp, Pavan Deolasee, Andrei Martsinchyk, Michael Paquier<br />
<br />
Preferred method of contact: write to pgsql-cluster-hackers@postgresql.org.<br />
<br />
Website link: Not yet available.<br />
<br />
== Google Summer of Code 2010 ==<br />
<br />
We are applying for Google Summer of Code 2010, with the idea list here [[Postgres-XC-GSOC]]<br />
<br />
[[Category:Replication]]<br />
[[Category:Clustering]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=Postgres-2&diff=10182Postgres-22010-03-12T14:05:29Z<p>Masonsharp: </p>
<hr />
<div>== Project Overview ==<br />
<br />
Postgres-2 (PG-2) is a multi-master write-scalable PostgreSQL cluster based on shared-nothing<br />
architecture, developed by NTT and EnterpriseDB.<br />
<br />
Feature of PG-2 is as follows:<br />
<br />
# Write‐scalable PostgreSQL cluster<br />
#* More than 3.4 performance scalability with five servers, compared with pure PostgreSQL (DBT‐1)<br />
# Synchronous multi‐master configuration<br />
#* Any update to any master is visible from other masters immediately.<br />
# Table location transparent<br />
#* Can continue to use the same applications.<br />
#* No change in transaction handling.<br />
# Based upon PostgreSQL<br />
# Same API to Apps. as PostgreSQL<br />
<br />
Introductory material for Postgres-2 will be found in <br />
[[media:Postgres-2_Write-Scalable_Cluster.pdf]].<br />
<br />
== Project Status ==<br />
<br />
Now under development.<br />
<br />
* Planned to be available in public by the end of March, 2010.<br />
<br />
== Project Contacts ==<br />
<br />
Developer: Koichi Suzuki, Mason Sharp, Pavan Deolasee, Andrei Martsinchyk, Michael Paquier<br />
<br />
Preferred method of contact: write to pgsql-cluster-hackers@postgresql.org.<br />
<br />
Website link: Not yet available.<br />
<br />
== Google Summer of Code 2010 ==<br />
<br />
We are applying for Google Summer of Code 2010, with the idea list here [[Postgres-XC-GSOC]]<br />
<br />
[[Category:Replication]]<br />
[[Category:Clustering]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=Postgres-XC-GSOC&diff=10181Postgres-XC-GSOC2010-03-12T13:59:46Z<p>Masonsharp: Postgres-XC Google Summer of Code 2010</p>
<hr />
<div>== Postgres-XC Google Summer of Code 2010 ==<br />
<br />
[[Postgres-2|Postgres-XC]] (previously also known as Postgres-2) is applying for Google Summer of Code 2010.<br />
<br />
The idea list for contributions include:<br />
<br />
* Support for multiple Coordinators. Secondary Coordinators register with the Primary Coordinator. DDL (CREATE TABLE, etc.) goes first through primary Coordinator, which synchronizes changes amongst the nodes. Long term we also allow for tracking if secondary coordinators are out of date, and for copying over catalog information to the secondaries.<br />
<br />
* Add support for cursors, first for forward only without ORDER BY.<br />
<br />
* Expand capability of pooler to handle session parameters.<br />
<br />
We prefer to focus on the first item, support for multiple Coordinators<br />
<br />
<br />
[[Category:Replication]]<br />
[[Category:Clustering]]</div>Masonsharphttps://wiki.postgresql.org/index.php?title=PGCon2009JapanClusterDeveloperMeeting&diff=8737PGCon2009JapanClusterDeveloperMeeting2009-11-16T08:29:33Z<p>Masonsharp: Added link to GridSQL</p>
<hr />
<div>== Participants' Input to the Meeting ==<br />
<br />
This is the first PostgreSQL cluster developers meeting. The meeting is held as an associated event of PostgreSQL Conference 2009 Japan. For the detail of the meeting, please visit [http://www.postgresql.jp/events/pgcon09j/e/dev_mtg Call for Participants].<br />
<br />
Participants of the meeting is encouraged to submit inputs to the meeting to this page. Organizational information can be found here: [[PostgreSQL_Conference_2009_Japan]].<br />
<br />
== Links to Information about Clustering Solutions ==<br />
<br />
Please put links here to software, background material, presentations, and other information about your particular clustering software. <br />
<br />
=== Notes On General Design ===<br />
<br />
Both for this page and for your 5-minute presentation, please try to answer the following questions about your current solution:<br />
<br />
* What is the primary use-case your solution is designed for?<br />
* General Design<br />
** What's the general clustering architecture of your software? (e.g. statement replication, shared memory, GCS, clustered table, etc.)<br />
** Does it consist of a collection of tools or a monolithic control-and-management architecture?<br />
** Does your solution supply administration and monitoring tools?<br />
** Is your solution intended to be generic, or does it require the user's application to be built around the clustering architecture?<br />
** Does the solution require patches on core PostgreSQL, or is it entirely external?<br />
* Availability: how does your software deal with uptime availablity?<br />
** Is failover automated?<br />
** Is data synchronous between nodes or asynchrnous?<br />
** What failure conditions can it protect against, and which can't it?<br />
** Does it work over a WAN or do clustered machines have to be in the same data center?<br />
* Scalability: how does your software help with horizontal scaling?<br />
** How does it scale for reads, if at all?<br />
** How does it scale for writes, if at all?<br />
** Is it more designed to scale for many small queries, a few large queries, or for geographic distrubution?<br />
** What kinds of non-simple-query operations (reporting queries, stored procedures, triggers, etc.) can it handle, and which can it not?<br />
* Status: what's the project's current development and adoption status?<br />
** Is it still under active development?<br />
** How mature is it? prototype / beta / first release / second release / in maintenance<br />
** How widely adopted is it? Is it used only by customers of the developers, or by PostgreSQL users in general?<br />
<br />
=== Links ===<br />
<br />
*Some theory:<br />
**[http://www.cs.purdue.edu/homes/bb/cs542-05Spr/ParallelDBMS.ppt Basics about DB clustering] by Tamer Özsu & Patrick Valduriez<br />
<br />
*DB Cluster softwares:<br />
**Slony-I: [http://www.slony.info/documentation/ Documentation]<br />
**pgpool-II: [http://pgpool.projects.postgresql.org/ Home Page]<br />
**pgbouncer: [http://pgbouncer.projects.postgresql.org/ Project Home Page]<br />
**PL/Proxy: [http://pgfoundry.org/projects/plproxy/ PGFoundry Home Page]<br />
**PgCluster: [http://pgfoundry.org/projects/pgcluster/ PGFoundry Home Page]<br />
**Postgres-R: [http://www.postgres-r.org/ Project Home Page] (see esp. the [http://www.postgres-r.org/downloads/concept.pdf concept document] and the [http://www.postgres-r.org/documentation/references references] for related scientific papers)<br />
**PostgresForest: [http://www.nttdata.co.jp/services/postgresforest/ Home Page in Japanese]<br />
**Bucardo: [http://bucardo.org/wiki/Main_Page Project Home Page]<br />
**GridSQL: [http://www.enterprisedb.com/community/projects/gridsql.do#ui-tabs-57 Architecture Page]<br />
**Postgres-2: [http://wiki.postgresql.org/wiki/Postgres-2 Postgres-2 Introduction Page]<br />
<br />
== Clustering Marketplace ==<br />
<br />
What do you think current commercial and user demand for clustering is? Are users trying to get scalability, availability, or other benefits from Clustering? Has interest in clustering waned or grown?<br />
<br />
Josh Says: I've seen the desire for an "Oracle RAC Replacement" is less prominent, at least in the USA, than it was a few years ago. It's possible that folks are realizing that RAC has a lot of drawbacks, or it may just be that I don't talk to Oracle users as much. People seem to be looking more for clustering to help with horizontal scalability, especially to help with performance on cloud hosting platforms, which is a big source of demand now. With MySQL in trouble, people are really looking for an "approximate consistency, low administration" solution to replace MySQL Replication & NDB.<br />
<br />
== Challenges and Issues ==<br />
<br />
What challenges are you currently facing in working on clustering and replication? What things do you think should be different about core Postgres or developed in common?<br />
<br />
== Agenda For Day ==<br />
<br />
Please contribute to this agenda! It is not yet final, but we do need to have a list of items people want to talk about before the meeting itself. If you add an item to the agenda, please put your name next to it so we know who to call to start the item.<br />
<br />
The meeting will run from 9:30AM to 5:30PM.<br />
<br />
=== Introduction ===<br />
<br />
Current clustering definitions, use cases and customer goals (1/2 hour short presentation, Koichi-san and Josh Berkus)<br />
<br />
# User goals<br />
# Specific use cases<br />
# Current market for PostgreSQL clustering<br />
# Competitive market of other DBMSes<br />
<br />
=== Review of Existing Projects ===<br />
<br />
Each project team will be welcome to give a 5-minute presentation about<br />
your current development work on your clustering or replication solution<br />
near the beginning of the event. Note that you are NOT obligated to<br />
give this presentation; if you feel that your current efforts are well<br />
enough known, or if you have no time to prepare, you may choose not to<br />
give a presentation.<br />
<br />
In order to have a productive day, please design your presentation around the following:<br />
* Presentations will be 5 minutes only, strictly timed.<br />
* In order to support (1), presentations will be given on *my* laptop using PDF slides. Please bring a PDF with you to the meeting, or (better) e-mail it to me before the meeting.<br />
* Please discuss *current* work on your software and challenges you are currently facing. Summaries of the history or features of your solution are unnecessary unless they have changed in the last year. Instead, link to these on the wiki.<br />
<br />
Each team which is giving a presentation should sign up below:<br />
<br />
* Postgres-R: Flashlight (Markus Wanner)<br />
<br />
=== Future Requirements and Expectations ===<br />
<br />
Discussion: please add any discussion items you have around the future of database clustering, the demand for it, and user needs around clustering:<br />
<br />
# Common issues to several products<br />
** Usability<br />
** Administration<br />
# Application or industry specific issues<br />
<br />
=== Technical Issues in clustering design ===<br />
<br />
Please add any items you have around specific technical issues in clustering design, especially unsolved or recently solved ones:<br />
<br />
# Challenges<br />
** High Availability<br />
** Scalability (read/write)<br />
# Specifications and APIs<br />
<br />
=== Plans for future development ===<br />
<br />
Please add any items you want to discuss around future development, especially development involving a collaboration between teams or with the general PostgreSQL community.<br />
<br />
# To be developed in core PostgreSQL<br />
** ReplicationHooks -- where did they go?<br />
** Standby/replication (sync/async)/partitioning<br />
** Transaction Management<br />
** APIs and interfaces<br />
** Tools<br />
** (MW) common unit and/or regression testing harness?<br />
** (MW) common benchmark framework?<br />
<br />
# To be developed separately<br />
# Merging clustering projects/products?<br />
<br />
=== Schedule and Map ===<br />
<br />
Meeting Schedule and the map from stations near by will be found in [[Media:Schedule_and_Map.pdf]].<br />
<br />
== Contact Information ==<br />
<br />
Communication for the clustering summit has been on Josh Berkus's clustering@berkus.org mailing list.<br />
<br />
Phone numbers for Koichi Suzuki, Michael Paquier and Josh Berkus have been sent by e-mail. Note that many/most foreign cell phones do not work in Japan.<br />
<br />
Please list below your name and the hotel you are staying at in case we need to find you:<br />
<br />
* Josh Berkus: Shiba Park Hotel<br />
* Bruce Momjian: Park Tokyo Hotel<br />
* Jan Wieck: Park Hotel Tokyo<br />
* Markus Wanner: Shiba Park Hotel<br />
<br />
[[Category:PostgreSQL Events]]</div>Masonsharp