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

Commite240187

Browse files
author
Neil Conway
committed
This patch makes some SGML markup more consistent and makes a small
improvement to the SSL auth docs.
1 parent7fb5a99 commite240187

File tree

2 files changed

+44
-29
lines changed

2 files changed

+44
-29
lines changed

‎doc/src/sgml/problems.sgml

Lines changed: 27 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.16 2003/11/29 19:51:37 pgsql Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.17 2003/12/14 00:05:29 neilc Exp $
33
-->
44

55
<sect1 id="bug-reporting">
@@ -18,7 +18,7 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.16 2003/11/29 19:51:37 pgsql E
1818
<para>
1919
The following suggestions are intended to assist you in forming bug reports
2020
that can be handled in an effective fashion. No one is required to follow
21-
them butit tends to be to everyone's advantage.
21+
them butdoing so tends to be to everyone's advantage.
2222
</para>
2323

2424
<para>
@@ -204,17 +204,19 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.16 2003/11/29 19:51:37 pgsql E
204204

205205
<listitem>
206206
<para>
207-
Any command line options and other start-up options, including concerned
208-
environment variables or configuration files that you changed from the
209-
default. Again, be exact. If you are using a prepackaged
210-
distribution that starts the database server at boot time, you should try
211-
to find out how that is done.
207+
Any command line options and other start-up options, including
208+
any relevant environment variables or configuration files that
209+
you changed from the default. Again, please provide exact
210+
information. If you are using a prepackaged distribution that
211+
starts the database server at boot time, you should try to find
212+
out how that is done.
212213
</para>
213214
</listitem>
214215

215216
<listitem>
216217
<para>
217-
Anything you did at all differently from the installation instructions.
218+
Anything you did at all differently from the installation
219+
instructions.
218220
</para>
219221
</listitem>
220222

@@ -234,22 +236,29 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.16 2003/11/29 19:51:37 pgsql E
234236
</para>
235237

236238
<para>
237-
If your version is older than &version; we will almost certainly tell
238-
you to upgrade. There are tons
239-
of bug fixes in each new release, that is why we make new releases.
239+
If your version is older than &version; we will almost certainly
240+
tell you to upgrade. There are many bug fixes and improvements
241+
in each new release, so it is quite possible that a bug you have
242+
encountered in an older release of <productname>PostgreSQL</>
243+
has already been fixed. We can only provide limited support for
244+
sites using older releases of PostgreSQL; if you require more
245+
than we can provide, consider acquiring a commercial support
246+
contract.
240247
</para>
241248
<para>
242249
</para>
243250
</listitem>
244251

245252
<listitem>
246253
<para>
247-
Platform information. This includes the kernel name and version, C library,
248-
processor, memory information. In most cases it is sufficient to report
249-
the vendor and version, but do not assume everyone knows what exactly
250-
<quote>Debian</quote> contains or that everyone runs on Pentiums. If
251-
you have installation problems then information about compilers, make,
252-
etc. is also necessary.
254+
Platform information. This includes the kernel name and version,
255+
C library, processor, memory information, and so on. In most
256+
cases it is sufficient to report the vendor and version, but do
257+
not assume everyone knows what exactly <quote>Debian</quote>
258+
contains or that everyone runs on Pentiums. If you have
259+
installation problems then information about the toolchain on
260+
your machine (compiler, <application>make</application>, and so
261+
on) is also necessary.
253262
</para>
254263
</listitem>
255264
</itemizedlist>
@@ -269,7 +278,7 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.16 2003/11/29 19:51:37 pgsql E
269278
</para>
270279

271280
<para>
272-
When writing a bug report, pleasechoose non-confusing terminology.
281+
When writing a bug report, pleaseavoidconfusing terminology.
273282
The software package in total is called <quote>PostgreSQL</quote>,
274283
sometimes <quote>Postgres</quote> for short. If you
275284
are specifically talking about the backend server, mention that, do not

‎doc/src/sgml/ref/lock.sgml

Lines changed: 17 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/lock.sgml,v 1.39 2003/11/29 19:51:39 pgsql Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/lock.sgml,v 1.40 2003/12/14 00:05:29 neilc Exp $
33
PostgreSQL documentation
44
-->
55

@@ -108,9 +108,10 @@ where <replaceable class="PARAMETER">lockmode</replaceable> is one of:
108108
</para>
109109

110110
<para>
111-
The command <literal>LOCK a, b;</> is equivalent to
112-
<literal>LOCK a; LOCK b;</>. The tables are locked one-by-one in
113-
the order specified in the <command>LOCK</command> command.
111+
The command <literal>LOCK TABLE a, b;</> is equivalent to
112+
<literal>LOCK TABLE a; LOCK TABLE b;</>. The tables are locked
113+
one-by-one in the order specified in the <command>LOCK
114+
TABLE</command> command.
114115
</para>
115116
</listitem>
116117
</varlistentry>
@@ -136,17 +137,18 @@ where <replaceable class="PARAMETER">lockmode</replaceable> is one of:
136137
<title>Notes</title>
137138

138139
<para>
139-
<literal>LOCK ... IN ACCESS SHARE MODE</> requires <literal>SELECT</>
140+
<literal>LOCKTABLE... IN ACCESS SHARE MODE</> requires <literal>SELECT</>
140141
privileges on the target table. All other forms of <command>LOCK</>
141142
require <literal>UPDATE</> and/or <literal>DELETE</> privileges.
142143
</para>
143144

144145
<para>
145-
<command>LOCK</command> is useful only inside a transaction block
146-
(<command>BEGIN</>/<command>COMMIT</> pair), since the lock is dropped
147-
as soon as the transaction ends. A <command>LOCK</> command appearing
148-
outside any transaction block forms a self-contained transaction, so the
149-
lock will be dropped as soon as it is obtained.
146+
<command>LOCK TABLE</command> is useful only inside a transaction
147+
block (<command>BEGIN</>/<command>COMMIT</> pair), since the lock
148+
is dropped as soon as the transaction ends. A <command>LOCK
149+
TABLE</> command appearing outside any transaction block forms a
150+
self-contained transaction, so the lock will be dropped as soon as
151+
it is obtained.
150152
</para>
151153

152154
<para>
@@ -157,7 +159,11 @@ where <replaceable class="PARAMETER">lockmode</replaceable> is one of:
157159
<literal>ROW EXCLUSIVE</> mode is a sharable table lock. Keep in
158160
mind that all the lock modes have identical semantics so far as
159161
<command>LOCK TABLE</> is concerned, differing only in the rules
160-
about which modes conflict with which.
162+
about which modes conflict with which. For information on how to
163+
acquire an actual row-level lock, see <xref linkend="locking-rows">
164+
and the <xref linkend="sql-for-update"
165+
endterm="sql-for-update-title"> in the <command>SELECT</command>
166+
reference documentation.
161167
</para>
162168
</refsect1>
163169

0 commit comments

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