- 11 3月, 2006 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Neil Conway 提交于
var_samp(), stddev_pop(), and stddev_samp(). var_samp() and stddev_samp() are just renamings of the historical Postgres aggregates variance() and stddev() -- the latter names have been kept for backward compatibility. This patch includes updates for the documentation and regression tests. The catversion has been bumped. NB: SQL2003 requires that DISTINCT not be specified for any of these aggregates. Per discussion on -patches, I have NOT implemented this restriction: if the user asks for stddev(DISTINCT x), presumably they know what they are doing.
-
- 07 3月, 2006 3 次提交
-
-
由 Tom Lane 提交于
not likely ever to be implemented seeing it's been removed from SQL2003. This allows getting rid of the 'filter' version of yylex() that we had in parser.c, which should save at least a few microseconds in parsing.
-
由 Bruce Momjian 提交于
- new function justify_interval(interval) - modified function justify_hours(interval) - modified function justify_days(interval) These functions are defined to meet the requirements as discussed in this thread. Specifically: - justify_hours makes certain the sign bit on the hours matches the sign bit on the days. It only checks the sign bit on the days, and not the months, when determining if the hours should be positive or negative. After the call, -24 < hours < 24. - justify_days makes certain the sign bit on the days matches the sign bit on the months. It's behavior does not depend on the hours, nor does it modify the hours. After the call, -30 < days < 30. - justify_interval makes sure the sign bits on all three fields months, days, and hours are all the same. After the call, -24 < hours < 24 AND -30 < days < 30. Mark Dilger
-
由 Bruce Momjian 提交于
Kevin Grittner
-
- 05 3月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 03 3月, 2006 1 次提交
-
-
由 Tom Lane 提交于
-
- 01 3月, 2006 1 次提交
-
-
由 Tom Lane 提交于
creation of a shell type. This allows a less hacky way of dealing with the mutual dependency between a datatype and its I/O functions: make a shell type, then make the functions, then define the datatype fully. We should fix pg_dump to handle things this way, but this commit just deals with the backend. Martijn van Oosterhout, with some corrections by Tom Lane.
-
- 28 2月, 2006 1 次提交
-
-
由 Peter Eisentraut 提交于
particular get rid of single quotes around language names and old WITH () construct.
-
- 27 2月, 2006 1 次提交
-
-
由 Neil Conway 提交于
Kirkwood, minor improvements by Neil Conway. The regression tests have been updated and the catversion has been bumped.
-
- 19 2月, 2006 2 次提交
-
-
由 Neil Conway 提交于
required by the SQL standard, and TABLESPACE is useful functionality. Patch from Kris Jurka, minor editorialization by Neil Conway.
-
由 Peter Eisentraut 提交于
up a bunch of the support utilities. In src/backend/utils/mb/Unicode remove nearly duplicate copies of the UCS_to_XXX perl script and replace with one version to handle all generic files. Update the Makefile so that it knows about all the map files. This produces a slight difference in some of the map files, using a uniform naming convention and not mapping the null character. In src/backend/utils/mb/conversion_procs create a master utf8<->win codepage function like the ISO 8859 versions instead of having a separate handler for each conversion. There is an externally visible change in the name of the win1258 to utf8 conversion. According to the documentation notes, it was named incorrectly and this changes it to a standard name. Running the Unicode mapping perl scripts has shown some additional mapping changes in koi8r and iso8859-7.
-
- 13 2月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME Joachim Wieland
-
- 12 2月, 2006 6 次提交
-
-
由 Tom Lane 提交于
it to report reasonable errors in error cases.
-
由 Bruce Momjian 提交于
records and row types. Pavel Stehule
-
由 Bruce Momjian 提交于
comments on cluster global objects like databases, tablespaces, and roles. It touches a lot of places, but not much in the way of big changes. The only design decision I made was to duplicate the query and manipulation functions rather than to try and have them handle both shared and local comments. I believe this is simpler for the code and not an issue for callers because they know what type of object they are dealing with. This has resulted in a shobj_description function analagous to obj_description and backend functions [Create/Delete]SharedComments mirroring the existing [Create/Delete]Comments functions. pg_shdescription.h goes into src/include/catalog/ Kris Jurka
-
由 Tom Lane 提交于
This is mostly just over-compulsiveness on my part, but the exercise did reveal one real bug: errors.out has a space difference now where it should not.
-
由 Bruce Momjian 提交于
Joachim Wieland
-
由 Tom Lane 提交于
inet operators.
-
- 11 2月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
minus inet. Stephen R. van den Berg
-
- 10 2月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
If the second output column value is 'a\nb', the 'b' should appear in the second display column, rather than the first column as it does now. Change libpq's PQdsplen() to return more useful values. > Note: this changes the PQdsplen function, it can now return zero or > minus one which was not possible before. It doesn't appear anyone is > actually using the functions other than psql but it is a change. The > functions are not actually documentated anywhere so it's not like we're > breaking a defined interface. The new semantics follow the Unicode > standard. BACKWARD COMPATIBLE CHANGE. The only user-visible change I saw in the regression tests is that a SELECT * on a table where all the columns have been dropped doesn't return a blank line like before. This seems like a step forward. Martijn van Oosterhout
-
- 05 2月, 2006 1 次提交
-
-
由 Andrew Dunstan 提交于
DROP IF EXISTS for ROLE/USER/GROUP
-
- 26 1月, 2006 2 次提交
-
-
由 Tom Lane 提交于
and rely exclusively on the SQL type system to tell the difference between the types. Prevent creation of invalid CIDR values via casting from INET or set_masklen() --- both of these operations now silently zero any bits to the right of the netmask. Remove duplicate CIDR comparison operators, letting the type rely on the INET operators instead.
-
由 Bruce Momjian 提交于
instead of "10^0".
-
- 22 1月, 2006 1 次提交
-
-
由 Neil Conway 提交于
and DELETE. If specified, the alias must be used instead of the full table name. Also, the alias currently cannot be used in the SET clause of UPDATE. Patch from Atsushi Ogawa, various editorialization by Neil Conway. Along the way, make the rowtypes regression test pass if add_missing_from is enabled, and add a new (skeletal) regression test for DELETE.
-
- 21 1月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
Continue to support GRANT ON [TABLE] for sequences for backward compatibility; issue warning for invalid sequence permissions. [Backward compatibility warning message.] Add USAGE permission for sequences that allows only currval() and nextval(), not setval(). Mention object name in grant/revoke warnings because of possible multi-object operations.
-
- 18 1月, 2006 1 次提交
-
-
由 Neil Conway 提交于
cursors. Patch from Joachim Wieland, review and ediorialization by Neil Conway. The view lists cursors defined by DECLARE CURSOR, using SPI, or via the Bind message of the frontend/backend protocol. This means the view does not list the unnamed portal or the portal created to implement EXECUTE. Because we do list SPI portals, there might be more rows in this view than you might expect if you are using SPI implicitly (e.g. via a procedural language). Per recent discussion on -hackers, the query string included in the view for cursors defined by DECLARE CURSOR is based on debug_query_string. That means it is not accurate if multiple queries separated by semicolons are submitted as one query string. However, there doesn't seem a trivial fix for that: debug_query_string is better than nothing. I also changed SPI_cursor_open() to include the source text for the portal it creates: AFAICS there is no reason not to do this. Update the documentation and regression tests, bump the catversion.
-
- 17 1月, 2006 1 次提交
-
-
由 Neil Conway 提交于
an array of regtype, rather than an array of OIDs. This is likely to be more useful to user, and the type OID can easily be obtained by casting a regtype value to OID. Per suggestion from Tom. Update the documentation and regression tests, and bump the catversion.
-
- 16 1月, 2006 2 次提交
-
-
由 Neil Conway 提交于
to prepared statements with unknown type are correctly enforced, per recent bug report.
-
由 Neil Conway 提交于
data type is unspecified or is declared to be "unknown", the type will be inferred from the context in which the parameter is used. This was already possible for protocol-level prepared statements.
-
- 12 1月, 2006 1 次提交
-
-
由 Tom Lane 提交于
Replace the former ad-hoc implementation used in the regression tests. Joachim Wieland
-
- 11 1月, 2006 1 次提交
-
-
由 Tom Lane 提交于
-
- 08 1月, 2006 1 次提交
-
-
由 Neil Conway 提交于
access information about the prepared statements that are available in the current session. Original patch from Joachim Wieland, various improvements by Neil Conway. The "statement" column of the view contains the literal query string sent by the client, without any rewriting or pretty printing. This means that prepared statements created via SQL will be prefixed with "PREPARE ... AS ", whereas those prepared via the FE/BE protocol will not. That is unfortunate, but discussion on -patches did not yield an efficient way to improve this, and there is some merit in returning exactly what the client sent to the backend. Catalog version bumped, regression tests updated.
-
- 05 1月, 2006 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 29 12月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
wording ("table" added).
-
- 28 12月, 2005 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
single column dump that has a \. value, so the load works properly. I also added documentation describing this issue.
-
由 Tom Lane 提交于
(previously we only did = and <> correctly). Also, allow row comparisons with any operators that are in btree opclasses, not only those with these specific names. This gets rid of a whole lot of indefensible assumptions about the behavior of particular operators based on their names ... though it's still true that IN and NOT IN expand to "= ANY". The patch adds a RowCompareExpr expression node type, and makes some changes in the representation of ANY/ALL/ROWCOMPARE SubLinks so that they can share code with RowCompareExpr. I have not yet done anything about making RowCompareExpr an indexable operator, but will look at that soon. initdb forced due to changes in stored rules.
-
- 15 12月, 2005 1 次提交
-
-
由 Tom Lane 提交于
example from Jim Dew. Add some simple regression tests, since this is an area we seem to break regularly :-(
-