- 29 1月, 1999 1 次提交
-
-
由 Vadim B. Mikheev 提交于
-
- 28 1月, 1999 6 次提交
-
-
由 Jan Wieck 提交于
check if a rewrite rule on SELECT exists/not exists instead of asking pg_get_viewdef() function. Jan
-
由 Jan Wieck 提交于
identifier support. Jan
-
由 Jan Wieck 提交于
Left are identifiers that contain non-alnum/_ chars. So e.g. whitespaces in identifiers are still not supported. Jan
-
由 Tom Lane 提交于
-
由 Jan Wieck 提交于
instead of SPI_execp() for simple expressions. Jan
-
由 Bruce Momjian 提交于
-
- 27 1月, 1999 4 次提交
-
-
由 Marc G. Fournier 提交于
From: Tatsuo Ishii <t-ishii@sra.co.jp> 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().
-
由 Tom Lane 提交于
result, too ... another little bit of speed for SELECT.
-
由 Tom Lane 提交于
only once per SELECT, not once per tuple. 10% here, 10% there, pretty soon you're talking about real speedups ...
-
由 Bruce Momjian 提交于
-
- 26 1月, 1999 4 次提交
-
-
由 Marc G. Fournier 提交于
primary key support cleanups from D'Arcy...
-
由 Bruce Momjian 提交于
-
由 Marc G. Fournier 提交于
From: Peter T Mount <peter@retep.org.uk> 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 ;-)
-
由 Bruce Momjian 提交于
-
- 25 1月, 1999 4 次提交
-
-
由 Vadim B. Mikheev 提交于
-
由 Tom Lane 提交于
by about 10% which seems to be good for half a percent or so of a SELECT.
-
由 Tom Lane 提交于
seems to have improved speed of routine by 5% or so ...
-
由 Tom Lane 提交于
but useful speedup.
-
- 24 1月, 1999 7 次提交
-
-
由 Tom Lane 提交于
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.
-
由 Tom Lane 提交于
characters ...
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
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.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
buffering lost by not going through stdio anymore for client I/O.
-
由 Tom Lane 提交于
-
- 23 1月, 1999 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 22 1月, 1999 8 次提交
-
-
由 Marc G. Fournier 提交于
|From: "D'Arcy" "J.M." Cain <darcy@druid.net> | |The following patch just prevents a warning from being generated because |the data type isn't specified.
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
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.]
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
pgsql-6.3.2. I think array_iterator is a great thing to have!!! With best regards, Tobias Gabele
-
由 Marc G. Fournier 提交于
From: Michael Meskes <Michael.Meskes@usa.net> See attached file. Now accepts "exec sql whenever sqlwarning".
-
由 Vadim B. Mikheev 提交于
-
由 Vadim B. Mikheev 提交于
-
- 21 1月, 1999 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Thomas G. Lockhart 提交于
They are not corrected now. Allow the date type to accept BC dates. Share more date/time validation declarations through dt.h.
-