Re: [HACKERS] PostgreSQL Anniversary Proposals -- Important Update

2006-04-04 Thread Josh Berkus
Tatsuo, I'm wondering if this was approved or not... We haven't approved *anything* yet. The deadline was just Saturday, and I'm still keying stuff into the conference management system. -- Josh Berkus Aglio Database Solutions San Francisco ---(end of

Re: [pgsql-advocacy] [HACKERS] PostgreSQL Anniversary Proposals --Important Update

2006-03-20 Thread Dave Page
-Original Message- From: Devrim GUNDUZ [mailto:[EMAIL PROTECTED] Sent: 19 March 2006 23:08 To: Josh Berkus Cc: [EMAIL PROTECTED]; Dave Page; pgsql-hackers@postgresql.org Subject: Re: [pgsql-advocacy] [HACKERS] PostgreSQL Anniversary Proposals --Important Update Hi

Re: [pgsql-advocacy] [HACKERS] PostgreSQL Anniversary Proposals --Important Update

2006-03-20 Thread Magnus Hagander
Well, aside from anything else, we seem likely to have you, Devrim, Magnus and maybe even Robert Treat there (Robert?). Which would mean a good time for a meeting of the Web Team, yes? It seems that I'll be there, and yes, a PostgreSQL.org web development session will be

Re: [pgsql-advocacy] [HACKERS] PostgreSQL Anniversary Proposals --Important Update

2006-03-20 Thread Dave Page
-Original Message- From: Magnus Hagander [mailto:[EMAIL PROTECTED] Sent: 20 March 2006 08:31 To: Dave Page; Devrim GUNDUZ; Josh Berkus Cc: [EMAIL PROTECTED]; pgsql-hackers@postgresql.org Subject: RE: [pgsql-advocacy] [HACKERS] PostgreSQL Anniversary Proposals --Important Update

Re: [pgsql-advocacy] [HACKERS] PostgreSQL Anniversary Proposals --Important Update

2006-03-20 Thread Robert Treat
On Monday 20 March 2006 03:31, Magnus Hagander wrote: Well, aside from anything else, we seem likely to have you, Devrim, Magnus and maybe even Robert Treat there (Robert?). Which would mean a good time for a meeting of the Web Team, yes? It seems that I'll be

Re: [HACKERS] PostgreSQL Anniversary Proposals -- Important Update

2006-03-20 Thread Jim C. Nasby
On Sat, Mar 18, 2006 at 12:38:30PM -0500, Rod Taylor wrote: One example might be a 'self-aggregating' structure. Start with one entry per minute in a table indexed by time. After 2 weeks passes, the per-minute data is aggregated and the single entry at the start of the day is updated with the

Re: [pgsql-advocacy] [HACKERS] PostgreSQL Anniversary Proposals -- Important Update

2006-03-19 Thread Josh Berkus
Dave, I wouldn't mind talking (or hosting a discussion) but have been unable to think of anything that other hackers might be interested in. I obviously can't discuss the server internals in any great depth, but if anyone wants to hear about pgadmin, pginstaller, the web infrastructure or

Re: [HACKERS] PostgreSQL Anniversary Proposals -- Important Update

2006-03-19 Thread Qingqing Zhou
Tom Lane [EMAIL PROTECTED] wrote Hm, I already talked about that once: http://www.postgresql.org/files/developer/transactions.pdf but perhaps that's not the level of detail you are after? Yeah, I've read the presentation -- and yes, that's not the level I am after. Actually, I guess the

Re: [HACKERS] PostgreSQL Anniversary Proposals -- Important Update

2006-03-18 Thread Dave Page
-Original Message- From: Josh Berkusjosh@agliodbs.com Sent: 18/03/06 01:55:04 To: pgsql-hackers@postgresql.orgpgsql-hackers@postgresql.org Cc: [EMAIL PROTECTED][EMAIL PROTECTED] Subject: [HACKERS] PostgreSQL Anniversary Proposals -- Important Update Heck, if you have an idea

Re: [HACKERS] PostgreSQL Anniversary Proposals -- Important Update

2006-03-18 Thread Rod Taylor
On Fri, 2006-03-17 at 22:03 -0500, Tom Lane wrote: Josh Berkus josh@agliodbs.com writes: -- There are only 13 days left to submit a proposal. Please do so. We'd rather not be forced into a last-minute rush to evaluate all of the stuff in April. Remember this is a family event so you

Re: [HACKERS] PostgreSQL Anniversary Proposals -- Important Update

2006-03-18 Thread Hannu Krosing
Ühel kenal päeval, L, 2006-03-18 kell 12:38, kirjutas Rod Taylor: This will, presumably, be a very PostgreSQL friendly group so a sales pitch isn't really required. How about the opposite? Tom Lanes list of areas that PostgreSQL does a poor job and a detailed explanation as to how that

Re: [HACKERS] PostgreSQL Anniversary Proposals -- Important Update

2006-03-18 Thread Alvaro Herrera
Qingqing Zhou wrote: I am really interested in the concurrency control part of the PostgreSQL. I can see the MVCC/lock rules there, and basically I can follow them -- but there are so many if-else in the rules, so the problem always for me is: how can we gaurantee that the rules are complete

[HACKERS] PostgreSQL Anniversary Proposals -- Important Update

2006-03-17 Thread Josh Berkus
Folks, Wanted to update you on a few things regarding speaking at the upcoming PostgreSQL Anniversary Summit: -- There are only 13 days left to submit a proposal. Please do so. We'd rather not be forced into a last-minute rush to evaluate all of the stuff in April. Remember this is a

Re: [HACKERS] PostgreSQL Anniversary Proposals -- Important Update

2006-03-17 Thread Tom Lane
Josh Berkus josh@agliodbs.com writes: -- There are only 13 days left to submit a proposal. Please do so. We'd rather not be forced into a last-minute rush to evaluate all of the stuff in April. Remember this is a family event so you don't have to have all of your materials together

Re: [HACKERS] PostgreSQL Anniversary Proposals -- Important Update

2006-03-17 Thread Qingqing Zhou
Tom Lane [EMAIL PROTECTED] wrote What would people like to hear about? I am really interested in the concurrency control part of the PostgreSQL. I can see the MVCC/lock rules there, and basically I can follow them -- but there are so many if-else in the rules, so the problem always for me is:

Re: [HACKERS] PostgreSQL Anniversary Proposals -- Important Update

2006-03-17 Thread Tom Lane
Qingqing Zhou [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] wrote What would people like to hear about? I am really interested in the concurrency control part of the PostgreSQL. Hm, I already talked about that once: http://www.postgresql.org/files/developer/transactions.pdf but perhaps