Re: Support for Limit in Update, Insert...
От | Cristian Prieto |
---|---|
Тема | Re: Support for Limit in Update, Insert... |
Дата | |
Msg-id | 03f901c5b4dc$8a530ab0$6500a8c0@gt.ClickDiario.local обсуждение исходный текст |
Ответ на | Support for Limit in Update, Insert... ("Cristian Prieto" <cristian@clickdiario.com>) |
Ответы |
Re: Support for Limit in Update, Insert...
|
Список | pgsql-general |
Maybe the first 1000 rows based in the primary index???? ----- Original Message ----- From: "Tom Lane" <tgl@sss.pgh.pa.us> To: "Cristian Prieto" <cristian@clickdiario.com> Cc: <pgsql-general@postgresql.org> Sent: Thursday, September 08, 2005 6:05 PM Subject: Re: [GENERAL] Support for Limit in Update, Insert... > "Cristian Prieto" <cristian@clickdiario.com> writes: >> Would be any future support for limit in update/insert queries? so you = >> could do something like >> update table1 set col1=3Dvalue1 limit 1000; >> would update just the first 1000 rows in the table. > > That seems like a spectacularly bad idea, considering that you could > have no guarantees about *which* 1000 rows get updated. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match
В списке pgsql-general по дате отправления: