Re: catalog corruption bug
От | Jeremy Drake |
---|---|
Тема | Re: catalog corruption bug |
Дата | |
Msg-id | Pine.LNX.4.63.0601091104580.15097@garibaldi.apptechsys.com обсуждение исходный текст |
Ответ на | Re: catalog corruption bug (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | 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
В списке pgsql-hackers по дате отправления: