One of the design rules of PostgreSQL is extensibility. And
to follow this rule means (at least for me) that there should
not only be a builtin PL. Instead I would prefer a defined
interface for PL implemetations.
Marc G. Fournier [Tue, 13 Jan 1998 04:20:51 +0000 (04:20 +0000)]
One more src/interfaces/libpq/Makefile problem: there's an explicit
reference to the name of the shared library, instead of dereferencing
the definition from the top of the file.
Marc G. Fournier [Tue, 13 Jan 1998 04:05:12 +0000 (04:05 +0000)]
Some *very* major changes by darrenk@insightdist.com (Darren King)
==========================================
What follows is a set of diffs that cleans up the usage of BLCKSZ.
As a side effect, the person compiling the code can change the
value of BLCKSZ _at_their_own_risk_. By that, I mean that I've
tried it here at 4096 and 16384 with no ill-effects. A value
of 4096 _shouldn't_ affect much as far as the kernel/file system
goes, but making it bigger than 8192 can have severe consequences
if you don't know what you're doing. 16394 worked for me, _BUT_
when I went to 32768 and did an initdb, the SCSI driver broke and
the partition that I was running under went to hell in a hand
basket. Had to reboot and do a good bit of fsck'ing to fix things up.
The patch can be safely applied though. Just leave BLCKSZ = 8192
and everything is as before. It basically only cleans up all of the
references to BLCKSZ in the code.
If this patch is applied, a comment in the config.h file though above
the BLCKSZ define with warning about monkeying around with it would
be a good idea.
Darren darrenk@insightdist.com
(Also cleans up some of the #includes in files referencing BLCKSZ.)
==========================================
Marc G. Fournier [Tue, 13 Jan 1998 03:49:51 +0000 (03:49 +0000)]
> It seems there is a mistake in substr function:
> then you try get substr, which consists only of last char in string
> you get all string
>
> For example:
> userbase=> select substr('123456', 6,1) ;
> substr
> ------
> 123456
> (1 row)
>
Fix up for recent changes in elog error messages.
Some behavior of the triggers test cases changed for the least week or two;
now back to the usual expected behavior.
Bruce Momjian [Tue, 6 Jan 1998 18:53:02 +0000 (18:53 +0000)]
Change some labels in bootparse to make ctags happy. Clean up outfunc/readfunc code and add missing fields for Query structure and new Union fields. Fix optimizer bug shown in new \do command. Change WARN to ERROR in contrib and regression stuff.
Test for __ELF__ rather than LINUX_ELF in headers.
Comment-out dynamic link function declarations since they are all
provided by the system.
Should we bother continuing to support non-elf Linux systems??
Change precedence for boolean operators to match expected behavior.
Change NOTICE/NOTICE/NOTICE/WARN elog messages to a single message
with a few newline/tab breaks embedded in the string. Much cleaner I hope.
Add substring function for text based on oracle_compat package but
closer to standard behavior.
Substitute "text *" for "struct varlena *" in declarations.
Marc G. Fournier [Tue, 30 Dec 1997 02:26:56 +0000 (02:26 +0000)]
Slightly delayed patches from Todd...damn holidays :)
o A new patch that contains the following changes:
-- The pg_pwd file is now cached in the postmaster's memory.
-- pg_pwd is reloaded when the postmaster detects a flag file creat()'ed
by a backend.
-- qsort() is used to sort loaded password entries, and bsearch() is
is used to find entries in the pg_pwd cache.
-- backends now copy the pg_user relation to pg_pwd.pid, and then
rename the temp file to be pg_pwd.
-- The delimiter for pg_pwd has been changed to a tab character.