| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Rajeev rastogi <rajeev(dot)rastogi(at)huawei(dot)com>, Ants Aasma <ants(at)cybertec(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Markus Wanner <markus(at)bluegap(dot)ch> |
| Subject: | Re: Proposal for CSN based snapshots |
| Date: | 2014-06-03 13:55:48 |
| Message-ID: | CA+TgmoZ4cP_1Pavwn+VX74_ksDhHf-whO5FFR1j+NdZqONu8MA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 30, 2014 at 2:38 PM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> (forgot to answer this question)
>
> On 05/30/2014 06:27 PM, Andres Freund wrote:
>>
>> On 2014-05-30 17:59:23 +0300, Heikki Linnakangas wrote:
>>>
>>> * I expanded pg_clog to 64-bits per XID, but people suggested keeping
>>> pg_clog as is, with two bits per commit, and adding a new SLRU for the
>>> commit LSNs beside it. Probably will need to do something like that to
>>> avoid
>>> bloating the clog.
>>
>>
>> It also influences how on-disk compatibility is dealt with. So: How are
>> you planning to deal with on-disk compatibility?
>
>
> Have pg_upgrade read the old clog and write it out in the new format.
That doesn't address Bruce's concern about CLOG disk consumption.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G Johnston | 2014-06-03 14:02:08 | Re: Re-create dependent views on ALTER TABLE ALTER COLUMN ... TYPE? |
| Previous Message | Abhijit Menon-Sen | 2014-06-03 13:30:42 | Re: idle_in_transaction_timeout |