From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | theo(at)flame(dot)co(dot)za |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 7.1 items |
Date: | 2000-04-06 16:00:08 |
Message-ID: | 200004061600.MAA21583@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > >>>> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak | 2000-04-06 16:02:27 | Re: 7.1 items |
Previous Message | Bruce Momjian | 2000-04-06 15:58:53 | Temporary indexes |