| From: | Darren Duncan <darren(at)darrenduncan(dot)net> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: how to start a procedure after postgresql started. |
| Date: | 2011-05-23 02:24:35 |
| Message-ID: | 4DD9C563.3060206@darrenduncan.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
John R Pierce wrote:
> On 05/22/11 10:45 AM, Darren Duncan wrote:
>> Absolutely. But if the kind of stored procedures were supported that
>> can do anything a database client can do, including transaction
>> control statements, then the main program routine would typically be
>> one of those.
>
> yes, but postgres doesn't support the idea of stored procedures callable
> outside of transactions, so I don't know how this could be implemented
> without some major rework of the core engine.
Well, one can dream. I also anticipate that this limitation will be gone some
day. I may even help remove it some day if it comes to that. -- Darren Duncan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2011-05-23 02:40:24 | Re: Fwd: how to start a procedure after postgresql started. |
| Previous Message | jun yang | 2011-05-23 02:14:04 | Fwd: how to start a procedure after postgresql started. |