| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Petr Jelinek <pjmodos(at)pjmodos(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: USING clause for DO statement |
| Date: | 2009-11-21 20:18:31 |
| Message-ID: | 4B084B17.10107@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> In any case I don't think that "getting stuff from
> psql variables into a DO script" is the way to define the problem.
> It's "getting stuff from shell variables into a DO script" that is the
> real-world problem.
Indeed. But setting psql variables from the command line is easy. We
have a nifty switch for it. So we could reduce one problem to the other.
> Maybe psql is the wrong tool altogether.
>
>
>
Yeah. The workaround is to use some sort of wrapper, in shell script,
perl or whatever. Maybe we should just let sleeping dogs lie.
I think you and I are in agreement though that an SQL level mechanism is
not the way to go, at least for now.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2009-11-21 20:18:33 | Re: ecpg & 8.3 -> 8.4 migration |
| Previous Message | Tom Lane | 2009-11-21 20:14:03 | Re: Proposal: USING clause for DO statement |