Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit0958666

Browse files
author
Thomas G. Lockhart
committed
Minor fixes in markup.
Include cross-references in NOTIFY and UNLISTEN.
1 parent5e0ea52 commit0958666

File tree

5 files changed

+82
-42
lines changed

5 files changed

+82
-42
lines changed

‎doc/src/sgml/ref/create_sequence.sgml‎

Lines changed: 27 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -234,10 +234,16 @@ CREATE SEQUENCE <replaceable class="parameter">seqname</replaceable>
234234
to get a new number from the sequence.
235235
The function
236236
<function>currval('<replaceable class="parameter">seqname</replaceable>')</function>
237-
may be used
238-
to determine the number returned by the last call to
237+
may be used to determine the number returned by the last call to
239238
<function>nextval(<replaceable class="parameter">seqname</replaceable>)</function>
240239
for the specified sequence in the current session.
240+
The function
241+
<function>setval('<replaceable class="parameter">seqname</replaceable>',
242+
<replaceable class="parameter">newvalue</replaceable>)</function>
243+
may be used to set the current value of the specified sequence.
244+
The next call to
245+
<function>nextval(<replaceable class="parameter">seqname</replaceable>)</function>
246+
will return the given value plus the sequence increment.
241247
</para>
242248

243249
<para>
@@ -259,10 +265,8 @@ SELECT last_value FROM sequence_name;
259265
calls to a generator.
260266
</para>
261267

262-
<para>
263-
<TITLE>
264-
NOTE:
265-
</TITLE>
268+
<caution>
269+
<para>
266270
Unexpected results may be obtained if a cache setting greater than one
267271
is used for a sequence object that will be used concurrently by multiple
268272
backends. Each backend will allocate "cache" successive sequence values
@@ -273,15 +277,16 @@ SELECT last_value FROM sequence_name;
273277
will be lost. Furthermore, although multiple backends are guaranteed to
274278
allocate distinct sequence values, the values may be generated out of
275279
sequence when all the backends are considered. (For example, with a cache
276-
setting of 10, backend A might reserve values 1..10 and return nextval=1, then
280+
setting of 10, backend A might reserve values 1..10 and return nextval=1,
281+
then
277282
backend B might reserve values 11..20 and return nextval=11 before backend
278283
A has generated nextval=2.) Thus, with a cache setting of one it is safe
279284
to assume that nextval values are generated sequentially; with a cache
280285
setting greater than one you should only assume that the nextval values
281286
are all distinct, not that they are generated purely sequentially.
282287
Also, last_value will reflect the latest value reserved by any backend,
283288
whether or not it has yet been returned by nextval.
284-
</para>
289+
</caution>
285290

286291
<REFSECT2 ID="R2-SQL-CREATESEQUENCE-3">
287292
<REFSECT2INFO>
@@ -327,6 +332,20 @@ nextval
327332
INSERT INTO distributors VALUES (NEXTVAL('serial'),'nothing');
328333
</programlisting>
329334
</para>
335+
336+
<para>
337+
Set the sequence value after a COPY FROM:
338+
<programlisting>
339+
CREATE FUNCTION distributors_id_max() RETURNS INT4
340+
AS 'SELECT max(id) FROM distributors'
341+
LANGUAGE 'sql';
342+
BEGIN;
343+
COPY distributors FROM 'input_file';
344+
SELECT setval('serial', distributors_id_max());
345+
END;
346+
</programlisting>
347+
</para>
348+
330349
</REFSECT1>
331350

332351
<REFSECT1 ID="R1-SQL-CREATESEQUENCE-3">

‎doc/src/sgml/ref/create_table.sgml‎

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -117,16 +117,10 @@ requires the <REPLACEABLE CLASS="PARAMETER">column_constraint_clause</REPLACEABL
117117
an insert or update operation to succeed. Each constraint
118118
must evaluate to a boolean expression. Multiple columns
119119
may be referenced within a single constraint.
120-
The use of
121-
<TERM>
120+
Only one PRIMARY KEY clause may be specified for a table;
122121
PRIMARY KEY <REPLACEABLE>column</REPLACEABLE>
123-
</TERM>
124-
as a table constraint
125-
is mutually incompatible with
126-
<TERM>
127-
PRIMARY KEY
128-
</TERM>
129-
used as a column constraint.
122+
(a table constraint) and PRIMARY KEY (a column constraint) are
123+
mutually exclusive..
130124
See the table constraint clause for more information.
131125
</PARA>
132126
</LISTITEM>

‎doc/src/sgml/ref/notify.sgml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<REFENTRY ID="SQL-NOTIFY">
22
<REFMETA>
3-
<REFENTRYTITLE>
3+
<REFENTRYTITLE id="sql-notify-ref">
44
NOTIFY
55
</REFENTRYTITLE>
66
<REFMISCINFO>SQL - Language Statements</REFMISCINFO>

‎doc/src/sgml/ref/set.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -450,11 +450,11 @@ DEFAULT
450450
<listitem>
451451
<para>
452452
Sets the maximum number of rows returned by a query to be unlimited.
453-
</varlistentry>
454-
455453
<para>
456454
By default, there is no limit to the number of rows
457455
returned by a query.
456+
</varlistentry>
457+
458458
</variablelist>
459459

460460
</VARLISTENTRY>

‎doc/src/sgml/ref/unlisten.sgml‎

Lines changed: 49 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -10,20 +10,20 @@ UNLISTEN
1010
UNLISTEN
1111
</REFNAME>
1212
<REFPURPOSE>
13-
Stop listening for notification on a notify condition
13+
Stop listening for notification
1414
</REFPURPOSE>
1515

