Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
bb35e499
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
bb35e499
编写于
9月 10, 2001
作者:
B
Bruce Momjian
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Remove mention of INV_ARCHIVE.
上级
ea41e77c
变更
3
显示空白变更内容
内联
并排
Showing
3 changed file
with
6 addition
and
11 deletion
+6
-11
doc/src/sgml/libpgtcl.sgml
doc/src/sgml/libpgtcl.sgml
+1
-1
doc/src/sgml/lobj.sgml
doc/src/sgml/lobj.sgml
+3
-7
doc/src/sgml/pygresql.sgml
doc/src/sgml/pygresql.sgml
+2
-3
未找到文件。
doc/src/sgml/libpgtcl.sgml
浏览文件 @
bb35e499
...
...
@@ -1134,7 +1134,7 @@ The oid of the large object created.
<TITLE>Usage
</TITLE>
<PARA>
mode can be any OR'ing together of INV_READ
, INV_WRITE, and INV_ARCHIV
E.
mode can be any OR'ing together of INV_READ
and INV_WRIT
E.
The OR delimiter character is "|".
<ProgramListing>
[pg_lo_creat $conn "INV_READ|INV_WRITE"]
...
...
doc/src/sgml/lobj.sgml
浏览文件 @
bb35e499
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v 1.1
7 2001/09/10 03:02:06 ishii
Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v 1.1
8 2001/09/10 04:15:41 momjian
Exp $
-->
<chapter id="largeObjects">
...
...
@@ -117,17 +117,13 @@ Oid lo_creat(PGconn *<replaceable class="parameter">conn</replaceable>, int <rep
<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
<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
|INV_ARCHIVE
);
inv_oid = lo_creat(INV_READ|INV_WRITE);
</programlisting>
</para>
</sect2>
...
...
doc/src/sgml/pygresql.sgml
浏览文件 @
bb35e499
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/Attic/pygresql.sgml,v 1.
1 2001/03/04 18:54:07 petere
Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/Attic/pygresql.sgml,v 1.
2 2001/09/10 04:15:41 momjian
Exp $ -->
<chapter id="pygresql">
<title><application>PyGreSQL</application> - <application>Python</application> Interface</title>
...
...
@@ -418,7 +418,6 @@ make && make install
<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
...
...
@@ -2253,7 +2252,7 @@ locreate(<replaceable>mode</replaceable>)
<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_ARCHIV
E</literal>).
(<literal>INV_READ
and INV_WRIT
E</literal>).
</para>
</refsect1>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录