aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Fix for psql help create table.Bruce Momjian1999-02-02
|
* Fix create_rule is->as.Bruce Momjian1999-02-02
|
* Fixed failed assertion happening in multiple action rulesJan Wieck1999-02-02
| | | | | | | when parsestate in makeRangeTable() already contains an opened p_target_relation. Jan
* Add TEMP tables/indexes. Add COPY pfree(). Other cleanups.Bruce Momjian1999-02-02
|
* Fixed growing of backend due to not pfree()'d data on COPY FROMJan Wieck1999-02-01
| | | | | | | Fixed growing of backend if BEFORE DELETE trigger returns heap tuple different from trigtuple. Jan
* Initialize es_snapshot.Vadim B. Mikheev1999-02-01
|
* Tighten coding in samekeys(). Pretty braindead change,Tom Lane1999-02-01
| | | | | but it saves almost 10% of the runtime in Charles Hornberger's optimizer example, so what the heck ...
* freebsd4.0 needed to be added to configure...Marc G. Fournier1999-02-01
|
* From: Michael Meskes <Michael.Meskes@usa.net>Marc G. Fournier1999-01-31
| | | | | | | | | | | | | | | + + Wed Jan 27 12:42:22 CET 1999 + + - Fixed bug that caused ecpg to lose 'goto' information. + - Set ecpg version to 2.4.7 + + Fri Jan 29 18:03:52 CET 1999 + + - Fixed bug that caused 'enum' to be rejected in pure C code. + - Fixed bug that caused function names to be translated to lower case. + - Set ecpg version to 2.4.8 +
* From: D'Arcy J.M. Cain <darcy@druid.net>Marc G. Fournier1999-01-31
| | | | | | | | | The following patch does two things. - Clarifies what the effect of allowing users to add new users (Thet become super-users.) - Makes the default database for the new user if they are not allowed to and the user agrees to create it.
* Fix postmaster to not try to start more than MaxBackendId children,Tom Lane1999-01-30
| | | | per patch from Tatsuo Ishii
* Small fix for READ COMMITTED isolevel.Vadim B. Mikheev1999-01-29
|
* Hope that execMain.c good merged.Vadim B. Mikheev1999-01-29
| | | | | Fix for BEFORE ROW UPDATE triggers: result tuple may be different (due to concurrent update) from one initially produced by top level plan.
* Trying to fix bad merging...Vadim B. Mikheev1999-01-29
|
* READ COMMITTED isolevel is implemented and is default now.Vadim B. Mikheev1999-01-29
|
* Changed qualification of pg_views and pg_tables to directlyJan Wieck1999-01-28
| | | | | | | check if a rewrite rule on SELECT exists/not exists instead of asking pg_get_viewdef() function. Jan
* New prebuilt versions of gram.c and scan.c for the mixed caseJan Wieck1999-01-28
| | | | | | identifier support. Jan
* Partial support for mixed case in PL/pgSQL.Jan Wieck1999-01-28
| | | | | | | | Left are identifiers that contain non-alnum/_ chars. So e.g. whitespaces in identifiers are still not supported. Jan
* Quick fix for subplan-related crash.Tom Lane1999-01-27
|
* Speedup of PL/pgSQL by calling ExecEvalExpr() directlyJan Wieck1999-01-27
| | | | | | instead of SPI_execp() for simple expressions. Jan
* fix for aggregatesBruce Momjian1999-01-27
|
* From: Tatsuo Ishii <t-ishii@sra.co.jp>Marc G. Fournier1999-01-27
| | | | | | Included patches fix a portability problem of unsetenv() used in 6.4.2 multi-byte support. unsetenv() is only avaliable on FreeBSD and Linux so I decided to replace with putenv().
* Turns out it's easy to cache the fmgr function lookupTom Lane1999-01-27
| | | | result, too ... another little bit of speed for SELECT.
* Another SELECT speedup: extract OIDs of column print functionsTom Lane1999-01-27
| | | | | only once per SELECT, not once per tuple. 10% here, 10% there, pretty soon you're talking about real speedups ...
* More agg cleanup.Bruce Momjian1999-01-26
|
* primary key support cleanups from D'Arcy...Marc G. Fournier1999-01-26
|
* pgindent file.Bruce Momjian1999-01-26
|
* From: Peter T Mount <peter@retep.org.uk>Marc G. Fournier1999-01-25
| | | | | | | | | This implements some of the JDBC2 methods, fixes a bug introduced into the JDBC1 portion of the driver, and introduces a new example, showing how to use the CORBA ORB thats in Java2 with JDBC. The Tar file contains the new files, the diff the changes to the others. CHANGELOG is separate as I forgot to make a .orig ;-)
* Agg/Aggreg cleanup and datetime.sql patch.Bruce Momjian1999-01-25
|
* SELECT FOR UPDATE is implemented...Vadim B. Mikheev1999-01-25
|
* Tighten coding of fmgr_isbuiltin() ... managed to speed it upTom Lane1999-01-25
| | | | by about 10% which seems to be good for half a percent or so of a SELECT.
* Tighten coding of inner loops in nocachegetattr ...Tom Lane1999-01-24
| | | | seems to have improved speed of routine by 5% or so ...
* Use heap_attisnull, rather than heap_getattr, for a smallTom Lane1999-01-24
| | | | but useful speedup.
* Replace typtoout() and gettypelem() with a single routine,Tom Lane1999-01-24
| | | | | | so that fetching an attribute value needs only one SearchSysCacheTuple call instead of two redundant searches. This speeds up a large SELECT by about ten percent, and probably will help GROUP BY and SELECT DISTINCT too.
* Fix a couple little problems with signed vs. unsignedTom Lane1999-01-24
| | | | characters ...
* Rename Aggreg to Aggref.Bruce Momjian1999-01-24
|
* Improper addition of NaN/Infinity recognition to float8in()Tom Lane1999-01-24
| | | | | | | was causing it not to detect out-of-range float values, as evidenced by failure of float8 regression test. I corrected that logic and also modified expected float8 results to account for new error message generated for out-of-range inputs.
* Remove unused Choose node.Bruce Momjian1999-01-23
|
* Add explicit buffering in backend libpq, to compensate forTom Lane1999-01-23
| | | | buffering lost by not going through stdio anymore for client I/O.
* Fix unportable test syntax in regression script.Tom Lane1999-01-23
|
* Fix for intersect FOR UPDATE check.Bruce Momjian1999-01-22
|
* Relcache Size fix.Bruce Momjian1999-01-22
|
* Fix for Size sizeof in cache code.Bruce Momjian1999-01-22
|
* |From: "D'Arcy" "J.M." Cain <darcy@druid.net>Marc G. Fournier1999-01-22
| | | | | | | |The following patch just prevents a warning from being generated because |the data type isn't specified.
* It seems that SPI_prepare() doesn't work well in some cases.Bruce Momjian1999-01-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Pawel Pierscionek [pawel@astercity.net] reported about the following case 1([SQL] drop table in pgsql). Michael Contzen [mcontzen@dohle.com] reported about the following case 2(PL/PGSQL bug using aggregates). You can find it from pgsql-hackers archive. 1. PL/pgSQL can't execute UTILITY commands. SPI_prepare() doesn't copy(save) the utilityStmt member of Query type nodes,because copyObject() is not implemented for nodes of (Create/Destroy etc)Stmt type. 2. Aggregates in PL/pgSQL cause wrong results. ... It's a list including Aggreg type nodes which exist in TargetList(i.e Aggreg type nodes are common to aggs member list and TargetList). AFAIC the common pointer is not copied to the same pointer by copyObject() function. In my patch I reconstruct aggs member node from new(copied) Agg type node. Is it proper to use set_agg_tlist_references() function to reconstruct aggs member node for Agg type nodes ? Thanks. Hiroshi Inoue Inoue@tpf.co.jp
* Here is a new version of my patch for allowing pg_dump to DROP schemaBruce Momjian1999-01-21
| | | | | | | | | | | | | | | | | | | elements prior to CREATEing new ones. It is under control of the -c command line option (with the default being status quo). The DROP TRIGGER portion still needs implementation. Anyone able to help clarify what exactly the CREATE TRIGGER portion does so I can fix this? Again, I have tried this with tables/indexes/sequences, but do not have other schema elements in my database. As a result, I am not 100% convinced that I got the syntax correct in all cases (but think I did, nonetheless). If anyone can check the other cases, I'd appreciate it. Cheers, Brook [I added manual page and sgml additions for the new -c option.]
* The following patch finishes primary key support. Previously, whenBruce Momjian1999-01-21
| | | | | | | | | | | | | | | | | | | | a field was labelled as a primary key, the system automatically created a unique index on the field. This patch extends it so that the index has the indisprimary field set. You can pull a list of primary keys with the followiing select. SELECT pg_class.relname, pg_attribute.attname FROM pg_class, pg_attribute, pg_index WHERE pg_class.oid = pg_attribute.attrelid AND pg_class.oid = pg_index.indrelid AND pg_index.indkey[0] = pg_attribute.attnum AND pg_index.indisunique = 't'; There is nothing in this patch that modifies the template database to set the indisprimary attribute for system tables. Should they be changed or should we only be concerned with user tables? D'Arcy
* From: Michael Meskes <Michael.Meskes@usa.net>Marc G. Fournier1999-01-21
| | | | See attached file. Now accepts "exec sql whenever sqlwarning".
* Copy RowMark node (it's for (-:)) FOR UPDATE).Vadim B. Mikheev1999-01-21
|
* FOR UPDATE is in parser & rules.Vadim B. Mikheev1999-01-21
|