> > >>>> WAL/write ahead log
> > >>>> TOAST/long tuples
> > >>>> outer joins
> > >>>> query tree redesign
> > >>>> function manager redesign
> > >>>>
> > >>>> What year to we want to release 7.1? :-)
> > > If all will right (and major developers will agree) I plan PREPARE/EXECUTE
> > > commands and changes in SPI background for plan saving (query cache).
> > Given that there is going to be a querytree redesign for 7.1, I'd
> > suggest holding off on prepared plans until 7.2. Otherwise it's
> > going to be a mess.
> Any chance for dirty read? Waiting for transaction end on inserts with
> duplicates on unique keys in transactions can be a lot of fun.
But we have committed read with no block. Why would you want dirty
read. Chapter 10 of my book is about transactions and locking. Of
course, I may be missing something here.
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
In response to
pgsql-hackers by date
|Next:||From: Karel Zak||Date: 2000-04-06 16:02:27|
|Subject: Re: 7.1 items |
|Previous:||From: Bruce Momjian||Date: 2000-04-06 15:58:53|
|Subject: Temporary indexes|