X-Original-To: pgsql-hackers@postgresql.org Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 70646475C15; Mon, 10 Mar 2003 14:17:17 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h2AJHHub019174; Mon, 10 Mar 2003 14:17:17 -0500 (EST) To: Justin Clift Cc: pgsql-hackers@postgresql.org Subject: Re: Roadmap for FE/BE protocol redesign In-reply-to: <3E6CE1F2.8030302@postgresql.org> References: <19041.1047322279@sss.pgh.pa.us> <3E6CE1F2.8030302@postgresql.org> Comments: In-reply-to Justin Clift message dated "Tue, 11 Mar 2003 05:35:22 +1030" Date: Mon, 10 Mar 2003 14:17:17 -0500 Message-ID: <19173.1047323837@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/368 X-Sequence-Number: 36614 Justin Clift writes: > The scenario that's appealing to me the most is this for the next release: > PostgreSQL 8.0 > + Includes PITR and the Win32 port If the folks doing those things can get done in time, great. I'm even willing to push out the release schedule (now, not later) to make it more likely they can get done. What I'm not willing to do is define the release in terms of "it happens when these things are done". We learned the folly of that approach in 7.1 and 7.2. Setting a target date and sticking to it works *much* better. > + Not sure where Satoshi is up to with his 2 phase commit proposal, but > that might make sense to incorporate into a wire protocol revision. I can't see any need for protocol-level support for such a thing. Why wouldn't it just be some more SQL commands? (Not that I believe in 2PC as a real-world solution anyway, but that's a different argument...) regards, tom lane