Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id C007B9FE16E for ; Thu, 14 Jun 2012 18:52:23 -0300 (ADT) Received: from moutng.kundenserver.de ([212.227.17.8]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SfHxl-0005cD-Gw for pgsql-hackers@postgresql.org; Thu, 14 Jun 2012 21:52:22 +0000 Received: from awork2.localnet (p5DDC6437.dip.t-dialin.net [93.220.100.55]) by mrelayeu.kundenserver.de (node=mreu3) with ESMTP (Nemesis) id 0MJrYu-1SgNt41lYK-0017Wf; Thu, 14 Jun 2012 23:52:06 +0200 From: Andres Freund Organization: 2ndquadrant.com To: pgsql-hackers@postgresql.org Subject: Re: WAL format changes Date: Thu, 14 Jun 2012 23:52:04 +0200 User-Agent: KMail/1.13.7 (Linux/3.4.0-andres; KDE/4.8.3; x86_64; ; ) Cc: Heikki Linnakangas References: <4FDA5136.6080206@enterprisedb.com> In-Reply-To: <4FDA5136.6080206@enterprisedb.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201206142352.04528.andres@2ndquadrant.com> X-Provags-ID: V02:K0:F7hGEThIcEutLDtwAapUcqQron+RXB38596ZU3LdQeV g0qn8NvS6DUWBRlq0r4ejEtLYUjVoV52ceDQmSdflQITdB2oeT z4+gfTykQWCb46GtSzjEeFVPtaXDu70JlzrAAT2s1rOZcx96a0 Dgf9nE/VvUyBu203/bh4DIDkQSa+6bx+zgySHPGsGUQLjETywZ Dl+WCmCfshIJsR0BivzTZySRxLsIQR4MY9/pQQwOx8omnDbaa4 WshtA79wUb7LOqEvNP8hsz3uQo95bjPFeQ1PGaZOm4xnTQkw0l 5g8sn76jrDgBwhVUENRr5iv6prekiVSiI4/wcTrZWAL0UiRVLO MfX4CIetTqheMenD/Bkrb1Sawug8OgHV/Q5nWdRJE X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201206/689 X-Sequence-Number: 209529 On Thursday, June 14, 2012 11:01:42 PM Heikki Linnakangas wrote: > As I threatened earlier > (http://archives.postgresql.org/message-id/4FD0B1AB.3090405@enterprisedb.co > m), here are three patches that change the WAL format. The goal is to > change the format so that when you're inserting a WAL record of a given > size, you know exactly how much space it requires in the WAL. I fear the patches need rebasing after the pgindent run... Even before that (60801944fa105252b48ea5688d47dfc05c695042) it only applies with offsets? Greetings, Andres -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services