| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| 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:43:59 |
| Message-ID: | 14086.1459727039@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Corey Huinker <corey(dot)huinker(at)gmail(dot)com> writes:
>>> + 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?
Meh, I suspect a lot of people don't know that term. Perhaps something
like "The generated queries are executed in the order in which the rows
are returned, and left-to-right within each row if there is more than one
column."
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Shulgin | 2016-04-03 23:47:13 | Re: More stable query plans via more predictable column statistics |
| Previous Message | Dave Cramer | 2016-04-03 23:34:32 | Re: Proposal: RETURNING primary_key() |