| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: review: CHECK FUNCTION statement |
| Date: | 2012-03-07 05:35:06 |
| Message-ID: | CAFj8pRBQNLygN3_+LMtw=RvrM6db1o41+qJbf1xF9hQSpgW7Fg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello
I found one small issue where Query was not forwarded when trigger
record was broken. I had to append "context" forwarding.
Regards
Pavel
2012/3/6 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> Hello
>
> there is new version
>
> * fixed small formatting issues related to drop SPI call
> * long functions was divided
> * CREATE TRIGGER ALL ON table support
>
> Regards
>
> Pavel
| Attachment | Content-Type | Size |
|---|---|---|
| check_function-2012-03-07-1.patch.gz | application/x-gzip | 34.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2012-03-07 06:14:57 | Re: Speed dblink using alternate libpq tuple storage |
| Previous Message | Pavel Stehule | 2012-03-07 05:17:07 | Re: poll: CHECK TRIGGER? |