There are many places in our docs where INV_ARCHIVE is mentioned. In
my understanding, INV_ARCHIVE has never been supported since
PostgreSQL 6.0 was born. Shall we remove it from the docs?
--
Tatsuo Ishii

Mon, 10 Sep 2001 11:57:50 +0900
Tatsuo Ishii <t-ishii@sra.co.jp>
INV_ARCHIVE?
> There are many places in our docs where INV_ARCHIVE is mentioned. In
> my understanding, INV_ARCHIVE has never been supported since
> PostgreSQL 6.0 was born. Shall we remove it from the docs?

It is for large object/inverted object archiving, which we don't have.
I have applied this patch to remove it.

Good eye.  Thanks.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Index: doc/src/sgml/libpgtcl.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/libpgtcl.sgml,v
retrieving revision 1.15
diff -c -r1.15 libpgtcl.sgml
*** doc/src/sgml/libpgtcl.sgml	2001/05/12 22:51:35	1.15
--- doc/src/sgml/libpgtcl.sgml	2001/09/10 04:12:38
***************
*** 1134,1140 ****
  <TITLE>Usage
  </TITLE>
  <PARA>
! mode can be any OR'ing together of INV_READ, INV_WRITE, and INV_ARCHIVE. 
  The OR delimiter character is "|".
  <ProgramListing>
  [pg_lo_creat $conn "INV_READ|INV_WRITE"]
--- 1134,1140 ----
  <TITLE>Usage
  </TITLE>
  <PARA>
! mode can be any OR'ing together of INV_READ and INV_WRITE. 
  The OR delimiter character is "|".
  <ProgramListing>
  [pg_lo_creat $conn "INV_READ|INV_WRITE"]
Index: doc/src/sgml/lobj.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/lobj.sgml,v
retrieving revision 1.16
diff -c -r1.16 lobj.sgml
*** doc/src/sgml/lobj.sgml	2001/02/09 19:24:09	1.16
--- doc/src/sgml/lobj.sgml	2001/09/10 04:12:39
***************
*** 117,133 ****
       <filename>$<envar>PGROOT</envar>/src/backend/libpq/libpq-fs.h</filename>
       The access type (read, write, or both) is controlled by
       OR ing together the bits <acronym>INV_READ</acronym>  and
!      <acronym>INV_WRITE</acronym>.   If
!      the large object should be archived -- that is, if 
!      historical versions of it should be moved periodically  to
!      a  special archive relation -- then the <acronym>INV_ARCHIVE</acronym> bit
!      should be set.  The low-order sixteen bits of mask  are
       the  storage  manager  number on which the large object
       should reside.  For sites other  than  Berkeley,  these
       bits should always be zero.
       The commands below create an (Inversion) large object:
       <programlisting>
! inv_oid = lo_creat(INV_READ|INV_WRITE|INV_ARCHIVE);
       </programlisting>
      </para>
     </sect2>
--- 117,129 ----
       <filename>$<envar>PGROOT</envar>/src/backend/libpq/libpq-fs.h</filename>
       The access type (read, write, or both) is controlled by
       OR ing together the bits <acronym>INV_READ</acronym>  and
!      <acronym>INV_WRITE</acronym>.  The low-order sixteen bits of mask  are
       the  storage  manager  number on which the large object
       should reside.  For sites other  than  Berkeley,  these
       bits should always be zero.
       The commands below create an (Inversion) large object:
       <programlisting>
! inv_oid = lo_creat(INV_READ|INV_WRITE);
       </programlisting>
      </para>
     </sect2>
Index: doc/src/sgml/pygresql.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/pygresql.sgml,v
retrieving revision 1.1
diff -c -r1.1 pygresql.sgml
*** doc/src/sgml/pygresql.sgml	2001/03/04 18:54:07	1.1
--- doc/src/sgml/pygresql.sgml	2001/09/10 04:12:50
***************
*** 418,424 ****
       <varlistentry>
        <term><varname>INV_READ</varname></term>
        <term><varname>INV_WRITE</varname></term>
-       <term><varname>INV_ARCHIVE</varname></term>
        <listitem>
         <para>
          large objects access modes, used by
--- 418,423 ----
***************
*** 2253,2259 ****
        <para>
          <function>locreate()</function> method creates a large object in the database.
          The mode can be defined by OR-ing the constants defined in the pg module
!         (<literal>INV_READ, INV_WRITE</literal> and <literal>INV_ARCHIVE</literal>).
        </para>
      </refsect1>
  
--- 2252,2258 ----
        <para>
          <function>locreate()</function> method creates a large object in the database.
          The mode can be defined by OR-ing the constants defined in the pg module
!         (<literal>INV_READ and INV_WRITE</literal>).
        </para>
      </refsect1>
Mon, 10 Sep 2001 00:14:44 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: INV_ARCHIVE?
On Mon, Sep 10, 2001 at 12:14:44AM -0400, Bruce Momjian wrote:
> > There are many places in our docs where INV_ARCHIVE is mentioned. In
> > my understanding, INV_ARCHIVE has never been supported since
> > PostgreSQL 6.0 was born. Shall we remove it from the docs?
> 
> It is for large object/inverted object archiving, which we don't have.
> I have applied this patch to remove it.

 I never use 6.0, but may be try dump LO by pg_dumplo (in 7.0 release)?

			Karel

-- 
 Karel Zak  <zakkr@zf.jcu.cz>
 http://home.zf.jcu.cz/~zakkr/
 
 C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz

Mon, 10 Sep 2001 09:21:05 +0200
Karel Zak <zakkr@zf.jcu.cz>
Re: INV_ARCHIVE?