| From: | Jeff Amiel <becauseimjeff(at)yahoo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Corrupt database? 8.1/FreeBSD6.0 |
| Date: | 2007-01-13 17:40:41 |
| Message-ID: | 758295.45906.qm@web60818.mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
Really? Wow, *that's* an interesting thought. Is it likely that that
temp table could contain many-hour-old data?
Certainly...our connection pool used by jboss can have connections to postgres persisting for multiple days. (We're still looking for a way to tell it to recycle these occasionally). As each 'user' of our web based app performs some action, they acquire one of the connection pool connections and set their user_id in the temporary table used by that connection (we use that for our audit triggers) Once they are 'done' with the connection, the connection is just released back to the pool but not actually closed...so the temp table still contains the data from a previous iteration.
---------------------------------
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | elein | 2007-01-14 00:05:43 | Re: [HACKERS] Autovacuum Improvements |
| Previous Message | Richard Troy | 2007-01-13 17:09:54 | Re: index type for indexing long texts |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-01-13 22:18:59 | Memory context in exception handler |
| Previous Message | Tom Lane | 2007-01-13 16:54:29 | Re: Corrupt database? 8.1/FreeBSD6.0 |