From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Johnston <polobo(at)yahoo(dot)com> |
Cc: | Chris <dmagick(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: recursive query returning extra rows in 8.4 |
Date: | 2013-10-15 14:56:27 |
Message-ID: | 6459.1381848987@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
David Johnston <polobo(at)yahoo(dot)com> writes:
> chris smith-9 wrote
>> Using postgres 8.4.13 (latest that redhat provides in rhel6) the query
>> below returns an extra row compared to running the same thing in later
>> versions (tried 9.0, 9.1, 9.2 - they don't return the extra row).
> Likely this is a bug that was fixed in one of the five newer 8.4 point
> releases. You can use "SELECT DISTINCT *" to get rid of the extra data if
> you choose not to upgrade.
In particular I think this matches the first item in the 8.4.14 release
notes:
* Fix planner's assignment of executor parameters, and fix executor's
rescan logic for CTE plan nodes (Tom Lane)
These errors could result in wrong answers from queries that scan the
same WITH subquery multiple times.
When I worked for Red Hat, it was hard to get permission to push PG update
releases unless a nontrivial security fix was involved. That's probably
why they're still on 8.4.13. You could file a bug asking for an update
because of this issue, but I can't say how quickly anything would happen.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | ginkgo36 | 2013-10-15 15:52:26 | Help function to sort string |
Previous Message | Laurentius Purba | 2013-10-15 13:36:57 | Re: Postgresql 9.0.13 core dump |