Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
f129615f
Commit
f129615f
authored
Jun 03, 2013
by
Stephen Frost
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Additional spelling corrections
A few more minor spelling corrections, no functional changes. Thom Brown
parent
e1e2bb34
Changes
4
Show whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
5 additions
and
5 deletions
+5
-5
src/backend/access/hash/README
src/backend/access/hash/README
+2
-2
src/backend/access/nbtree/README
src/backend/access/nbtree/README
+1
-1
src/backend/utils/adt/windowfuncs.c
src/backend/utils/adt/windowfuncs.c
+1
-1
src/interfaces/libpq/fe-exec.c
src/interfaces/libpq/fe-exec.c
+1
-1
No files found.
src/backend/access/hash/README
View file @
f129615f
...
...
@@ -429,8 +429,8 @@ algorithm is:
(this requires read/update/write/release of fore and aft siblings)
pin meta page and take buffer content lock in shared mode
determine which bitmap page contains the free space bit for page
relase meta page buffer content lock
pin bitmap page and take buffer content lock in exclusie mode
rel
e
ase meta page buffer content lock
pin bitmap page and take buffer content lock in exclusi
v
e mode
update bitmap bit
mark bitmap page dirty and release buffer content lock and pin
if page number is less than what we saw as first-free-bit in meta:
...
...
src/backend/access/nbtree/README
View file @
f129615f
...
...
@@ -46,7 +46,7 @@ Lehman and Yao don't require read locks, but assume that in-memory
copies of tree pages are unshared. Postgres shares in-memory buffers
among backends. As a result, we do page-level read locking on btree
pages in order to guarantee that no record is modified while we are
examining it. This reduces concurrency but guarantee
e
s correct
examining it. This reduces concurrency but guarantees correct
behavior. An advantage is that when trading in a read lock for a
write lock, we need not re-read the page after getting the write lock.
Since we're also holding a pin on the shared buffer containing the
...
...
src/backend/utils/adt/windowfuncs.c
View file @
f129615f
...
...
@@ -161,7 +161,7 @@ window_percent_rank(PG_FUNCTION_ARGS)
/*
* cume_dist
* return fraction betwee
e
n 0 and 1 inclusive,
* return fraction between 0 and 1 inclusive,
* which is described as NP / NR, where NP is the number of rows preceding or
* peers to the current row, and NR is the total number of rows, per spec.
*/
...
...
src/interfaces/libpq/fe-exec.c
View file @
f129615f
...
...
@@ -279,7 +279,7 @@ PQsetResultAttrs(PGresult *res, int numAttributes, PGresAttDesc *attDescs)
* PG_COPYRES_ATTRS - Copy the source result's attributes
*
* PG_COPYRES_TUPLES - Copy the source result's tuples. This implies
* copying the attrs, see
e
ing how the attrs are needed by the tuples.
* copying the attrs, seeing how the attrs are needed by the tuples.
*
* PG_COPYRES_EVENTS - Copy the source result's events.
*
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment