f6689a328f
Fixed a few "fixes" and bugs. Adjusted messages and options to GNU suggestions.
2000-01-12 19:36:36 +00:00
267c6c7f06
Multi-byte case fix by Oliver Elphick (olly@lfix.co.uk)
2000-01-12 13:08:55 +00:00
0b14b0c87e
Use fmgr_array_args() to avoid dependency on FUNC_MAX_ARGS.
2000-01-12 05:28:47 +00:00
72ed6ff5ad
In PQfn(), defend against too many args, and avoid dependency
...
on FUNC_MAX_ARGS by using an appropriate fmgr() call.
2000-01-12 05:27:20 +00:00
ef899c7f62
RemoveFunction didn't defend against too many args.
2000-01-12 05:25:09 +00:00
488f315913
Defend against > INDEX_MAX_KEYS keys in an index.
2000-01-12 05:04:42 +00:00
8acc568a6b
CommentProc was careless about too many arguments.
2000-01-12 04:59:41 +00:00
421d4f9bd7
Put back erroneously removed zeroing of sentinel elements
...
in indexkeys, classlist arrays.
2000-01-12 00:53:21 +00:00
b9d832f6ef
Make FUNC_MAX_ARGS equal INDEX_MAX_KEYS, as it should.
...
Set default INDEX_MAX_KEYS to 16. Document minimum safe value is 9.
2000-01-11 05:58:55 +00:00
f1e1634e72
oid8 => oidvector in alter_table regress test
2000-01-11 05:56:33 +00:00
41f17e676f
Another FUNC_MAX_ARGS tweak.
2000-01-11 05:41:49 +00:00
fa3aa5e1bb
Wrong boundary condition on number-of-args check.
2000-01-11 05:22:25 +00:00
cc2e19ef9a
Ah-hah, there are attribute size constants lurking here too.
2000-01-11 05:18:42 +00:00
5c2fb2a1e2
Use symbolic INDEX_MAX_KEYS in pg_type entries for oidvector
...
and int2vector.
2000-01-11 04:02:28 +00:00
c2fa275d20
Correct hardwired type information in bootstrap.
2000-01-11 04:00:30 +00:00
7bc1fbe100
Remove no-longer-used symbols.
2000-01-11 03:59:31 +00:00
bd52f4bffd
More cleanups. Still doesn't work.
2000-01-11 03:33:14 +00:00
aadd14b8f2
More cleanups.
2000-01-11 02:46:48 +00:00
401e6de7ee
More fixes, but still need +1 for FUNC_MAX_ARGS
2000-01-11 02:30:06 +00:00
bf49f0849d
Remove outdated comment about 8 arguments.
2000-01-11 01:42:08 +00:00
a97caacb5e
Fix initdb so it works, but still only for 8.
2000-01-10 23:03:41 +00:00
182162a388
Update type stuff.
2000-01-10 20:46:23 +00:00
dd8b0e67ec
Cleanup for func args > 8.
2000-01-10 20:23:31 +00:00
2d920dc717
More updates for function call interface > 8.
2000-01-10 18:27:41 +00:00
0bdd0cdd98
Update fmgr to allow 32 arguments.
2000-01-10 18:18:30 +00:00
8a093d0ae3
Make number of args to a function configurable.
2000-01-10 17:14:46 +00:00
6456b17bc1
Rename oid8 -> oidvector and int28 -> int2vector. Cleanup of *out functions.
2000-01-10 16:13:23 +00:00
3f03f74f36
Update int28out and out8out and _in_ functions to handle trailing zeros
...
properly.
2000-01-10 15:41:34 +00:00
0f2e7948e2
Improve cache invalidation handling. Eespecially
...
this would fix TODO
* elog() flushes cache, try invalidating just entries from
current xact, perhaps using invalidation cache
2000-01-10 06:30:56 +00:00
5770935965
Fix oid8in and int28in for spaces
2000-01-10 05:23:47 +00:00
a040281787
Move fixes for >8 indexed fields.
2000-01-10 05:20:26 +00:00
b99f300675
Move INDEX_MAX_KEYS to postgres.h, and make it configurable for users.
2000-01-10 04:36:37 +00:00
fcb7c14d02
Repair subtle VACUUM bug that led to 'HEAP_MOVED_IN was not expected'
...
errors. VACUUM normally compacts the table back-to-front, and stops
as soon as it gets to a page that it has moved some tuples onto.
(This logic doesn't make for a complete packing of the table, but it
should be pretty close.) But the way it was checking whether it had
got to a page with some moved-in tuples was to look at whether the
current page was the same as the last page of the list of pages that
have enough free space to be move-in targets. And there was other
code that would remove pages from that list once they got full.
There was a kluge that prevented the last list entry from being
removed, but it didn't get the job done. Fixed by keeping a separate
variable that contains the largest block number into which a tuple
has been moved. There's no longer any need to protect the last element
of the fraged_pages list.
Also, fix NOTICE messages to describe elapsed user/system CPU time
correctly.
2000-01-10 04:09:50 +00:00
b86ca72f39
Update platform-specific-expected-file support so that platforms can be
...
specified by regular-expression patterns. Add some more files.
2000-01-09 20:54:36 +00:00
4f9d74f98b
install_plpgsql is no longer a regress test (it's done via createlang);
...
remove the no-longer-used files.
2000-01-09 19:34:43 +00:00
85b309ee8f
Add SetPidFile() and friends.
2000-01-09 12:19:27 +00:00
ac0d141ead
Do not start if postmaster is running.
2000-01-09 12:17:33 +00:00
10283ee6a4
Move SetPidFile() and firends to utils/init/miscinit.c from
...
postmaster/postmaster.c so that
tcop/postgres.c can use them. Now we have an interlock between
postmaster and postgres.
2000-01-09 12:15:57 +00:00
3f3421f905
Move SetPidFile() and firends to utils/init/miscinit.c so that
...
tcop/postgres.c can use them. Now we have an interlock between
postmaster and postgres.
2000-01-09 12:13:24 +00:00
359652898b
Add more portability to echo -n (code stolen from createlang)
...
Do not start postmaster if postgres is running
2000-01-09 12:06:52 +00:00
bd62e062aa
New scheme for managing platform-specific regress test result files.
...
Instead of hard-wiring one result file per platform, there is a map file
'resultmap' that says which one to use --- a lot like template/.similar.
I have only created entries in resultmap for my own platform (HPUX) so
far; feel free to add lines for other platforms.
2000-01-09 07:54:00 +00:00
2a19ac97a7
Remove obsolete platform-specific comparison files.
2000-01-09 06:34:46 +00:00
8ba050698b
First examples of multiplatform result comparison files.
2000-01-09 06:32:33 +00:00
62cbd53bcd
Remove obsolete platform-specific regress test comparison files.
...
Note: don't put any of these back till you've grokked the new code for
platform-specific comparisons that I'm about to commit...
2000-01-09 06:30:55 +00:00
fc0a46dc16
Remove CVS $Header lines from a couple of regress test files that had
...
them --- it is just *way* too painful to keep expected results in sync
when these are present.
2000-01-09 04:01:49 +00:00
f5b754a492
Update remaining tests for new psql, with the exception of 'arrays'.
2000-01-09 03:50:27 +00:00
260b6afc79
Update remaining tests for new psql, with the exception of 'arrays',
...
which is broken in some weird way that I don't understand. I think it
may be exposing a bug in the new psql --- for one thing, I get different
results when I run psql by hand than the regress script gets. What
the heck???
2000-01-09 03:48:39 +00:00
0e821fb771
Fix some missing substitutions of _OBJWD_ and _DLSUFFIX_.
2000-01-09 02:48:01 +00:00
166b5c1def
Another round of planner/optimizer work. This is just restructuring and
...
code cleanup; no major improvements yet. However, EXPLAIN does produce
more intuitive outputs for nested loops with indexscans now...
2000-01-09 00:26:47 +00:00
69d4299e3e
This patch removes the initialization of ri in loop in
...
quote_postgres(...) in ecpglib.c.
The code in CVS reads:
quote_postgres(char *arg, int lineno)
{
char *res = (char *) ecpg_alloc(2 * strlen(arg) + 3, lineno);
int i,
ri = 0;
if (!res)
return (res);
res[ri++] = '\'';
for (i = 0, ri=0; arg[i]; i++, ri++)
{
switch (arg[i])
{
case '\'':
res[ri++] = '\'';
break;
case '\\':
res[ri++] = '\\';
break;
default:
;
}
The problem here is that ri is reset to 0, thus overwriting the initial
quote.
Stephen Birch
2000-01-08 22:58:03 +00:00
