On Tue, Mar 24, 2009 at 10:11 PM, Tom Lane wrote:
> Sigh ... I could've sworn I tested that code path, but evidently not,
> 'cause it's broken as can be.
If it's a code path not exercised by any regression test, is it worth
it to add one or we don't have any chance to break this code again
later?
Tom,
Thanks for the fix and the quick reply. Your patch solved my original
issue, as well as the supplied test case.
Regards,
Bruce Toll
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
"Bruce Toll" writes:
> I encountered a problem that will hopefully be
> easy for you to reproduce using psql with the
> snippet below.
Sigh ... I could've sworn I tested that code path, but evidently not,
'cause it's broken as can be.
*** src/backend/optimizer/plan/planner.c.orig Fri Jan 9 10
The following bug has been logged online:
Bug reference: 4728
Logged by: Bruce Toll
Email address: bt...@dhsus.com
PostgreSQL version: 8.4devel
Operating system: GNU/Linux (Ubuntu Hardy)
Description:segfault with window function partition involving
subquery
Details:
