| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
| Cc: | Decibel! <decibel(at)decibel(dot)org>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is autovacuum too noisy about orphan temp tables? |
| Date: | 2008-10-15 20:52:03 |
| Message-ID: | 27711.1224103923@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Robert Haas" <robertmhaas(at)gmail(dot)com> writes:
> A much better solution would be to not print the warning every time.
> I think the right solution is to do exactly what you rejected
> upthread, namely adding some kind of stack to track the last time this
> was printed.
I really doubt that the problem is worth so much effort. Your handwavy
solution doesn't work, I think, because you are ignoring the problem
that this code is executed in relatively short-lived processes that
aren't all examining the same database. By the time you got to a
solution that did work it'd be pretty complicated.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurent Wandrebeck | 2008-10-15 21:17:31 | Re: Column level triggers |
| Previous Message | Simon Riggs | 2008-10-15 20:51:03 | Re: Deriving Recovery Snapshots |