Re: Explain buffers wrong counter with parallel plans

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Explain buffers wrong counter with parallel plans
Date: 2018-08-01 15:20:20
Message-ID: 25683.1533136820@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Looking at it, this sounds suspiciously something where we could just
> test EXEC_FLAG_BACKWARD, based on the comments for that flag, but I
> wouldn't be willing to bet very much on me being right about that.
> Can somebody try to fetch backward even if this flag wasn't provided?

They're not supposed to, and it would be a bug of theirs not yours
if they did. Other node types that rely on eflags being provided
honestly generally just Assert that they're not asked for something
else later.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marco van Eck 2018-08-01 15:33:39 Re: Have an encrypted pgpass file
Previous Message Cynthia Shang 2018-08-01 15:18:04 Re: Allow COPY's 'text' format to output a header