Documentation Source Text

Check-in [c1e2fd15ff]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Add poor locking to the reasons to avoid DB-over-network.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: c1e2fd15ffa6cd0fd39b7a33254165bbe4c55c97611f02a6afa6ecff008e48d2
User & Date: larrybr 2022-04-10 15:38:28.645
Context
2022-04-27
09:17
Cherry-pick minor documentation fixes from trunk. (check-in: c869cc4a55 user: drh tags: branch-3.38)
2022-04-12
00:22
In datatypes explainer, note that "Determination of Column Affinity" section does not apply to STRICT tables. (check-in: bbba322a09 user: larrybr tags: trunk)
2022-04-10
15:38
Add poor locking to the reasons to avoid DB-over-network. (check-in: c1e2fd15ff user: larrybr tags: trunk)
2022-04-07
12:29
Update the CPU cycle reduction amount after the latest optimizations. (check-in: a11c6b3eaa user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/useovernet.in.
︙︙
133
134
135
136
137
138
139







140
141
142
143
144
145
146
147
148

  and correctly implemented fsync() (or equivalent) OS functions.
  Unfortunately for some applications, network filesystem sync
  operation can be less robust than local filesystem sync.
  Attaining robust sync in the face of network packet transport errors
  is hard, and safeguards are sometimes relaxed in favor of performance.
</p>
<p>







  The bottom line is that network filesystem sync reliability
  varies among implementations and installations. The design
  assumptions upon which it relies may hold more true where
  an application is tested than where it is relied upon.
  <b>Rely upon it at your (and your customers') peril.</b>
  See [How To Corrupt Your Database Files].
</p>

<h1>Performance and Reliability Issues</h1>








>
>
>
>
>
>
>
|
|








133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155

  and correctly implemented fsync() (or equivalent) OS functions.
  Unfortunately for some applications, network filesystem sync
  operation can be less robust than local filesystem sync.
  Attaining robust sync in the face of network packet transport errors
  is hard, and safeguards are sometimes relaxed in favor of performance.
</p>
<p>
  A similar hazard arises with file locking in network filesystems.
  SQLite relies on exclusive locks for write operations, and those have
  been known to operate incorrectly for some network filesystems. This
  has led to database corruption. That may happen again as the designers
  of such change their implementataion to suit more common use cases.
</p>
<p>
  The bottom line is that network filesystem sync and locking reliability
  vary among implementations and installations. The design
  assumptions upon which it relies may hold more true where
  an application is tested than where it is relied upon.
  <b>Rely upon it at your (and your customers') peril.</b>
  See [How To Corrupt Your Database Files].
</p>

<h1>Performance and Reliability Issues</h1>
︙︙