Re: (Comment)Bug in CteScanNext

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: (Comment)Bug in CteScanNext
Date: 2016-09-04 22:58:14
Message-ID: 88b70b80-be5a-064c-155a-0a32a7395890@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/3/16 1:30 PM, Tom Lane wrote:
> Or we could add something like "But first, we must deal with the special
> case of reversing direction after reaching EOF."

I'm working on that, but one thing isn't clear to me... why do we only
skip past the last tuple if (!node->leader->eof_cte)? Even if we've hit
the end of the underlying node, the tuplestore could still return data,
and AFAICT we would still need to move past the last item in the
tuplestore, no?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2016-09-04 23:05:27 Re: \timing interval
Previous Message Jim Nasby 2016-09-04 22:30:57 Minor fix to comments