aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
* wups, took out one memset too many ...Tom Lane2003-07-22
|
* Error message editing in backend/libpq, backend/postmaster, backend/tcop.Tom Lane2003-07-22
| | | | | Along the way, fix some logic problems in pgstat_initstats, notably the bogus assumption that malloc returns zeroed memory.
* Error message editing in backend/access.Tom Lane2003-07-21
|
* Error message editing in backend/executor.Tom Lane2003-07-21
|
* Error message editing in backend/catalog.Tom Lane2003-07-21
|
* Another round of error message editing, covering backend/commands/.Tom Lane2003-07-20
|
* Error message editing: finish up undone task of reporting the problemTom Lane2003-07-19
| | | | xid when we fail to access pg_clog.
* Add ereport-related functions to GETTEXT_TRIGGERS list.Tom Lane2003-07-19
|
* Another round of error message editing, covering backend/parser/.Tom Lane2003-07-19
|
* First bits of work on error message editing.Tom Lane2003-07-18
|
* Add cleaner formatting to config file.Bruce Momjian2003-07-18
|
* Oh, for crying in a bucket ... relax Assert so that glibc's strxfrmTom Lane2003-07-17
| | | | does not dump core.
* Work around buggy strxfrm() present in some Solaris releases.Tom Lane2003-07-17
|
* For COMMENT ON DATABASE where database name is unknown or not the currentTom Lane2003-07-17
| | | | | | database, emit a WARNING and do nothing, rather than raising ERROR. Per recent discussion in which we concluded this is the best way to deal with database dumps that are reloaded into a database of a new name.
* Repair boundary-case bug introduced by patch of two months ago thatTom Lane2003-07-17
| | | | | | | | fixed incorrect initial setting of StartUpID. The logic in XLogWrite() expects that Write->curridx is advanced to the next page as soon as LogwrtResult points to the end of the current page, but StartupXLOG() failed to make that happen when the old WAL ended exactly on a page boundary. Per trouble report from Hannu Krosing.
* Make EXTRACT(TIMEZONE) and SET/SHOW TIMEZONE follow the SQL conventionTom Lane2003-07-17
| | | | | | for the sign of timezone offsets, ie, positive is east from UTC. These were previously out of step with other operations that accept or show timezones, such as I/O of timestamptz values.
* Add defenses against trying to attach qual conditions to a setOperationTom Lane2003-07-16
| | | | | | query node, since that won't work unless the planner is upgraded. Someday we should try to support at least some cases of this, but for now just plug the hole in the dike. Per discussion with Dmitry Tkach.
* Now that I look, SHOW TRANSACTION_ISOLATION isn't quite consistentTom Lane2003-07-15
| | | | with SET TRANSACTION_ISOLATION, either.
* Cause SHOW DATESTYLE to produce a string that will be accepted by SETTom Lane2003-07-15
| | | | | | DATESTYLE, for instance 'SQL, European' instead of 'SQL with European conventions'. Per gripe a month or two back from Barry Lind.
* Tweak original coding so that we can determine the platform-specificTom Lane2003-07-15
| | | | | | | | shared_buffers and max_connections values to use before we run the bootstrap process. Without this, initdb would fail on platforms where the hardwired default values are too large. (We could get around that by making the hardwired defaults tiny, perhaps, but why slow down bootstrap by starving it for buffers...)
* Make cost estimates for SubqueryScan more realistic: charge cpu_tuple_costTom Lane2003-07-14
| | | | | for each row processed, and don't forget the evaluation cost of any restriction clauses attached to the node. Per discussion with Greg Stark.
* The default values for shared_buffers and max_connections are now 1000Tom Lane2003-07-14
| | | | | | | | | and 100 respectively, if the platform will allow it. initdb selects values that are not too large to allow the postmaster to start, and places these values in the installed postgresql.conf file. This allows us to continue to start up out-of-the-box on platforms with small SHMMAX, while having somewhat-realistic default settings on platforms with reasonable SHMMAX. Per recent pghackers discussion.
* Fix a *second* buffer overrun bug in to_ascii(). Grumble.Tom Lane2003-07-14
|
* Add description for new GUC context.Bruce Momjian2003-07-09
| | | | Aizaz Ahmed
* Add special checks for non-super-user setting LOG_MIN_DURATION_STATEMENTBruce Momjian2003-07-09
| | | | to zero.
* Add new USERLIMIT GUC source level so certain options can be disabledBruce Momjian2003-07-09
| | | | | | | or increased only by super-users. This fixes problems caused by making certain variables SUSET for security reasons.
* tm2timestamp should return -1, not elog, on overflow. (In the backendTom Lane2003-07-04
| | | | | this is merely an API inconsistency, but in ecpg it's fatal.) Also, fix misconceived overflow test in HAVE_INT64_TIMESTAMP case.
* Add --help-config facility to dump information about GUC parametersTom Lane2003-07-04
| | | | | | without needing a running backend. Reorder postgresql.conf.sample to match new layout of runtime.sgml. This commit re-adds work lost in Wednesday's crash.
* Some early work on error message editing. Operator-not-found andTom Lane2003-07-04
| | | | | function-not-found messages now distinguish the cases no-match and ambiguous-match, and they follow the style guidelines too.
* Fix bug I introduced in recent rewrite of NUMERIC code: numeric toTom Lane2003-07-03
| | | | | integer conversions gave the wrong answer for values with stripped trailing zeroes, such as 10000000.
* Do honest transformation and preprocessing of LIMIT/OFFSET clauses,Tom Lane2003-07-03
| | | | | | | | instead of the former kluge whereby gram.y emitted already-transformed expressions. This is needed so that Params appearing in these clauses actually work correctly. I suppose some might claim that the side effect of 'SELECT ... LIMIT 2+2' working is a new feature, but I say this is a bug fix.
* Code review for UPDATE tab SET col = DEFAULT patch ... whack it aroundTom Lane2003-07-03
| | | | so it has some chance of working in rules ...
* Aggregates can be polymorphic, using polymorphic implementation functions.Tom Lane2003-07-01
| | | | | | It also works to create a non-polymorphic aggregate from polymorphic functions, should you want to do that. Regression test added, docs still lacking. By Joe Conway, with some kibitzing from Tom Lane.
* Dept. of second thoughts: supporting inlining of polymorphic SQL functionsTom Lane2003-07-01
| | | | | takes only a few more lines of code than preventing it, so might as well support it.
* STRENGH => STRENGTH, per Jon Jensen.Tom Lane2003-07-01
|
* Department of second thoughts: even if we can't run the full parser onTom Lane2003-07-01
| | | | | a SQL function with polymorphic inputs, we can at least run the raw parser to catch silly syntactic errors.
* SQL functions can have arguments and results declared ANYARRAY orTom Lane2003-07-01
| | | | | | | | ANYELEMENT. The effect is to postpone typechecking of the function body until runtime. Documentation is still lacking. Original patch by Joe Conway, modified to postpone type checking by Tom Lane.
* Change EXECUTE INTO to CREATE TABLE AS EXECUTE.Peter Eisentraut2003-07-01
|
* Add GUC option log_error_verbosity to control which fields of errorTom Lane2003-06-30
| | | | | | reports get put into the postmaster log. Options are TERSE, DEFAULT, VERBOSE, with the same behavior as implemented on the client side in libpq.
* Restructure building of join relation targetlists so that a join planTom Lane2003-06-29
| | | | | | | | | | | | | | node emits only those vars that are actually needed above it in the plan tree. (There were comments in the code suggesting that this was done at some point in the dim past, but for a long time we have just made join nodes emit everything that either input emitted.) Aside from being marginally more efficient, this fixes the problem noted by Peter Eisentraut where a join above an IN-implemented-as-join might fail, because the subplan targetlist constructed in the latter case didn't meet the expectation of including everything. Along the way, fix some places that were O(N^2) in the targetlist length. This is not all the trouble spots for wide queries by any means, but it's a step forward.
* Information schema views for group privileges, some corrections on columnPeter Eisentraut2003-06-29
| | | | privileges.
* It was comparing the wrong pair of columns, which triggered the previouslyPeter Eisentraut2003-06-29
| | | | mentioned bug.
* Add missing PO files from last commit.Peter Eisentraut2003-06-29
|
* Support expressions of the form 'scalar op ANY (array)' andTom Lane2003-06-29
| | | | | | | | | | 'scalar op ALL (array)', where the operator is applied between the lefthand scalar and each element of the array. The operator must yield boolean; the result of the construct is the OR or AND of the per-element results, respectively. Original coding by Joe Conway, after an idea of Peter's. Rewritten by Tom to keep the implementation strictly separate from subqueries.
* Merge PO file updates from 7.3 branch.Peter Eisentraut2003-06-28
|
* Make information schema aware of arrays.Peter Eisentraut2003-06-28
| | | | | The view element_types is currently not functional, awaiting some fixes in the planner (reported on -hackers).
* Add is_superuser parameter reporting, soon to be used by psql.Tom Lane2003-06-27
|
* Fix compile warnings.Tom Lane2003-06-27
|
* First batch of object rename commands.Peter Eisentraut2003-06-27
|
* Create real array comparison functions (that use the element datatype'sTom Lane2003-06-27
| | | | | | | | | | | | | | | | comparison functions), replacing the highly bogus bitwise array_eq. Create a btree index opclass for ANYARRAY --- it is now possible to create indexes on array columns. Arrange to cache the results of catalog lookups across multiple array operations, instead of repeating the lookups on every call. Add string_to_array and array_to_string functions. Remove singleton_array, array_accum, array_assign, and array_subscript functions, since these were for proof-of-concept and not intended to become supported functions. Minor adjustments to behavior in some corner cases with empty or zero-dimensional arrays. Joe Conway (with some editorializing by Tom Lane).
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 02:44:11 +0000