| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] temp table oddness? |
| Date: | 1999-09-04 16:22:20 |
| Message-ID: | 24436.936462140@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
> Yep. Wouldn't the best way be to have the temp system record the
> transaction id used, and to invalidate all temp entries associated with
> an aborted transaction. That is how the cache code works, so it seems
> it should be extended to the temp code.
Yeah, that would work -- add an xact abort cleanup routine that goes
through the temprel list and removes entries added during the current
transaction.
AFAICS this only explains the coredump-at-exit business, though.
I'm particularly baffled by that
ERROR: cannot find attribute 1 of relation pg_temp.24335.3
in my last example --- do you understand why that's happening?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-09-04 16:26:42 | Re: [HACKERS] temp table oddness? |
| Previous Message | Bruce Momjian | 1999-09-04 16:16:47 | Re: [HACKERS] temp table oddness? |