> >>>> 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.
In response to
pgsql-hackers by date
|Next:||From: Karel Zak||Date: 2000-04-06 16:17:49|
|Subject: Re: pg_dumplo, thanks :) (fwd)|
|Previous:||From: Vince Vielhaber||Date: 2000-04-06 16:07:53|
|Subject: Re: pg_dump and serial |