Thread: Cluster meeting?
Are we going to have a cluster meeting in Ottawa this year? Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp
NTT may have some info on this. Sorry, I'm not involved at present. --- Koichi Suzuki NTT DATA Intellilink Corporation ________________________________________ 差出人: pgsql-cluster-hackers-owner@postgresql.org [pgsql-cluster-hackers-owner@postgresql.org] が Tatsuo Ishii [ishii@postgresql.org]の代理で送信しました 送信日時: 2015年1月23日 14:00 宛先: pgsql-cluster-hackers@postgresql.org 件名: [pgsql-cluster-hackers] Cluster meeting? Are we going to have a cluster meeting in Ottawa this year? Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp -- Sent via pgsql-cluster-hackers mailing list (pgsql-cluster-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-cluster-hackers
> Are we going to have a cluster meeting in Ottawa this year? Yes, we are. There are some schedule changes to the Developer Meeting being proposed, and I will need to schedule around that. But the plan is to have one. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
On 01/23/2015 01:32 PM, Josh Berkus wrote: > >> Are we going to have a cluster meeting in Ottawa this year? > > Yes, we are. There are some schedule changes to the Developer Meeting > being proposed, and I will need to schedule around that. But the plan > is to have one. Expect this meeting to be on Wednesday of pgCon week, rather than Tuesday as in the past. Final confirmation of the new schedule in 1 week. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
Does anybody know the Developer Meeting schedule was fixed or not? Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp > On 01/23/2015 01:32 PM, Josh Berkus wrote: >> >>> Are we going to have a cluster meeting in Ottawa this year? >> >> Yes, we are. There are some schedule changes to the Developer Meeting >> being proposed, and I will need to schedule around that. But the plan >> is to have one. > > Expect this meeting to be on Wednesday of pgCon week, rather than > Tuesday as in the past. Final confirmation of the new schedule in 1 week. > > -- > Josh Berkus > PostgreSQL Experts Inc. > http://pgexperts.com
On Mon, Mar 30, 2015 at 10:29 PM, Tatsuo Ishii <ishii@postgresql.org> wrote: > Does anybody know the Developer Meeting schedule was fixed or not? There will be a closed developer meeting on Tuesday morning. Instead of spending a whole day doing a closed developer meeting as we have in the past, we will instead have a half-day closed session and then switch to an unconference format for Tuesday afternoon and all of Wednesday. So, depending on your point of view, the developer meeting is either half as long as before (half a day instead of all day) or twice as long as before (two days instead of one day). I suggest that it would be best to integrate the cluster summit into the unconference time. In the unconference format, the schedule is not determined in advance; rather, it is determined at the event. We will ask those attending the unconference what topics they wish to talk about. Then, we will ask those in attendance which talks they wish to attend. The talks that are popular will be assigned a room from among the three allocated to the unconference. The talks that few or no attendees wish to attend won't be assigned a room, and thus won't happen. I think this format offers several advantages. On the one hand, I expect the unconference to include a large number of the senior PostgreSQL developers, and so clustering-related topics which are of interest may attract the attention of senior hackers who have not gone to the cluster summit in the past. On the other hand, both the developer meeting and the cluster summit have the problem that time is sometimes allocated to topics in which there is not much interest, because the organizers do not want to say "no" to anyone. The unconference format will help us to solve this problem by asking attendees to vote, not just on the clustering topics, but on all the topics. People will not need to decide between attending the cluster summit and skipping it; they can decide to attend sessions on the specific topics they want to hear about. Ultimately, I think it is very important to integrate "cluster hacking" back into "PostgreSQL hacking". This mailing list (pgsql-cluster-hackers) is all but dead. Meanwhile, interesting cluster work is being done on pgsql-hackers (see commit cb1ca4d800621dcae67ca6c799006de99fa4f0a5 and https://commitfest.postgresql.org/4/161/ among other examples). We need to stop thinking of clustering as something that is going to happen only outside of PostgreSQL core and begin thinking of it as an integral part of the work that we need to do to make PostgreSQL successful. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On Wed, Apr 1, 2015 at 01:07:35PM -0400, Robert Haas wrote: > Ultimately, I think it is very important to integrate "cluster > hacking" back into "PostgreSQL hacking". This mailing list > (pgsql-cluster-hackers) is all but dead. Meanwhile, interesting > cluster work is being done on pgsql-hackers (see commit > cb1ca4d800621dcae67ca6c799006de99fa4f0a5 and > https://commitfest.postgresql.org/4/161/ among other examples). We > need to stop thinking of clustering as something that is going to > happen only outside of PostgreSQL core and begin thinking of it as an > integral part of the work that we need to do to make PostgreSQL > successful. Agreed. See my sharding presentation for an overview of a possible approach: http://momjian.us/main/presentations/overview.html#sharding -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. +
> There will be a closed developer meeting on Tuesday morning. Instead > of spending a whole day doing a closed developer meeting as we have in > the past, we will instead have a half-day closed session and then > switch to an unconference format for Tuesday afternoon and all of > Wednesday. So, depending on your point of view, the developer meeting > is either half as long as before (half a day instead of all day) or > twice as long as before (two days instead of one day). > > I suggest that it would be best to integrate the cluster summit into > the unconference time. In the unconference format, the schedule is > not determined in advance; rather, it is determined at the event. We > will ask those attending the unconference what topics they wish to > talk about. Then, we will ask those in attendance which talks they > wish to attend. The talks that are popular will be assigned a room > from among the three allocated to the unconference. The talks that > few or no attendees wish to attend won't be assigned a room, and thus > won't happen. > > I think this format offers several advantages. On the one hand, I > expect the unconference to include a large number of the senior > PostgreSQL developers, and so clustering-related topics which are of > interest may attract the attention of senior hackers who have not gone > to the cluster summit in the past. On the other hand, both the > developer meeting and the cluster summit have the problem that time is > sometimes allocated to topics in which there is not much interest, > because the organizers do not want to say "no" to anyone. The > unconference format will help us to solve this problem by asking > attendees to vote, not just on the clustering topics, but on all the > topics. People will not need to decide between attending the cluster > summit and skipping it; they can decide to attend sessions on the > specific topics they want to hear about. Thanks for the input. I will talk to NTT people and reply back if it is allowed. > Ultimately, I think it is very important to integrate "cluster > hacking" back into "PostgreSQL hacking". This mailing list > (pgsql-cluster-hackers) is all but dead. Meanwhile, interesting > cluster work is being done on pgsql-hackers (see commit > cb1ca4d800621dcae67ca6c799006de99fa4f0a5 and > https://commitfest.postgresql.org/4/161/ among other examples). We > need to stop thinking of clustering as something that is going to > happen only outside of PostgreSQL core and begin thinking of it as an > integral part of the work that we need to do to make PostgreSQL > successful. Well I think it depends on the definition of "cluster hacking". For example, the most common reason people want to use pgpool-II are query dispatching, automatic fail over and read query load balancing (plus connection pooling sometimes). That means without these PostgreSQL will not succeed in the real world IMO. But most PostgreSQL developers tend to think that they are not part of "cluster hacking", and they seem to want to avoid integrating them into PostgreSQL core. Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp
On 04/01/2015 10:07 AM, Robert Haas wrote: > I suggest that it would be best to integrate the cluster summit into > the unconference time. In the unconference format, the schedule is This is the current plan. The "Cluster Track" will be on Tuesday afternoon and Wednesday, as part of the general Developer Unconference. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
> On 04/01/2015 10:07 AM, Robert Haas wrote: >> I suggest that it would be best to integrate the cluster summit into >> the unconference time. In the unconference format, the schedule is > > This is the current plan. The "Cluster Track" will be on Tuesday > afternoon and Wednesday, as part of the general Developer Unconference. Ok, there will be no closed cluster summit this year. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp
>> Ok, there will be no closed cluster summit this year. > > Cluster Summit is an alias of the Cluster Track this year. > NTT supports this event as before, and expects more participants. I'm a little bit confused. Robert said: > because the organizers do not want to say "no" to anyone. The > unconference format will help us to solve this problem by asking > attendees to vote, not just on the clustering topics, but on all the > topics. People will not need to decide between attending the cluster > summit and skipping it; they can decide to attend sessions on the > specific topics they want to hear about. So In my understanding, there's no pre-reserved tracks in the unconference for particular topic since people can vote "no" to the if they have no interest in the cluster topics. Or a room will be reserved for cluster topics only in Wednesday afternoon? Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp
(My previous message to the ML is stalled, since I posted it from unregisterd address. I include it here.) > Cluster Summit is an alias of the Cluster Track this year. > NTT supports this event as before, and expects more participants. Since last year's Cluster Summit attracted many participants (27 in RSVP list, and much more in actual), we can expect same in this year. In general, unconference topics will be selected on site. But if many people express intent to participate it previously, a track dedicated to cluster might be pre-reserved. How do you think about, Josh? Anyway, NTT, which will co-sponser unconference sessions this year, has already planned the Cluster Summit 2015 as usual. Josh is kindly doing the organizing work. -- Hemmi On 2015/04/02 11:48, Tatsuo Ishii wrote: >>> Ok, there will be no closed cluster summit this year. >> Cluster Summit is an alias of the Cluster Track this year. >> NTT supports this event as before, and expects more participants. > I'm a little bit confused. > > Robert said: >> because the organizers do not want to say "no" to anyone. The >> unconference format will help us to solve this problem by asking >> attendees to vote, not just on the clustering topics, but on all the >> topics. People will not need to decide between attending the cluster >> summit and skipping it; they can decide to attend sessions on the >> specific topics they want to hear about. > So In my understanding, there's no pre-reserved tracks in the > unconference for particular topic since people can vote "no" to the if > they have no interest in the cluster topics. > > Or a room will be reserved for cluster topics only in Wednesday > afternoon? > > Best regards, > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese:http://www.sraoss.co.jp > >
>> Cluster Summit is an alias of the Cluster Track this year. >> NTT supports this event as before, and expects more participants. > > Since last year's Cluster Summit attracted many participants (27 in > RSVP list, > and much more in actual), we can expect same in this year. > In general, unconference topics will be selected on site. But if many > people > express intent to participate it previously, a track dedicated to > cluster > might be pre-reserved. > How do you think about, Josh? > Anyway, NTT, which will co-sponser unconference sessions this year, > has already planned > the Cluster Summit 2015 as usual. > Josh is kindly doing the organizing work. Thanks for the input. I'll wait and see what will happen. Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp
On 04/02/2015 12:28 AM, Hitoshi HEMMI wrote: > Since last year's Cluster Summit attracted many participants (27 in RSVP > list, > and much more in actual), we can expect same in this year. > In general, unconference topics will be selected on site. But if many > people > express intent to participate it previously, a track dedicated to cluster > might be pre-reserved. > How do you think about, Josh? > Anyway, NTT, which will co-sponser unconference sessions this year, has > already planned > the Cluster Summit 2015 as usual. > Josh is kindly doing the organizing work. Yes, my plan is to set up a wiki page where people can suggest topics in advance. Particularly, we'll want to coordinate for items which include meetings of dev teams, such as the Postgres-XC development team. Stay tuned. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com