|
1 | 1 |
|
2 | 2 | Developer's Frequently Asked Questions (FAQ) for PostgreSQL |
3 | 3 |
|
4 | | - Last updated: FriDec 24 11:43:42 EST 1999 |
| 4 | + Last updated: FriJun 9 21:54:54 EDT 2000 |
5 | 5 |
|
6 | 6 | Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) |
7 | 7 |
|
|
91 | 91 | or |
92 | 92 | ; Cmd to set tab stops &etc for working with PostgreSQL code |
93 | 93 | (c-add-style "pgsql" |
94 | | - '("bsd" |
| 94 | + '("bsd" |
95 | 95 | (indent-tabs-mode . t) |
96 | 96 | (c-basic-offset . 4) |
97 | 97 | (tab-width . 4) |
98 | | - (c-offsets-alist . |
| 98 | + (c-offsets-alist . |
99 | 99 | ((case-label . +)))) |
100 | 100 | t) ; t = set this mode on |
101 | 101 |
|
@@ -309,8 +309,8 @@ c-mode) |
309 | 309 | you to query the system catalogs. This is the preferred way to access |
310 | 310 | system tables, because the first call to the cache loads the needed |
311 | 311 | rows, and future requests can return the results without accessing the |
312 | | - base table.Some of thecaches use system table indexes to look up |
313 | | -tuples. Alist of available caches is located in |
| 312 | + base table.Thecaches use system table indexes to look up tuples. A |
| 313 | + list of available caches is located in |
314 | 314 | src/backend/utils/cache/syscache.c. |
315 | 315 | src/backend/utils/cache/lsyscache.c contains many column-specific |
316 | 316 | cache lookup functions. |
@@ -353,11 +353,12 @@ c-mode) |
353 | 353 | is to use heap_tuplemodify() and pass it your palloc'ed tuple, and the |
354 | 354 | values you want changed. It returns another palloc'ed tuple, which you |
355 | 355 | pass to heap_replace(). You can delete tuples by passing the tuple's |
356 | | - t_self to heap_destroy(). Remember, tuples can be either system cache |
357 | | - versions, which may go away soon after you get them, buffer cache |
358 | | - version, which will go away when you heap_getnext(), heap_endscan, or |
359 | | - ReleaseBuffer(), in the heap_fetch() case. Or it may be a palloc'ed |
360 | | - tuple, that you must pfree() when finished. |
| 356 | + t_self to heap_destroy(). You can use it for heap_update() too. |
| 357 | + Remember, tuples can be either system cache versions, which may go |
| 358 | + away soon after you get them, buffer cache versions, which go away |
| 359 | + when you heap_getnext(), heap_endscan, or ReleaseBuffer(), in the |
| 360 | + heap_fetch() case. Or it may be a palloc'ed tuple, that you must |
| 361 | + pfree() when finished. |
361 | 362 |
|
362 | 363 | 10) What is elog()? |
363 | 364 |
|
|