Re: Guidance on INSERT RETURNING order
От | Mike Bayer |
---|---|
Тема | Re: Guidance on INSERT RETURNING order |
Дата | |
Msg-id | 86f9eae7-acd6-45e7-b8a6-2a24b42fe306@app.fastmail.com обсуждение исходный текст |
Ответ на | Re: Guidance on INSERT RETURNING order (Thorsten Glaser <tg@evolvis.org>) |
Ответы |
Re: Guidance on INSERT RETURNING order
|
Список | pgsql-general |
We do something different for uuids. These are usually created client side anyway or are very easy to create client sideif not and then we also have a separate sentinel column option. Overall the whole thing is an optimization that can be turned off for uncommon cases. We just can't go back to having insertof 1000 rows be 3-5x slower for all tables w server generated primary keys which is what statement at a time gets us. Surrogate integer Pks w sequence or identity is the big case. On Wed, Apr 12, 2023, at 8:58 PM, Thorsten Glaser wrote: > On Wed, 12 Apr 2023, Mike Bayer wrote: > >>ascending values for "mytable_id_seq" will correspond to the ascending >>values for "num". > > But, again, what if it’s uuid or something instead of a sequence? > > bye, > //mirabilos > -- > 15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)
В списке pgsql-general по дате отправления: