From: | Selena Deckelmann <selena(at)chesnok(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: plpgsql_check_function - rebase for 9.3 |
Date: | 2012-10-07 00:07:01 |
Message-ID: | CAN1EF+zH8FUzs6FqnbA3fGJAbBRaOb5HSKAp5nKcD1KL0jHVbQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi!
On Tue, Jun 26, 2012 at 1:19 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> I am sending lightly refreshed patch for checking plpgsql functions..
>
> I checked different implementation, but without success: a) enhancing
> of SPI to some fake mode can has negative impact on application, and
> patch was not clear, b) generic plpgsql walker doesn't save lines too.
>
> I invite any ideas how to improve this patch
I reviewed this and did a clean up for bitrot and a little whitespace.
In particular, it needed to learn a little about event triggers.
This patch is a follow on from an earlier review thread I found:
http://archives.postgresql.org/message-id/D960CB61B694CF459DCFB4B0128514C2072DF447@exadv11.host.magwien.gv.at
I dug through that thread a bit, and I believe issues raised by
Laurenz, Petr and Alvaro were resolved by Pavel over time.
All tests pass, and after a read-through, the code seems fine.
This also represents my inaugural use of pg_bsd_indent. I ran it on
pl_check.c - which made things mostly better. Happy to try and fix it
up more if someone can explain to me what (if anything) I did
incorrectly when using it.
-selena
Attachment | Content-Type | Size |
---|---|---|
plpgsql_check_function-20121006.patch | application/octet-stream | 97.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2012-10-07 00:12:20 | Re: 64-bit API for large object |
Previous Message | Tom Lane | 2012-10-06 21:47:11 | Re: Regarding identifying a foreign scan |