| From: | Gerhard Wiesinger <lists(at)wiesinger(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL 64 Bit XIDs - Transaction IDs |
| Date: | 2012-03-23 19:15:16 |
| Message-ID: | alpine.LFD.2.02.1203232012240.10155@bbs.intern |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 23 Mar 2012, Tom Lane wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
>> On Fri, Mar 23, 2012 at 11:35 AM, Gerhard Wiesinger <lists(at)wiesinger(dot)com> wrote:
>>> So I think XID overflow should be planned for one of the next PostgreSQL
>>> releases.
>
>> two mitigating factors:
>> 1. read only transactions do not increment xid counter
>
> Yes. Ask your admin what his throughput of *data modifying*
> transactions is. I'll bet that number is a few orders of magnitude
> smaller again.
That were all small writing transactions benchmarking the database (with
the corrected values discussed).
Ciao,
Gerhard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | david.sahagian | 2012-03-23 19:29:34 | Change the default [tgenabled] for new "internal" triggers ? |
| Previous Message | Gerhard Wiesinger | 2012-03-23 19:12:18 | Re: PostgreSQL 64 Bit XIDs - Transaction IDs |