Re: Reducing size of WAL record headers

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reducing size of WAL record headers
Date: 2013-01-11 00:14:53
Message-ID: CA+U5nMK4ofQ7F1tcg1jtZvvxFvpnh3xjiuRO8vqprFU=sU8pBA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10 January 2013 20:13, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> On Wed, Jan 9, 2013 at 05:06:49PM -0500, Tom Lane wrote:
>>> Let's wait till we see where the logical rep stuff ends up before we
>>> worry about saving 4 bytes per WAL record.
>
>> Well, we have wal_level to control the amount of WAL traffic.
>
> That's entirely irrelevant. The point here is that we'll need more bits
> to identify what any particular record is, unless we make a decision
> that we'll have physically separate streams for logical replication
> info, which doesn't sound terribly attractive; and in any case no such
> decision has been made yet, AFAIK.

You were right to say that this is less important than logical
replication. I don't need any more reason than that to stop talking
about it.

I have a patch for this, but as yet no way to submit it while at the
same time saying "put this at the back of the queue".

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2013-01-11 00:53:20 Re: PL/perl should fail on configure, not make
Previous Message Andrew Dunstan 2013-01-10 23:42:09 Re: json api WIP patch