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

Re: Refactoring log_newpage

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(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 09:35:44
Message-ID: CA+U5nMJXw_iTubW=LQyS6roQOUmhVvv2B6zDGVWZsXDnHKNkfA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Feb 2, 2012 at 7:26 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:

> 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
> non-issue.
>
> You can also identify the kind of page by looking at the special area of the
> stored page. See:
> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00392.php

How does that work with different forks?

I think its very ugly to mark all sorts of different pages as if they
were heap pages when they clearly aren't. I don't recall anything so
ugly being allowed anywhere else in the system. Why is it *needed*
here?

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

In response to

Responses

pgsql-hackers by date

Next:From: Abhijit Menon-SenDate: 2012-02-02 09:35:55
Subject: Re: JSON output functions.
Previous:From: Marko KreenDate: 2012-02-02 09:24:55
Subject: Re: pgsql_fdw, FDW for PostgreSQL server

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