Re: ToDo: fast update of arrays with fixed length fields for PL/pgSQL
| От | Pavel Stehule |
|---|---|
| Тема | Re: ToDo: fast update of arrays with fixed length fields for PL/pgSQL |
| Дата | |
| Msg-id | CAFj8pRB8BFpx9xD43Sf3hAxG_V0bELPnZeWkzuGb3n_MVKr7JA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: ToDo: fast update of arrays with fixed length fields for PL/pgSQL (Andres Freund <andres@2ndquadrant.com>) |
| Ответы |
Re: ToDo: fast update of arrays with fixed length fields for PL/pgSQL
|
| Список | pgsql-hackers |
2013/10/2 Andres Freund <andres@2ndquadrant.com>
Hi,A specific array might be located directly on a buffer - starting to
On 2013-10-02 18:56:51 +0200, Pavel Stehule wrote:
> Hello
>
> this proposal is related to reported issue
> http://www.postgresql.org/message-id/E1VQuta-0007Y4-Ip@wrigleys.postgresql.org
>
>
> We can directly modify any fields of int, float, double arrays (when result
> size will be immutable). This trick is used now for acceleration of some
> aggregates.
>
> Ideas, comments?
manipulate them inplace will lead to havoc in such scenarios. I don't
think we have the infrastructure for detecting such cases.
If you can do a update of some array in plpgsql now, then you have to work with local copy only. It is a necessary precondition, and I am think it is valid.
Pavel
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: