| From: | Tom Lane <tgl> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql/src/backend/tcop (pquery.c) |
| Date: | 2000-08-22 04:06:20 |
| Message-ID: | 200008220406.e7M46K765171@hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Date: Tuesday, August 22, 2000 @ 00:06:20
Author: tgl
Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/tcop
from hub.org:/home/projects/pgsql/tmp/cvs-serv65122/backend/tcop
Modified Files:
pquery.c
----------------------------- Log Message -----------------------------
Fix a many-legged critter reported by chifungfan(at)yahoo(dot)com: under the
right circumstances a hash join executed as a DECLARE CURSOR/FETCH
query would crash the backend. Problem as seen in current sources was
that the hash tables were stored in a context that was a child of
TransactionCommandContext, which got zapped at completion of the FETCH
command --- but cursor cleanup executed at COMMIT expected the tables
to still be valid. I haven't chased down the details as seen in 7.0.*
but I'm sure it's the same general problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-08-22 04:06:21 | pgsql/src/backend/commands (copy.c) |
| Previous Message | Tom Lane | 2000-08-22 04:00:11 | pgsql/src/backend/utils/mmgr (mcxt.c) |