From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, PostgreSQL <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql metaqueries with \gexec |
Date: | 2016-04-03 23:34:03 |
Message-ID: | CADkLM=dqTh2f78j_SynK-r=_=jca_Ohj1+jvXph3mZ6ZbO8bHw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> + The secondary queries are executed in top-to-bottom,
> left-to-right order, so the command
>
> I took that as meaning what I said above.
>
>
Would using the term https://en.wikipedia.org/wiki/Row-major_order be more
clear?
The secondary queries are executed in row-major order, so the
command...
If so, it will probably aide in translation as well.
> >> It should clear that in all the same
> >> places where gfname or gset_prefix get cleared.
>
> > I'm only seeing one place where those two vars are deallocated and
> nulled,
> > and that's at the tail end of SendQuery. Were you expecting more than
> just
> > that?
>
> That may be the only place; I've not looked around.
>
Yeah, seems that there might have been multiple ones in the past, but all
paths now funnel through the sendquery_cleanup: goto.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2016-04-03 23:34:32 | Re: Proposal: RETURNING primary_key() |
Previous Message | Dave Cramer | 2016-04-03 23:33:03 | Re: Proposal: RETURNING primary_key() |