summaryrefslogtreecommitdiff
path: root/src/backend/utils
Commit message (Collapse)AuthorAgeFilesLines
...
* Remove #include "port-protos.h", since we no longer use itMarc G. Fournier1998-02-241-6/+1
| | | | From: Frank Ridderbusch <ridderbusch.pad@sni.de>
* From: Jan Wieck <jwieck@debis.com>Marc G. Fournier1998-02-241-5/+6
| | | | | | So if the relname is given to acldefault() in utils/adt/acl.c, it can do a IsSystemRelationName() on it and return ACL_RD instead of ACL_WORLD_DEFAULT.
* Quick cleanupsMarc G. Fournier1998-02-231-2/+3
|
* From: Jan Wieck <jwieck@debis.com>Marc G. Fournier1998-02-234-4/+50
| | | | | | | | | | | | | | | | | | | | | | | | | The diff looks so simple and easy. But to find it wasn't fun. It must have been there for a long time. What happened: When a tuple in one of some central catalogs was updated, the referenced relation got flushed, so it would be reopened on the next access (to reflect new triggers, rules and table structure changes into the relation cache). Some data (the tupleDescriptor e.g.) is used in the system cache too. So when a relation is subject to the system cache, this must know too that a cached system relation got flushed because the tupleDesc data gets freed during the flush! For the GRANT/REVOKE on pg_class it was slightly different. There is some local data in inval.c that gets initialized on the first invalidation of a tuple in some central catalogs. This needs a SysCache lookup in pg_class. But when the first of all commands is a GRANT on pg_class, exactly the needed tuple is the one actually invalidated. So I added little code snippets that the initialization of the local variables in inval.c will already happen during InitPostgres().
* ExecReScan for Unique & Sort nodes.Vadim B. Mikheev1998-02-231-3/+24
|
* From: Tom I Helbekkmo <tih@Hamartun.Priv.NO>Marc G. Fournier1998-02-141-4/+4
| | | | | | | The file 'backend/utils/adt/arrayfuncs.c' won't compile with the February 14th snapshot, because of an inconsistency between the declaration and implementation of ReadArrayStr(). As far as I can tell, the predeclaration is wrong. I assume this is what was meant:
* Atttypmod cleanup.Bruce Momjian1998-02-131-7/+8
|
* Goodbye register keyword. Compiler knows better.Bruce Momjian1998-02-1120-103/+103
|
* Pass around typmod as int16.Bruce Momjian1998-02-102-5/+5
|
* atttypmod now -1.Bruce Momjian1998-02-071-3/+3
|
* Vadim fix for vacuum analyze.Bruce Momjian1998-02-051-4/+4
|
* Fix for varchar functions, and indextyple j-1 fix.Bruce Momjian1998-02-051-3/+3
|
* Define boolean functions for lseg <, <=, <>, >=, >Thomas G. Lockhart1998-02-031-164/+505
| | | | | | | | | Define close_ls(), close_lseg(), lseg_length(). Write real code for close_sb(), close_pb(), inter_sb(), inter_lb(). Repair lseg_perp() which determines if two lsegs are perpendicular. Repair lseg_dt() distance between two lsegs. Note: close_sl() is clearly broken but will repair later (calculating point on lseg rather than point on line).
* No datedebug printing of date debug is not defined.Bruce Momjian1998-02-021-2/+4
|
* Move all the isinf() stuff from float.c to isinf.c, and build it according toMarc G. Fournier1998-02-021-128/+1
| | | | configure vs port specific #ifdef's...
* Fix for psort. fixes regression tests.Bruce Momjian1998-02-011-3/+2
|
* AIX patch from Darren King and Univel patch from Billy Allie, mostlyBruce Momjian1998-02-011-6/+2
| | | | related to grammar and parser issues, with one postmaster fix.
* fmgr_faddr cleanupBruce Momjian1998-01-311-4/+4
|
* fmgr_faddr cleanupBruce Momjian1998-01-312-7/+7
|
* Inline fmgr_faddr() for speed.Bruce Momjian1998-01-312-15/+19
|
* Inline fastgetattr and others so data access does not use functionBruce Momjian1998-01-319-28/+23
| | | | calls.
* From: Phil Thompson <phil@river-bank.demon.co.uk>Marc G. Fournier1998-01-292-4/+4
| | | | | | | | | | | Attached is the patch to fix the warning messages from my code. I also fixed one which wasn't my code. Apart from the usual warnings about the bison/yacc generated code I only have one other warning message. This is in gramm.y around line 2234. I wasn't sure of the fix. I've also replaced all the calls to free() in gramm.y to calls to pfree(). Without these I was getting backend crashes with GRANT. This might already have been fixed.
* From: Phil Thompson <phil@river-bank.demon.co.uk>Marc G. Fournier1998-01-261-2/+3
| | | | | | | | | | | | | | | | | | | I've completed the patch to fix the protocol and authentication issues I was discussing a couple of weeks ago. The particular changes are: - the protocol has a version number - network byte order is used throughout - the pg_hba.conf file is used to specify what method is used to authenticate a frontend (either password, ident, trust, reject, krb4 or krb5) - support for multiplexed backends is removed - appropriate changes to man pages - the -a switch to many programs to specify an authentication service no longer has any effect - the libpq.so version number has changed to 1.1 The new backend still supports the old protocol so old interfaces won't break.
* From: Jeroen van Vianen <jeroenv@design.nl>Marc G. Fournier1998-01-251-7/+6
| | | | | This patch solves the problem with multiple order by columns, with the first one having NULL values.
* getpid/pid cleanupBruce Momjian1998-01-253-7/+8
|
* This patch fixes one of two problems with grant/revoke statements on theMarc G. Fournier1998-01-251-3/+3
| | | | | | Linux platform. From: James Hughes <jamesh@interpath.com>
* Parser cleanup.Bruce Momjian1998-01-201-50/+61
| | | | Add lock to i386 asm.
* New pg_attribute.atttypmod for type-specific information likeBruce Momjian1998-01-161-11/+11
| | | | | | | | | | | varchar length. Cleans up code so attlen is always length. Removed varchar() hack added earlier. Will fix bug in selecting varchar() fields, and varchar() can be variable length.
* Fix for aggreg problem and fmgr.c compile problems.Bruce Momjian1998-01-151-4/+4
|
* Thank god for searchable mail archives.PostgreSQL Daemon1998-01-159-147/+157
| | | | | | | | | Patch by: wieck@sapserv.debis.de (Jan Wieck) 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.
* Cleanup of prototypes. FIx for PQtrace start/stop several times.Bruce Momjian1998-01-141-7/+4
|
* Various cleanups for the i386_solaris environmentMarc G. Fournier1998-01-131-8/+1
|
* Some *very* major changes by darrenk@insightdist.com (Darren King)Marc G. Fournier1998-01-132-25/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | ========================================== 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.) ==========================================
* > It seems there is a mistake in substr function:Marc G. Fournier1998-01-131-2/+2
| | | | | | | | | | | | | | | > 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) > From Edmund Mergl <E.Mergl@bawue.de>
* Cleanup of varchar.Bruce Momjian1998-01-081-33/+18
|
* Re-install working varchar() with compress size.Bruce Momjian1998-01-081-6/+3
|
* Completion of varchar rollback.Bruce Momjian1998-01-081-19/+19
|
* Cleanup of varchar.Bruce Momjian1998-01-081-2/+2
|
* Rollback varchar size change.Bruce Momjian1998-01-081-5/+24
|
* Fix for varchar I missed.Bruce Momjian1998-01-071-2/+2
|
* Goodbye ABORT. Hello ERROR for all errors.Bruce Momjian1998-01-0710-66/+63
|
* Allow varchar() to only store needed bytes. Remove PALLOC,PALLOCTYPE,PFREE. ↵Bruce Momjian1998-01-0710-244/+220
| | | | Clean up use of VARDATA.
* Change some ABORTS to ERROR. Add line number when COPY Failure.Bruce Momjian1998-01-0522-257/+257
|
* Change elog(WARN) to elog(ERROR) and elog(ABORT).Bruce Momjian1998-01-051-3/+6
|
* Change elog(WARN) to elog(ERROR) and elog(ABORT).Bruce Momjian1998-01-051-5/+5
|
* Change elog(WARN) to elog(ERROR) and elog(ABORT).Bruce Momjian1998-01-0532-321/+321
|
* Define text_substr().Thomas G. Lockhart1998-01-011-70/+99
| | | | | Change declarations from "struct varlena *" to "text *". Remove register variables since compiler should do better on its own.
* Change some mallocs to palloc.Bruce Momjian1997-12-291-5/+3
|
* Fix format to produce actual German style. Affects new "GERMAN" feature only.Thomas G. Lockhart1997-12-231-6/+6
|
* Change logic slightly to avoid one unnecessary calculation. No big deal.Thomas G. Lockhart1997-12-231-5/+9
|
View Lorry Controller Status