From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Andy Colson <andy(at)squeakycode(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How does one make the following psql statement sql-injection resilient? |
Date: | 2015-03-17 04:31:04 |
Message-ID: | CAKFQuwZas=frYrn_ASH8JsTDNT5HDcx0i_bGaKWzzQRhtVxS5g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Monday, March 16, 2015, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> David G. Johnston wrote:
>
> > Thanks! I got the gist even with the typo. I actually pondered about
> > prepare/execute after hitting send. Am I correct in remembering that
> > "CREATE TEMP TABLE" cannot be prepared? I was using the actual query
> with
> > CREATE TEMP TABLE and then issuing "\copy" to dump the result out to the
> > file. The limitation of copy to having to be written on a single line
> > makes the intermediary temporary table seem almost a necessity.
>
> CREATE TEMP TABLE AS EXECUTE
>
>
Thanks.
Though unless I need to work on the temp table I think:
PREPARE ...;
\copy (EXECUTE ...) TO '~/temp.csv' ...;
Gives the best of all worlds.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Ruth Melendo | 2015-03-17 07:12:52 | Re: [ADMIN] pgpool + BDR, is it possible? |
Previous Message | Craig Ringer | 2015-03-17 03:59:48 | Re: Postgresql BDR(Bi-Directional Replication) Latency Monitoring |