Skip site navigation (1) Skip section navigation (2)

Re: Refactoring log_newpage

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Jim Nasby <jim(at)nasby(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Refactoring log_newpage
Date: 2012-02-02 07:26:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 02.02.2012 08:19, Simon Riggs wrote:
> On Wed, Feb 1, 2012 at 10:42 PM, Jim Nasby<jim(at)nasby(dot)net>  wrote:
>> On Feb 1, 2012, at 4:25 AM, Simon Riggs wrote:
>>> At present log_newpage() produces log records called XLOG_HEAP_NEWPAGE.
>>> That routine is used by HEAP, BTREE, GIN, SPGIST rmgrs, as well as
>>> various forks.
>>> WAL contains no information as to which rmgr the data refers to,
>>> making debugging much harder and skewing efforts to optimise WAL
>>> traffic and is a pretty gross modularity violation of the whole rmgr
>>> concept.
>>> This refactoring adds an RmgrId field onto each new page record and
>>> makes clearer that certain "heap" routines are actually generic. The
>>> WAL records are still marked as HEAP rmgr and have XLOG_NEWPAGE record
>>> type, but at least we can tell them apart. (We already had forknum,
>>> just not rmgrid).
>> But we already had RelFileNode; wouldn't that be enough to tell what rmgr was responsible for the new page? Can 2 different rmgrs write to the same file node?
> No, but which one? No way to tell unless you have full list of
> relfilenodes and check each one.

Well, you can obviously check the catalogs for that, but you must be 
assuming that you don't have access to the catalogs or this would be a 

You can also identify the kind of page by looking at the special area of 
the stored page. See:

   Heikki Linnakangas

In response to


pgsql-hackers by date

Next:From: Jaime CasanovaDate: 2012-02-02 07:26:26
Subject: Re: pg_stats_recovery view
Previous:From: Simon RiggsDate: 2012-02-02 06:19:23
Subject: Re: Refactoring log_newpage

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group