EXECUTE USING for plpgsql (for 8.4)

From: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
To: pgsql-patches(at)postgresql(dot)org
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Neil Conway" <neilc(at)samurai(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>
Subject: EXECUTE USING for plpgsql (for 8.4)
Date: 2007-10-22 10:48:08
Message-ID: 162867790710220348r39cf9900i6a62c3c56ddb28c9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Hello

this patch add USING clause into plpgsql EXECUTE statements.

Proposal:
http://archives.postgresql.org/pgsql-hackers/2007-10/msg00790.php

I found, so dynamics statements are little bit faster with parameters,
because we don't need call lot of in out/in functions. Mainly it is
barier to SQL injection.

I have question, who will be commiter of plpgsql region? I am quite
irritated from 8.3 process. Bruce's patch queue more or less black
hole, and I have not any idea, if somebody checking my patches or not
and if I have to be in readiness or not.

Patch queue is longer and longer, and I need to know any responsible
person who can be recipient of my reminder request. Really it's
nothing nice, if your work is repeatedly deleted or inserted to
current queue. Nobody can do any plans.

Best regards
Pavel Stehule

Attachment Content-Type Size
execute_using.diff text/x-patch 22.6 KB

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-10-22 14:50:48 Re: Hash Index Build Patch v2
Previous Message Heikki Linnakangas 2007-10-22 10:07:53 Re: pgstattuple locking fix