pgsql-4728

Version:

8.4.0

How it is diagnosed:

Source analysis.

Links:

Bug report: http://archives.postgresql.org/pgsql-bugs/2009-03/msg00132.php

Patch: http://archives.postgresql.org/pgsql-bugs/2009-03/msg00133.php

Symptom:

Crash.

Root cause:
*** src/backend/optimizer/plan/planner.c.orig        Fri Jan  9 10:46:10 2009
--- src/backend/optimizer/plan/planner.c        Tue Mar 24 17:03:03 2009
***************
*** 2546,2553 ****
                         if (list_length(new_pathkeys) > list_length(pathkeys))
                         {
                                 /* this sort clause is actually significant */
-                                *partColIdx[*partNumCols] = sortColIdx[scidx++];

+                                (*partColIdx)[*partNumCols] = sortColIdx[scidx++];
-                                (*partOperators)[*partNumCols] = sgc->eqop;
                                 (*partNumCols)++;
                                 pathkeys = new_pathkeys;
                        }

Is there any log message?:

Yes.

Can we automatically anticipate?

Yes. Signal handler.