- 19 2月, 2003 18 次提交
-
-
由 Bruce Momjian 提交于
- more work from the SGML police - some grammar improvements: rewriting a paragraph or two, replacing contractions where (IMHO) appropriate - fix missing utility commands in lock mode docs - improve CLUSTER, REINDEX, SET SESSION AUTHORIZATION ref pages Neil Conway
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
implementation of '\e' history tracking for systems that have a readline compatability library without replace_history_entry. I fall back to pushing the query onto the history stack after the \e, rather than replacing it. The patch adds one more place to look for readline headers, and a test for replace_history_entry. I've only included the patch for configure.in Ross J. Reedstrom
-
由 Bruce Momjian 提交于
RelOid_pg_class, and transaction locks XactLockTableId. RelId is renamed to objId. - LockObject() and UnlockObject() functions created, and their use sprinkled throughout the code to do descent locking for domains and types. They accept lock modes AccessShare and AccessExclusive, as we only really need a 'read' and 'write' lock at the moment. Most locking cases are held until the end of the transaction. This fixes the cases Tom mentioned earlier in regards to locking with Domains. If the patch is good, I'll work on cleaning up issues with other database objects that have this problem (most of them). Rod Taylor
-
由 Bruce Momjian 提交于
Neil Conway
-
由 Bruce Momjian 提交于
7.3.2). It removes some code duplication and #ifdeffing, and some unstructured ugliness such as tacky breaks and an unneeded continue. Breaks up a large function into smaller functions and reduces required nesting levels, and kills a variable or two. Jeroen T. Vermeulen
-
由 Bruce Momjian 提交于
Oliver Elphick
-
由 Bruce Momjian 提交于
ltree_73.patch.gz - for 7.3 : Fix ~ operation bug: eg '1.1.1' ~ '*.1' ltree_74.patch.gz - for current CVS Fix ~ operation bug: eg '1.1.1' ~ '*.1' Add ? operation Optimize index storage Last change needs drop/create all ltree indexes, so only for 7.4 Teodor Sigaev
-
由 Bruce Momjian 提交于
functions which limited the maximum date for a timestamp to AD 1465001. The new limit is AD 5874897. The files affected are: doc/src/sgml/datatype.sgml: Documentation change due to patch. Included is a notice about the reduced range when using an eight-byte integer for timestamps. src/backend/utils/adt/datetime.c: Replacement functions for j2date() and date2j() functions. src/include/utils/datetime.h: Corrected a bug with the limit on the earliest possible date, Nov 23,-4713 has a Julian day count of -1. The earliest possible date should be Nov 24, -4713 with a day count of 0. src/test/regress/expected/horology-no-DST-before-1970.out: src/test/regress/expected/horology-solaris-1947.out: src/test/regress/expected/horology.out: Copies of expected output for regression testing. Note: Only horology.out has been physically tested. I do not have access to a Solaris box and I don't know how to provoke the "pre-1970" test. src/test/regress/sql/horology.sql: Added some test cases to check extended range. John Cochran
-
由 Bruce Momjian 提交于
(7.3 and current CVS) with support of int8, float4, float8 in addition to int4. Thanks Janko Richter for contribution. Oleg Bartunov
-
由 Bruce Momjian 提交于
additions to the docs. Neil Conway
-
由 Bruce Momjian 提交于
performance of min() and max() is slow when applied to the entire table, and suggesting the simple workaround most experienced Pg users eventually learn about (SELECT xyz ... ORDER BY xyz LIMIT 1). Neil Conway
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< * Prevent index uniqueness checks when UPDATE does not modifying column > * Prevent index uniqueness checks when UPDATE does not modify the column 235c235 < o Make PL/PgSQL %TYPE schema-aware > o -Make PL/PgSQL %TYPE schema-aware
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 18 2月, 2003 15 次提交
-
-
由 Bruce Momjian 提交于
> * Allow WAL information to recover corrupted pg_controldata
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Allow pg_dump to dump sequences using NO_MAXVALUE and NO_MINVALUE
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
known problem with failure to respond to 'pg_ctl stop -m fast', and probable problems if SIGINT or SIGTERM arrives while processing a SIGUSR2 interrupt that arrived while waiting for a new client query.
-
由 Bruce Momjian 提交于
> * Add a script to ask system configuration questions and tune postgresql.conf
-
由 Bruce Momjian 提交于
consistency.
-
由 Bruce Momjian 提交于
> * Allow CIDR format to be used in pg_hba.conf
-
由 Bruce Momjian 提交于
< o Allow CLUSTER to cluster all tables (Alvaro Herrera) > o -Allow CLUSTER to cluster all tables (Alvaro Herrera) 243c243 < * Allow pg_dump to dump a specific schema (Neil Conway) > * -Allow pg_dump to dump a specific schema (Neil Conway) 398c398 < * Make IN/NOT IN have similar performance to EXISTS/NOT EXISTS (Tom) > * -Make IN/NOT IN have similar performance to EXISTS/NOT EXISTS (Tom)
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> o -Add ALTER TABLE tab SET WITHOUT OIDS (Rod) > o -Allow CLUSTER to cluster all tables (Alvaro Herrera) > * -Allow pg_dump to dump a specific schema (Neil Conway) > * -Make IN/NOT IN have similar performance to EXISTS/NOT EXISTS (Tom) > * Rod is Rod Taylor <pg@rbt.ca)>
-
由 Bruce Momjian 提交于
< * -Make a transaction-safe TRUNCATE > * -Make a transaction-safe TRUNCATE (Rod)
-
由 Bruce Momjian 提交于
> * -Make a transaction-safe TRUNCATE
-
- 17 2月, 2003 1 次提交
-
-
由 Michael Meskes 提交于
-
- 16 2月, 2003 6 次提交
-
-
由 Tom Lane 提交于
in the case where the node immediately above the scan is a Hash, Sort, or Material node. In these cases it's better to do the projection so that we don't store unneeded columns in the hash/sort/materialize table. Per discussion a few days ago with Anagh Lal.
-
由 Tom Lane 提交于
that turn into CASE expressions. They evaluate their arguments at most once. Patch by Kris Jurka, review and (very light) editorializing by me.
-
由 Bruce Momjian 提交于
< * Disallow DROP COLUMN on a column that is part of a multi-column index > * Require DROP COLUMN CASCADE for a column that is part of a multi-column index
-
由 Tom Lane 提交于
a bad choice between sorted and hashed aggregation.
-
由 Tom Lane 提交于
the outer query. (The implementation is a bit klugy, but it would take nontrivial restructuring to make it nicer, which this is probably not worth.) This avoids unnecessary sort steps in examples like SELECT foo,count(*) FROM (SELECT ... ORDER BY foo,bar) sub GROUP BY foo which means there is now a reasonable technique for controlling the order of inputs to custom aggregates, even in the grouping case.
-
由 Bruce Momjian 提交于
> * Disallow DROP COLUMN on a column that is part of a multi-column index
-