| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Christopher Browne" <cbbrowne(at)gmail(dot)com> |
| Cc: | "Ravindran G - TLS, Chennai(dot)" <ravindran_g(at)hcl(dot)in>, pgsql-performance(at)postgresql(dot)org, "Isac Newton A - TLS, Chennai(dot)" <isacnewtona(at)hcl(dot)in> |
| Subject: | Re: Postgre SQL 7.1 cygwin performance issue. |
| Date: | 2006-08-28 15:13:55 |
| Message-ID: | 28299.1156778035@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"Christopher Browne" <cbbrowne(at)gmail(dot)com> writes:
> On 8/28/06, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>> There's no solution short of upgrading.
> That's a little too negative. There is at least one alternative,
> possibly two...
But both of those would probably involve work comparable to an upgrade.
There is another reason for not encouraging these folk to stay on 7.1
indefinitely, which is that 7.1 still has the transaction ID wraparound
problem. It *will* --- not might, WILL --- eat their data someday.
Without knowing anything about their transaction rate, I can't say
whether that will happen tomorrow or not for many years, but insisting
on staying on 7.1 is a dangerous game.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michal Taborsky - Internet Mall | 2006-08-28 15:27:54 | Re: Identifying bloated tables |
| Previous Message | Joshua D. Drake | 2006-08-28 15:09:19 | Re: Postgre SQL 7.1 cygwin performance issue. |