| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> |
| Cc: | Steve Singer <ssinger_pg(at)sympatico(dot)ca>, pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: Review: Fix snapshot taking inconsistencies |
| Date: | 2011-02-28 19:03:43 |
| Message-ID: | 27598.1298919823@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> writes:
> On 2011-02-28 8:22 PM, Tom Lane wrote:
>> So: exactly what is the intended behavioral change as of now, and what
>> is the argument supporting that change?
> The only intended change is what I was wondering in the original post:
> snapshot handling between normal execution and EXPLAIN ANALYZE when a
> query expands to multiple trees because of rewrite rules. Like I said
> earlier, this is just a bugfix now that wCTEs don't need it anymore.
OK, and which behavior is getting changed, to what? I am not interested
in trying to reverse-engineer a specification from the patch.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-02-28 19:14:59 | Re: Review: Fix snapshot taking inconsistencies |
| Previous Message | Tom Lane | 2011-02-28 19:01:15 | Re: Review: Fix snapshot taking inconsistencies |