1616
<REFSYNOPSISDIV>
1717
<REFSYNOPSISDIVINFO>
18-
<DATE>1998-10-07</DATE>
18+
<DATE>1998-10-19</DATE>
1919
</REFSYNOPSISDIVINFO>
2020
<SYNOPSIS>
2121
UNLISTEN { <REPLACEABLE CLASS="PARAMETER">notifyname</REPLACEABLE> | * }
2222
</SYNOPSIS>
2323

2424
<REFSECT2 ID="R2-SQL-UNLISTEN-1">
2525
<REFSECT2INFO>
26-
<DATE>1998-10-07</DATE>
26+
<DATE>1998-10-19</DATE>
2727
</REFSECT2INFO>
2828
<TITLE>
2929
Inputs
@@ -37,7 +37,7 @@ Inputs
3737
</TERM>
3838
<LISTITEM>
3939
<PARA>
40-
Name ofnotify condition to stop listening to.
40+
Name ofpreviously registered notify condition.
4141

4242
<VARLISTENTRY>
4343
<TERM>
@@ -53,7 +53,7 @@ All current listen registrations for this backend are cleared.
5353

5454
<REFSECT2 ID="R2-SQL-UNLISTEN-2">
5555
<REFSECT2INFO>
56-
<DATE>1998-10-07</DATE>
56+
<DATE>1998-10-19</DATE>
5757
</REFSECT2INFO>
5858
<TITLE>
5959
Outputs
@@ -87,49 +87,75 @@ Acknowledgement that statement has executed.
8787

8888
<REFSECT1 ID="R1-SQL-UNLISTEN-1">
8989
<REFSECT1INFO>
90-
<DATE>1998-10-07</DATE>
90+
<DATE>1998-10-19</DATE>
9191
</REFSECT1INFO>
9292
<TITLE>
9393
Description
9494
</TITLE>
9595
<PARA>
96+
<command>UNLISTEN</command>
97+
is used to remove an existing <command>NOTIFY</command> registration.
9698
UNLISTEN cancels any existing registration of the current
97-
<productname>Postgres</productname>backend as a listener on the notify
99+
<productname>Postgres</productname>session as a listener on the notify
98100
condition <REPLACEABLE CLASS="PARAMETER">notifyname</REPLACEABLE>.
99-
The special conditionname "*"means to cancel all listener registrations
100-
for the currentbackend.
101+
The special conditionwildcard "*"cancels all listener registrations
102+
for the currentsession.
101103

102104
<para>
103-
The backend does not complain if you UNLISTEN something you were not
104-
listening for.
105+
<xref linkend="sql-notify-ref" endterm="sql-notify-ref">
106+
contains a more extensive
107+
discussion of the use of <command>LISTEN</command> and
108+
<command>NOTIFY</command>.
105109

110+
<REFSECT2 ID="R2-SQL-UNLISTEN-3">
111+
<REFSECT2INFO>
112+
<DATE>1998-10-19</DATE>
113+
</REFSECT2INFO>
114+
<TITLE>
115+
Notes
116+
</TITLE>
106117
<para>
118+
<REPLACEABLE CLASS="PARAMETER">classname</REPLACEABLE>
119+
needs not to be a valid class name but can be any string valid
120+
as a name up to 32 characters long.
121+
122+
<para>
123+
The backend does not complain if you UNLISTEN something you were not
124+
listening for.
107125
Each backend will automatically execute <command>UNLISTEN *</command> when
108126
exiting.
109127

110128
<para>
111-
The reference page for <command>NOTIFY</command> contains a more extensive
112-
discussion of the use of <command>LISTEN</command> and
113-
<command>NOTIFY</command>.
129+
A restriction in some previous releases of
130+
<productname>Postgres</productname> that a
131+
<REPLACEABLE CLASS="PARAMETER">classname</REPLACEABLE>
132+
which does not correspond to an actual table must be enclosed in double-quotes
133+
is no longer present.
134+
135+
</REFSECT2>
114136

115137
<REFSECT1 ID="R1-SQL-UNLISTEN-2">
116138
<TITLE>
117139
Usage
118140
</TITLE>
119-
<PARA>
120-
<ProgramListing>
121-
postgres=> listen virtual;
141+
142+
<para>
143+
<programlisting>
144+
postgres=> LISTEN virtual;
122145
LISTEN
123-
postgres=>notify virtual;
146+
postgres=>NOTIFY virtual;
124147
NOTIFY
125148
ASYNC NOTIFY of 'virtual' from backend pid '12317' received
126-
postgres=> unlisten virtual;
149+
</programlisting>
150+
151+
<programlisting>
152+
postgres=> UNLISTEN virtual;
127153
UNLISTEN
128-
postgres=>notify virtual;
154+
postgres=>NOTIFY virtual;
129155
NOTIFY
130156
-- notice no NOTIFY event is received
131157
postgres=>
132-
</ProgramListing>
158+
</programlisting>
133159

134160
</REFSECT1>
135161

@@ -141,11 +167,12 @@ Compatibility
141167

142168
<REFSECT2 ID="R2-SQL-UNLISTEN-4">
143169
<REFSECT2INFO>
144-
<DATE>1998-10-07</DATE>
170+
<DATE>1998-10-19</DATE>
145171
</REFSECT2INFO>
146172
<TITLE>
147173
SQL92
148174
</TITLE>
149175
<PARA>
150176
There is no <command>UNLISTEN</command> in <acronym>SQL92</acronym>.
177+
151178
</REFENTRY>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp