On 08/11/2014 12:22 AM, MauMau wrote:
> From: "Vik Fearing" <vik.fear...@dalibo.com>
>> On 08/10/2014 03:24 PM, MauMau wrote:
>>> Could you also improve the doc by changing "table" to "relation" in the
>>> description of get_raw_page()? Having a quick look at the code, it
>>> seems that the function can also handle indexes.
>>>
>>> table and returns a copy as a <type>bytea</> value. This
>>> allows a
>>
>>
>> Good catch. I wasn't sure whether using "relation" or "table or index"
>> was better, but after a quick test it seems it works for sequences, too,
>> so I've gone with "relation".
>>
>> It doesn't work with views, of course, but it does work with
>> materialized views.
>>
>> Modified patch attached.
>
> Thanks, I marked this as ready for committer.
>
> I think I'll leave it up to you to decide whether you improve the HINT
> message Fujii-san pointed out, which is in src/backend/catalog/catalog.c.
I think you're looking at an old version of the code. My understanding
of his message was that that patch had already been applied but not
backpatched and he wants it backpatched. To wit, that hint message does
include "init" on master and it's located in src/common/relpath.c.
However, I did find another occurence in the documentation, so third
patch attached.
--
Vik
*** a/doc/src/sgml/pageinspect.sgml
--- b/doc/src/sgml/pageinspect.sgml
***************
*** 28,38 ****
<listitem>
<para>
<function>get_raw_page</function> reads the specified block of the named
! table and returns a copy as a <type>bytea</> value. This allows a
single time-consistent copy of the block to be obtained.
<replaceable>fork</replaceable> should be <literal>'main'</literal> for
! the main data fork, or <literal>'fsm'</literal> for the free space map,
! or <literal>'vm'</literal> for the visibility map.
</para>
</listitem>
</varlistentry>
--- 28,39 ----
<listitem>
<para>
<function>get_raw_page</function> reads the specified block of the named
! relation and returns a copy as a <type>bytea</> value. This allows a
single time-consistent copy of the block to be obtained.
<replaceable>fork</replaceable> should be <literal>'main'</literal> for
! the main data fork, <literal>'fsm'</literal> for the free space map,
! <literal>'vm'</literal> for the visibility map, or <literal>'init'</literal>
! for the initialization fork.
</para>
</listitem>
</varlistentry>
*** a/doc/src/sgml/storage.sgml
--- b/doc/src/sgml/storage.sgml
***************
*** 265,272 **** The <function>pg_relation_filepath()</> function shows the entire path
as a substitute for remembering many of the above rules. But keep in
mind that this function just gives the name of the first segment of the
main fork of the relation — you may need to append a segment number
! and/or <literal>_fsm</> or <literal>_vm</> to find all the files associated
! with the relation.
</para>
<para>
--- 265,272 ----
as a substitute for remembering many of the above rules. But keep in
mind that this function just gives the name of the first segment of the
main fork of the relation — you may need to append a segment number
! and/or <literal>_fsm</>, <literal>_vm</>, or <literal>_init</> to find all
! the files associated with the relation.
</para>
<para>
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
