| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, John Adams <john_adams_mail(at)yahoo(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: returning multiple result sets from a stored procedure |
| Date: | 2010-09-09 18:43:44 |
| Message-ID: | AANLkTimDURGDwuykoQQQ2tfcJsFq6_x7qBKhjpTUoMQa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2010/9/9 Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
> Excerpts from Pavel Stehule's message of jue sep 09 14:29:57 -0400 2010:
>
>> * how can be implemented OUT variables - the original implementation
>> is simple - it's just pointer, but it's not directly possible inside
>> postgres, because we use a MemoryContexts?
>
> Why is this a problem? Just return a bunch of tuplestores, no?
and what context do you use? And you will pack and unpack tuple when
some field will be changed every time?
this is an possibility to solve our performance problems with arrays
or strings.
Regards
Pavel Stehule
>
> --
> Álvaro Herrera <alvherre(at)commandprompt(dot)com>
> The PostgreSQL Company - Command Prompt, Inc.
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-09-09 19:00:04 | Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session |
| Previous Message | Alvaro Herrera | 2010-09-09 18:37:39 | Re: returning multiple result sets from a stored procedure |