Skip site navigation (1) Skip section navigation (2)

Re: EXECUTE USING for plpgsql (for 8.4)

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>
Subject: Re: EXECUTE USING for plpgsql (for 8.4)
Date: 2007-10-22 15:09:14
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
This has been saved for the 8.4 release:


Pavel Stehule wrote:
> Hello
> this patch add USING clause into plpgsql EXECUTE statements.
> Proposal:
> 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, skipping... ]

> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-patches by date

Next:From: Tom LaneDate: 2007-10-22 17:21:04
Subject: Re: pgstattuple locking fix
Previous:From: Bruce MomjianDate: 2007-10-22 14:50:48
Subject: Re: Hash Index Build Patch v2

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group