| From: | Kenneth Downs <ken(at)secdat(dot)com> |
|---|---|
| To: | Rafal Pietrak <rafal(at)zorro(dot)isa-geek(dot)com> |
| Cc: | Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: background triggers? |
| Date: | 2006-05-23 17:01:01 |
| Message-ID: | 44733FCD.4010809@secdat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Rafal Pietrak wrote:
>So if I may re-phrase the question: "is there a way to have a trigger,
>that, when launched, can check if it's already running in backgroung for
>some other INSERT, return imediately if so, but turn into background for
>a long-lasting job if not".
>
>
>
Rafal, I'm wondering why you want to do this. You may be "fighting the
framework".
If you are trying to do something that is totally unsupported, it is
probably for a pretty good reason, usually dealing with security or data
loss. You can probably get what you want by supported methods, but it
may require looking at the problem in a different way.
What is it you are trying to accomplish? Is it just performance?
| Attachment | Content-Type | Size |
|---|---|---|
| ken.vcf | text/x-vcard | 186 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yonatan Ben-Nes | 2006-05-23 17:13:08 | Trying to update a box data type column |
| Previous Message | Bob Pawley | 2006-05-23 16:56:01 | Re: Interface |