From: | Jeremy Drake <pgsql(at)jdrake(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: catalog corruption bug |
Date: | 2006-01-09 19:41:36 |
Message-ID: | Pine.LNX.4.63.0601091104580.15097@garibaldi.apptechsys.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 9 Jan 2006, Tom Lane wrote:
> Does your application drop these temp tables explicitly, or leave them
> to be dropped automatically during commit? It might be interesting to
> see whether changing that makes any difference.
I drop them explicitly at the end of the function.
> I'm also curious
> whether the transaction that makes the temp table is ever rolled back
> instead of committed.
Not intentionally/explicitly. The only time it should roll back is if it
gets an error (which tends to be this error). I do sometimes hit ^C on
the perl scripts to tweak something, which would roll it back if in this
particular code, but I don't think i did that on the last run at least.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
--
Every little picofarad has a nanohenry all its own.
-- Don Vonada
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2006-01-09 19:42:00 | Re: lookup_rowtype_tupdesc considered harmful |
Previous Message | Neil Conway | 2006-01-09 19:29:48 | Re: PLs and domain constraints |