e10c5597b7
Display -? as -\? under unix for psql.
2000-05-11 03:14:19 +00:00
0fbde5d928
Add options and cleanup psql \? and -? help displays
2000-05-11 01:37:54 +00:00
5a75ad5573
Update psql \? to show file rather than "fname".
2000-05-09 19:08:36 +00:00
6706194e4e
Fix psql quotes in docs.
2000-05-09 18:55:56 +00:00
3b5338da25
More single-quote fixes.
2000-05-09 18:30:43 +00:00
4108ee962a
Add single quote.
2000-05-09 18:27:25 +00:00
f44328b2b8
Change HISTORY to show outer joins in 7.1 or 7.2.
2000-05-08 23:56:50 +00:00
11a93191dc
Minor fixups for markup and wording.
2000-05-08 16:19:56 +00:00
b5c430467f
Update TODO list.
2000-05-06 20:21:08 +00:00
91885836f7
Update TODO list.
2000-05-06 16:05:17 +00:00
50432d9d09
Update TODO list.
2000-05-06 01:05:10 +00:00
55778b36f4
Update TODO list.
2000-05-05 22:25:20 +00:00
b45f3a6e5b
Forgot that dumpall's output script should 'delete from pg_group' before
...
loading new data, for consistency with its handling of pg_shadow.
2000-05-05 17:50:38 +00:00
5e4d8be18b
psql: suppress warnings about too many arguments if the command is not valid in the first place
2000-05-05 09:38:40 +00:00
8322072188
Spello SERIALIZED -> SERIALIZABLE in psql tab completion
2000-05-05 08:44:27 +00:00
02faee5eaa
ImageViewer transaction fixes
2000-05-05 07:35:29 +00:00
2937bf0adf
Update TODO list.
2000-05-05 04:06:18 +00:00
ad1c88104b
Please apply the following patch to the FAQ_AIX
...
Thanks
Andreas
2000-05-05 03:40:20 +00:00
0471eb1681
Because we ended up forcing an initdb for 7.0 final, we aren't going
...
to need this updatepgproc.sql script after all...
2000-05-05 03:11:24 +00:00
c0337ec2a9
Force initdb because of pg_group index fix.
2000-05-05 03:10:24 +00:00
3bd03b3803
Make the indexes on pg_group be shared system relations.
2000-05-05 03:09:43 +00:00
3a69c316cc
Accept pg_group as well as pg_shadow data from dumpall script.
...
Rearrange handling of VACUUMs so that they are certain to be executed
as superuser not some random user; also, do not forget to vacuum
template1 itself.
2000-05-05 03:08:20 +00:00
3d1461802e
Dump contents of pg_group along with pg_shadow.
2000-05-05 03:04:00 +00:00
570a58f427
Don't leak a file descriptor when updating pg_pwd file. Also, check for
...
failure of rename() call.
2000-05-04 20:06:07 +00:00
8bd6c1f8e9
Polishing for 7.0 release. Fix up inconsistant spacing in release notes.
2000-05-04 16:15:08 +00:00
7db607f354
Installation guide for 7.0 release. From SGML sources.
2000-05-04 16:12:05 +00:00
de13d88146
Do not try to build libpq++ if class 'string' is not defined in the
...
available C++ header files.
2000-05-03 18:30:17 +00:00
86b8bd0748
Minor fixes ready for 7.0
2000-05-03 15:58:09 +00:00
c804a48ec6
Oops,I've forgotten to add an documentation about -P option of
...
postgres.
2000-05-03 07:33:44 +00:00
f25d8b47fc
Update sco faq.
2000-05-03 03:45:55 +00:00
5c6e5c887a
Update FAQ.
2000-05-02 21:57:59 +00:00
832df546f5
Remove derived files from CVS. Now kept in
...
hub.org:/home/projects/pgsql/ftp/www/html/users-lounge/7.0/docs/
2000-05-02 21:08:36 +00:00
b738d5948a
Improve section heading for date/time history.
2000-05-02 20:36:21 +00:00
45f79cae14
Fixups in content and markup for 7.0 release.
2000-05-02 20:02:03 +00:00
a6894eb81a
Update HISTORY/sgml for new pgaccess version.
2000-05-02 17:06:10 +00:00
7ef29a26cb
Update SCO FAQ. Billy G. Allie
2000-05-02 10:57:11 +00:00
832877e95a
Modify getdatabaseencoding(), pg_encoding_to_char()
...
pg_char_to_encoding() in multibyte disbaled case so that it does not
throw an error, rather return HARD CODED default value (currently SQL_ASCII).
This would solve the "non-mb backend vs. mb-enabled frontend" problem.
2000-05-02 08:13:08 +00:00
f6a3b87c7b
Reset CurrentMemoryContext to TopMemoryContext at the beginning of error
...
cleanup, ie, as soon as we have caught the longjmp. This ensures that
current context will be a valid context throughout error cleanup. Before
it was possible that current context was pointing at a context that would
get deleted during cleanup, leaving any subsequent pallocs in deep
trouble. I was able to provoke an Assert failure when compiled with
asserts + -DCLOBBER_FREED_MEMORY, if I did something that would cause
an error to be reported by the backend large-object code, because indeed
that code operates in a context that gets deleted partway through xact
abort --- and CurrentMemoryContext was still pointing at it! Boo hiss.
2000-04-30 21:29:23 +00:00
e0095c6c42
Remove bogus 'xid loop detected' check, which actually wasn't detecting
...
loops, but just arbitrarily failing at 1000 locks.
2000-04-30 21:23:31 +00:00
2f19d11fc8
Clean up ecpg test files.
2000-04-29 03:25:24 +00:00
3e24112b71
Update TODO list.
2000-04-29 02:27:21 +00:00
0ccf3c8877
Update pgeasy examples
2000-04-28 22:49:25 +00:00
9bd604f3be
Update TODO list.
2000-04-28 19:40:00 +00:00
7bd35f0f77
Update TODO list.
2000-04-28 19:15:49 +00:00
0e69b81d25
Update libpgeasy define.
2000-04-28 17:19:42 +00:00
96d643e5d5
More libpgeasy update of connectdb() parameter ordering
2000-04-28 15:03:39 +00:00
7aa443d01e
Change libpgeasy to take dbname at end like all other interfaces.
2000-04-28 14:58:51 +00:00
796695c9d1
Update TODO list.
2000-04-28 14:44:47 +00:00
a90dc572ed
Setting statistic options from SET PG_OPTIONS caused a backend crash
...
because StatFp never got set in that case. Set it immediately before
use to eliminate such problems.
2000-04-28 05:07:34 +00:00
45cc0e9b27
plpgsql RAISE statement was careless about the possibility of a NULL
...
field value being displayed; produced coredump instead of the expected
<NULL> display.
2000-04-28 00:12:44 +00:00
Bruce Momjian
Thomas G. Lockhart
Tom Lane
Peter Eisentraut
Peter Mount
Hiroshi Inoue
Tatsuo Ishii