| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot Standby and 64+ subxids (was COPY enhancements) |
| Date: | 2009-11-10 03:03:22 |
| Message-ID: | 16276.1257822202@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Simon Riggs wrote:
>> HS writes a WAL record for subtransactions at the point that the subxid
>> cache overflows for any single transaction. Current cache size = 64.
>> Top-level transaction then writes one additional WAL record every
>> additional 64 subxids after that. These are known as xid assignment
>> records.
> I don't recall seeing an answer to this, and I can't find one on the
> list archives either. Is it no longer an issue?
I'm still concerned about it, but realistically the subxids would be
writing other WAL records too, so it's probably not as bad as I thought
at first.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-11-10 03:37:02 | Re: drop tablespace error: invalid argument |
| Previous Message | Bruce Momjian | 2009-11-10 02:01:14 | Re: plpgsql EXECUTE will not set FOUND |