| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Increasing max # of backup blocks (was Re: GiST insert algorithm rewrite) |
| Date: | 2010-12-13 13:29:45 |
| Message-ID: | 4D061FC9.9010305@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 13.12.2010 15:20, Heikki Linnakangas wrote:
> On 13.12.2010 15:04, Robert Haas wrote:
>> On Mon, Dec 13, 2010 at 7:09 AM, Heikki Linnakangas
>> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>>> Attached is an updated patch, but that issue with limited number of
>>> backup
>>> blocks needs to be resolved. The straightforward way would be to
>>> change the
>>> WAL format to increase the limit.
>>
>> Eh, is that going to bloat WAL?
>
> Nah.
Or did you mean, if changing the WAL format to raise the limit would
bloat WAL? Depends on how it's done, of course. Assuming MAXALIGN=4,
there's 2 wasted bytes in XLogRecord at the moment that we could take
into use without making the header bigger.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KaiGai Kohei | 2010-12-13 13:32:54 | Re: rest of works for security providers in v9.1 |
| Previous Message | Heikki Linnakangas | 2010-12-13 13:20:22 | Re: GiST insert algorithm rewrite |