Thread: Re: [HACKERS] Status report: long-query-string changes
--- Tom Lane <tgl@sss.pgh.pa.us> wrote: > Thomas Lockhart <lockhart@alumni.caltech.edu> > writes: > > Though it drove me nuts earlier, resisting the > temptation to cast into > > concrete a short- or medium-range plan has been a > real plus for the > > project as a whole. > > The facts of the matter are that contributors work > on the problems that > they find interesting, and/or the things that are > getting in the way of > their own use of Postgres at the moment. .... > Indeed, the TODO list is awfully bare-bones; many of > the entries don't > convey much information to someone who's not already > familiar with the > issue. Something more fleshed-out would be a useful > project. > > regards, tom lane >From someone who lurks in this list to see what's upcoming in future releases, I have a couple of comments (which may be politically incorrect): 1. The TODO list shows under ENHANCEMENTS as URGENT as the number one item referential integrity. This is something we need desperately. And since refint.c with MVCC requires recoding our application (which is composed of 115 C++ objects -- and those are just the database related ones), we've been looking forward to integrated referential integrity. Particularly since refint.c is broke for cascading updates (it saves the SPI plan). The TODO list shows Jan as having claimed this item -- perhaps he goes away working like mad and comes back with a fantastic feature, like the rules system -- but I haven't seen any posts by Jan in months. 2. How is it that Tom Lane isn't considered "core"? Sorry to stir the pot...but I was just curious, Mike Mascari (mascarim@yahoo.com) __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com
Mike Mascari wrote: > > 1. The TODO list shows under ENHANCEMENTS as URGENT as > the number one item referential integrity. This is > something we need desperately. And since refint.c > with MVCC requires recoding our application (which is > composed of 115 C++ objects -- and those are just the > database related ones), we've been looking forward > to integrated referential integrity. Particularly > since refint.c is broke for cascading updates (it > saves the SPI plan). The TODO list shows Jan as having > claimed this item -- perhaps he goes away working like > mad and comes back with a fantastic feature, like the > rules system -- but I haven't seen any posts by Jan > in months. I would like to see something from Jan too... My opinion is that RI _MUST_ be implemented in 6.6. There are 3 ways: 1. Using deferrable rules/statement level triggers. 2. Using transaction log (to read changes made in parent/child tables and check RI constraints). 3. Using DIRTY READ in refint.c I hope to be able to do 2. or 3., though it would be much better to have 1. (with statement level triggers) implemented by Jan. Vadim
Mike Mascari <mascarim@yahoo.com> writes:
> 2. How is it that Tom Lane isn't considered "core"?
The core guys have been here a lot longer. I've only been
working with Postgres for a year or so.
There are quite a few major contributors besides the core four,
actually.
regards, tom lane
> I would like to see something from Jan too... > My opinion is that RI _MUST_ be implemented in 6.6. > There are 3 ways: > > 1. Using deferrable rules/statement level triggers. > 2. Using transaction log (to read changes made in > parent/child tables and check RI constraints). > 3. Using DIRTY READ in refint.c > > I hope to be able to do 2. or 3., though it would be much > better to have 1. (with statement level triggers) implemented by Jan. Uh, oh. Vadim has thrown down the hachet on a 6.6 _must_ _have_ item. (I agree with him, but am glad I didn't have to do it.) -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
> Mike Mascari <mascarim@yahoo.com> writes: > > 2. How is it that Tom Lane isn't considered "core"? > > The core guys have been here a lot longer. I've only been > working with Postgres for a year or so. > > There are quite a few major contributors besides the core four, > actually. I have renamed the Core group to "Founders" on the web site, and changed "Other Major Code Developers" to "Major Code Developers". -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026