0c86f0e174
Fix markup typo.
2005-01-31 22:59:06 +00:00
1b2ebc591c
Update debeug FAQ.
2005-01-31 22:58:00 +00:00
d96398d1eb
Restructure debug FAQ entry.
2005-01-31 22:57:17 +00:00
1f7aa643b6
Reorganize FAQ entry on performance.
2005-01-31 20:40:46 +00:00
7069a885af
Update admin tools FAQ.
2005-01-31 02:45:32 +00:00
2149b54f1c
Update PHP mention.
2005-01-31 02:43:11 +00:00
cd63e08f86
Remove "Support" FAQ item. We now have a tab on our web site.
2005-01-31 02:40:00 +00:00
18013e25c6
Wording improvement.
2005-01-31 02:19:23 +00:00
131ff4e5cd
Reorder support FAQ items.
2005-01-31 02:17:11 +00:00
14f3fb610d
Update section to mention developer's FAQ.
2005-01-31 02:09:34 +00:00
83d8591081
Mention releases are every 10-12 months now.
2005-01-31 01:59:54 +00:00
e688443cbf
Simplify FAQ item about obtaining support.
2005-01-31 01:53:49 +00:00
0a12c53385
Clarify license FAQ item.
2005-01-31 01:38:10 +00:00
810b5072dd
Modernize the FAQ item "What is PostgreSQL" to skip most historical
...
information.
2005-01-31 01:26:31 +00:00
0c109c7187
Recommend security@postgresql.org as the contact point for security-related bugs.
2005-01-30 21:31:48 +00:00
790c666931
Update FAQ text file.
2005-01-30 04:45:01 +00:00
60d6f49a47
FAQ markup fixes.
2005-01-30 04:44:11 +00:00
576853a79a
Fix ampersand in URL.
2005-01-30 04:25:26 +00:00
d79f2d4036
Remove IN/slow FAQ item because it only applies to <=7.3.X.
2005-01-30 04:20:52 +00:00
bfc536217d
Remove GEQO and Rtree FAQ items.
2005-01-30 04:16:11 +00:00
4c8a690d54
More index item rewording.kUpdate FAQ.
2005-01-30 04:06:26 +00:00
bbefccec09
Reword index/slow query item.
2005-01-30 04:05:15 +00:00
97052bc9c9
Remove FAQ item about binary cursors.
2005-01-30 04:03:02 +00:00
e136a49c5d
Remove FAQ items about IPC errors. We now report the help description
...
right in the failure. We can always re-add it if required.
2005-01-30 04:00:19 +00:00
93e1795404
Merge two Interfaces FAQ items into one.
2005-01-30 03:52:46 +00:00
a3b7d45807
Merge unix and non-unix platform faq items, and remove Y2K item.
2005-01-30 02:22:08 +00:00
811df91340
Update OID item description.
2005-01-30 02:06:33 +00:00
64428b8daf
Preliminary release notes for 8.0.1, 7.4.7, 7.3.9, 7.2.7.
2005-01-30 01:26:41 +00:00
5703a69003
We haven't had a fixed limit on rule recursion depth since 7.3 ...
...
but the documentation still said so.
2005-01-29 23:45:36 +00:00
750d9171f6
Add documentation for format_type(), which somehow escaped it before.
2005-01-28 23:12:59 +00:00
a9fec25df8
Add note cautioning that you can't use an encrypting IDENT server
...
with Postgres.
2005-01-28 22:38:37 +00:00
f07b9689c9
Generalize TRUNCATE to support truncating multiple tables in one
...
command. This is useful because we can allow truncation of tables
referenced by foreign keys, so long as the referencing table is
truncated in the same command.
Alvaro Herrera
2005-01-27 03:19:37 +00:00
aba691b728
Close all cursors created during a failed subtransaction. This is needed
...
to avoid problems when a cursor depends on objects created or changed in
the same subtransaction. We'd like to do better someday, but this seems
the only workable answer for 8.0.1.
2005-01-26 23:20:21 +00:00
4de12d4470
Add docs for a couple of formerly-undocumented geometric conversion functions.
2005-01-26 20:42:19 +00:00
d08889aa8b
Add tools/find_gt_lt to find < and > in SGML source.
...
Lowercase some uppercase tags so tools is more reliable at finding
problems.
2005-01-23 00:30:59 +00:00
754b5e1c42
More < and > changes to ampersands.
...
8.0.X and HEAD.
2005-01-22 23:22:19 +00:00
1ced129aa3
More < and > cleanups converted to ampersands.
2005-01-22 22:56:36 +00:00
9e292e3e48
More fixes for => and ->, use proper ampersand markups.
2005-01-22 22:31:52 +00:00
1e5eb160d1
Change -> and <- to use proper ampersand markups.
...
HEAD and 8.0.X.
2005-01-22 22:06:27 +00:00
b60a8512a0
Update count(*) discussion ideas:
...
< BY col {DESC} LIMIT 1. Completing this item involves making this
> BY col {DESC} LIMIT 1. Completing this item involves doing this
< invalidated if anyone modifies the table.
<
> invalidated if anyone modifies the table. Another idea is to
> get a count directly from a unique index, but for this to be
> faster than a sequential scan it must avoid access to the heap
> to obtain tuple visibility information.
>
> * Allow data to be pulled directly from indexes
>
> Currently indexes do not have enough tuple tuple visibility
> information to allow data to be pulled from the index without
> also accessing the heap. One way to allow this is to set a bit
> to index tuples to indicate if a tuple is currently visible to
> all transactions when the first valid heap lookup happens. This
> bit would have to be cleared when a heap tuple is expired.
>
2005-01-22 20:05:23 +00:00
a73198ac17
Document that Rekall is GPL now.
2005-01-19 19:45:52 +00:00
0d19d8b846
Add:
...
> * Add 'tid != tid ' operator for use in corruption recovery
2005-01-19 14:17:48 +00:00
3fc86c0f47
Fix typo.
2005-01-19 03:13:07 +00:00
31197bbdf5
Update version stamps for 8.1 as listed in RELEASE_CHANGES.
2005-01-18 05:00:35 +00:00
0f6be37fcb
Clarify that the --enable-integer-datetimes switch affects the time and
...
interval datatypes as well as timestamp.
2005-01-17 18:47:15 +00:00
be105bd789
Please find enclosed another patch that now (I hope) really is
...
correct. It's in addition to the previous patch.
David Fetter
2005-01-17 17:29:49 +00:00
8a9cc26ee1
Fix minor thinko in pg_dump documentation of "-n" option.
2005-01-17 04:30:37 +00:00
691bb1d247
Spelling fix.
2005-01-17 04:27:23 +00:00
6ea9da1ee0
Please find enclosed a patch to the pl/perl documents that correctly
...
tells what arguments go to pl/perl triggers.
David Fetter
2005-01-17 03:04:17 +00:00
56d982b7d4
Mention ALTER COLUMN TYPE in FAQ.
2005-01-17 03:02:56 +00:00
Bruce Momjian
Tom Lane
Neil Conway