| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | Christopher Browne <cbbrowne(at)acm(dot)org>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Help with count(*) |
| Date: | 2003-11-14 18:49:59 |
| Message-ID: | 3131.1068835799@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Hannu Krosing <hannu(at)tm(dot)ee> writes:
> Christopher Browne kirjutas R, 14.11.2003 kell 16:13:
>> I have seen this happen somewhat-invisibly when a JDBC connection
>> manager opens transactions for each connection, and then no processing
>> happens to use those connections for a long time. The open
>> transactions prevent vacuums from doing any good...
> Can't the backend be made to delay the "real" start of transaction until
> the first query gets executed ?
That is on the TODO list. I looked at it briefly towards the end of the
7.4 development cycle, and decided that it was nontrivial and I didn't
have time to make it happen before beta started. I don't recall why it
didn't seem trivial.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-11-14 18:52:32 | Re: Background writer process |
| Previous Message | Tom Lane | 2003-11-14 18:47:17 | Re: Background writer process |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Browne | 2003-11-14 19:16:56 | Re: Help with count(*) |
| Previous Message | Hannu Krosing | 2003-11-14 17:43:27 | Re: Help with count(*) |