- 17 2月, 2000 2 次提交
-
-
由 Tom Lane 提交于
selectivity functions and make the r-tree operators use them. The estimation functions themselves are just stubs, unfortunately, but perhaps someday someone will make them compute realistic estimates. Change pg_am so that the optimizer can reliably tell the difference between ordered and unordered indexes --- before it would think that an r-tree index can be scanned in '<<' order, which is not right AFAIK. Repair broken negator links for network_sup and related ops. Initdb forced. This might be my last initdb force for 7.0 ... hope so anyway ...
-
由 Thomas G. Lockhart 提交于
Transform datetime and timespan into timestamp and interval. Deprecate datetime and timespan, though translate to new types in gram.y. Transform all datetime and timespan catalog entries into new types. Make "INTERVAL" reserved word allowed as a column identifier in gram.y. Remove dt.h, dt.c files, and retarget datetime.h, datetime.c as utility routines for all date/time types. date.{h,c} now deals with date, time types. timestamp.{h,c} now deals with timestamp, interval types. nabstime.{h,c} now deals with abstime, reltime, tinterval types. Make NUMERIC a known native type for purposes of type coersion. Not tested.
-
- 16 2月, 2000 1 次提交
-
-
由 Tom Lane 提交于
accesses versus sequential accesses, a (very crude) estimate of the effects of caching on random page accesses, and cost to evaluate WHERE- clause expressions. Export critical parameters for this model as SET variables. Also, create SET variables for the planner's enable flags (enable_seqscan, enable_indexscan, etc) so that these can be controlled more conveniently than via PGOPTIONS. Planner now estimates both startup cost (cost before retrieving first tuple) and total cost of each path, so it can optimize queries with LIMIT on a reasonable basis by interpolating between these costs. Same facility is a win for EXISTS(...) subqueries and some other cases. Redesign pathkey representation to achieve a major speedup in planning (I saw as much as 5X on a 10-way join); also minor changes in planner to reduce memory consumption by recycling discarded Path nodes and not constructing unnecessary lists. Minor cleanups to display more-plausible costs in some cases in EXPLAIN output. Initdb forced by change in interface to index cost estimation functions.
-
- 15 2月, 2000 1 次提交
-
-
由 Thomas G. Lockhart 提交于
-
- 11 2月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
Don Baccus
-
- 31 1月, 2000 1 次提交
-
-
由 Jan Wieck 提交于
Jan
-
- 28 1月, 2000 1 次提交
-
-
由 Tom Lane 提交于
SELECT DISTINCT ON (expr [, expr ...]) targetlist ... and there is a check to make sure that the user didn't specify an ORDER BY that's incompatible with the DISTINCT operation. Reimplement nodeUnique and nodeGroup to use the proper datatype-specific equality function for each column being compared --- they used to do bitwise comparisons or convert the data to text strings and strcmp(). (To add insult to injury, they'd look up the conversion functions once for each tuple...) Parse/plan representation of DISTINCT is now a list of SortClause nodes. initdb forced by querytree change...
-
- 26 1月, 2000 2 次提交
-
-
由 Bruce Momjian 提交于
* Portions Copyright (c) 1996-2000, PostgreSQL, Inc to all files copyright Regents of Berkeley. Man, that's a lot of files.
-
由 Bruce Momjian 提交于
family functions. Contain: conversion from a datetype to formatted text: to_char( datetime, text) to_char( timestamp, text) to_char( int4, text) to_char( int8, text) to_char( float4, text) to_char( float8, text) to_char( numeric, text) vice versa: to_date ( text, text) to_datetime ( text, text) to_timestamp ( text, text) to_number ( text, text) (convert to numeric) PostgreSQL to_char is very compatible with Oracle's to_char(), but not total exactly (now). Small differentions are in number formating. It will fix in next to_char() version. ! If will this patch aplly to the main tree, must be delete the current to_char version in contrib (directory "dateformat" and note in contrib's README), this patch not erase it (sorry Bruce). The patch patching files: doc/src/sgml/func.sgml ^^^^^^^^ Hmm, I'm not sure if my English... :( Check it anyone (volunteer)? Thomas, it is right? SGML is not my primary lang and compile the current PG docs tree is very happy job (hard variables setting in docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/.... :-) What add any definition to global configure.in and set Makefiles in docs tree via ./configure? src/backend/utils/adt/Makefile src/backend/utils/adt/formatting.c src/include/catalog/pg_proc.h src/include/utils/formatting.h Karel Zak <zakkr@zf.jcu.cz> http://home.zf.jcu.cz/~zakkr/
-
- 24 1月, 2000 3 次提交
-
-
由 Tom Lane 提交于
(ie, WHERE x > lowbound AND x < highbound). It's not very bright yet but it does something useful. Also, rename intltsel/intgtsel to scalarltsel/scalargtsel to reflect usage better. Extend convert_to_scalar to do something a little bit useful with string data types. Still need to make it do something with date/time datatypes, but I'll wait for Thomas's datetime unification dust to settle first. Eventually the routine ought not have any type-specific knowledge at all; it ought to be calling a type-dependent routine found via a pg_type column; but that's a task for another day.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
optimizer.
-
- 23 1月, 2000 1 次提交
-
-
由 Tom Lane 提交于
pghackers discussion of 5-Jan-2000. The amopselect and amopnpages estimators are gone, and in their place is a per-AM amcostestimate procedure (linked to from pg_am, not pg_amop).
-
- 22 1月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 18 1月, 2000 1 次提交
-
-
由 Tatsuo Ishii 提交于
pg_char_to_encoding() pg_encoding_to_char()
-
- 17 1月, 2000 4 次提交
-
-
由 Tom Lane 提交于
Of the standard types, only 'timestamp' seems not to have an array type; should it be added, or are we going to remove that type for 7.0 anyway?
-
由 Tom Lane 提交于
comment style apparently isn't portable to other awks.
-
由 Tom Lane 提交于
data in its pg_proc entry. abs() doesn't require two arguments, last I heard.
-
由 Peter Eisentraut 提交于
-
- 16 1月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
- Prevent permissions on indexes - Instituted --enable-multibyte option and tweaked the MB build process where necessary - initdb prompts for superuser password
-
- 14 1月, 2000 1 次提交
-
-
由 Tom Lane 提交于
-
- 11 1月, 2000 4 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
and int2vector.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 10 1月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 07 1月, 2000 1 次提交
-
-
由 Jan Wieck 提交于
in trigger manager. Jan
-
- 28 12月, 1999 1 次提交
-
-
由 Jan Wieck 提交于
Jan
-
- 20 12月, 1999 1 次提交
-
-
由 Jan Wieck 提交于
Jan
-
- 17 12月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
initdb. No more obscure dependencies on environment variables or paths. It now finds the templates and the right postgres itself (with cmd line options as fallback). It also no longer depends on $USER (su safe), and doesn't advertise that --username allows you to install the db as a different user, since that doesn't work anyway. Also, recovery and cleanup on all errors. Consistent options, clearer documentation. Please take a look at this and adopt it if you feel it's safe enough. I have simulated all the stupid circumstances I could think of, but you never know with shell scripts. Oh yeah, you can give the postgres user a default password now. -- Peter Eisentraut Sernanders väg 10:115
-
由 Bruce Momjian 提交于
didn't have time for documentation yet, but I'll write some. There are still some things to work out what happens when you alter or drop users, but the group stuff in and by itself is done. -- Peter Eisentraut Sernanders väg 10:115
-
- 13 12月, 1999 1 次提交
-
-
由 Tom Lane 提交于
Note this forces initdb because of change of Aggref node in stored rules.
-
- 12 12月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
* Document/trigger/rule so changes to pg_shadow recreate pg_pwd I did it with a trigger and it seems to work like a charm. The function that already updates the file for create and alter user has been made a built-in "SQL" function and a trigger is created at initdb time. Comments around the pg_pwd updating function seem to be worried about this routine being called concurrently, but I really don't see a reason to worry about this. Verify for yourself. I guess we never had a system trigger before, so treat this with care, and feel free to adjust the nomenclature as well. -- Peter Eisentraut Sernanders väg 10:115
-
- 10 12月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 08 12月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 02 12月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 25 11月, 1999 3 次提交
-
-
由 Jan Wieck 提交于
comparision functions. Added all lztext comparision functions, operators and a default operator class for nbtree on lztext. Jan
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-