Re: 7.4 Wishlist
От | Bruce Momjian |
---|---|
Тема | Re: 7.4 Wishlist |
Дата | |
Msg-id | 200212050621.gB56LCJ29961@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: 7.4 Wishlist (Kevin Brown <kevin@sysexperts.com>) |
Ответы |
Re: 7.4 Wishlist
|
Список | pgsql-hackers |
Kevin Brown wrote: > Christopher Kings-Lynne <chriskl@familyhealth.com.au> wrote: > > Hi guys, > > > > Just out of interest, if someone was going to pay you to hack on Postgres > > for 6 months, what would you like to code for 7.4? > > Well, on top of the oft-requested replication support and savepoint > support, I'd like to see UPDATE, er, updated to be able to make use of > cursors. I think this could be easily done by using the tid of the cursor row for the update, assuming there is a clear tid for the SELECT. Jan has talked about doing that. > I'd also like to see (if this is even possible) a transaction > isolation mode that would make it possible for multiple concurrent > updates to the same row to happen without blocking each other (I > imagine one way to make this possible would be for the last > transaction to commit to be the one that "wins". Each transaction > that commits gets its updates written so that other transactions that > begin after they commit will see them, of course). Neither "read > committed" nor "serialized" modes offer this. Don't know if it's > possible, but it would be nice (such that a transaction sees the > database as if it has it all to itself and doesn't block on > updates)... How would you do the update if you don't know of the transaction commits or aborts? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073
В списке pgsql-hackers по дате отправления: