aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Get rid of the pg_shdepend entry for a TOAST table; it's unnecessary sinceTom Lane2007-05-14
| | | | | | | there's an indirect dependency on the owner via the parent table. We were already handling indexes that way, but not toast tables for some reason. Saves a little catalog space and cuts down the verbosity of checkSharedDependencies reports.
* Fix up grammar and translatability of recent checkSharedDependenciesTom Lane2007-05-14
| | | | patch; also make the code logic a bit more self-consistent.
* Prevent RevalidateCachedPlan from making any permanent change inTom Lane2007-05-14
| | | | | | | | | ActiveSnapshot. Having it affect ActiveSnapshot only in the unusual case of needing to replan seems a bad idea, and there's also the problem that the created snap might be in a relatively short-lived context, as noted by Jan Wieck. Also, there's no need to force a new snap at all unless we are called with no snap currently set, which is an unusual case in itself.
* Report all dependent objects to the server log when a shared object is dropped,Alvaro Herrera2007-05-14
| | | | | | | | | | | and only a truncated log of the objects in the current database to the client. Also, instead of reporting object counts for all databases on which the user might own objects, report only as many as fit in the predefined line count. This is to avoid flooding the client when the user owns too many objects, which could cause problems. Per report from Ed L. on April 4th and subsequent discussion.
* Update instructions on creating TODO entry.Bruce Momjian2007-05-14
|
* Log directory we're installing into.Magnus Hagander2007-05-13
| | | | Per request from Andrew Dunstan.
* Mark as done, add URL for other item:Bruce Momjian2007-05-13
| | | | | | | | < o Add support for arrays of complex types > > http://archives.postgresql.org/pgsql-patches/2007-05/msg00114.php > > o -Add support for arrays of complex types
* Add:Bruce Momjian2007-05-12
| | | | | | > * Have configure choose integer datetimes by default > > http://archives.postgresql.org/pgsql-patches/2007-05/msg00046.php
* Add:Bruce Momjian2007-05-12
| | | | | | > o Allow data to be passed in native language formats, rather > than only text > http://archives.postgresql.org/pgsql-hackers/2007-05/msg00289.php
* Improve predicate_refuted_by_simple_clause() to handle IS NULL and IS NOT NULLTom Lane2007-05-12
| | | | | | | more completely. The motivation for having it understand IS NULL at all was to allow use of "foo IS NULL" as one of the subsets of a partitioning on "foo", but as reported by Aleksander Kmetec, it wasn't really getting the job done. Backpatch to 8.2 since this is arguably a performance bug.
* Fix the problem that creating a user-defined type named _foo, followed by oneTom Lane2007-05-12
| | | | | | | | | | | named foo, would work but the other ordering would not. If a user-specified type or table name collides with an existing auto-generated array name, just rename the array type out of the way by prepending more underscores. This should not create any backward-compatibility issues, since the cases in which this will happen would have failed outright in prior releases. Also fix an oversight in the arrays-of-composites patch: ALTER TABLE RENAME renamed the table's rowtype but not its array type.
* Fix my oversight in enabling domains-of-domains: ALTER DOMAIN ADD CONSTRAINTTom Lane2007-05-11
| | | | | | | | | | | | needs to check the new constraint against columns of derived domains too. Also, make it error out if the domain to be modified is used within any composite-type columns. Eventually we should support that case, but it seems a bit painful, and not suitable for a back-patch. For the moment just let the user know we can't do it. Backpatch to 8.2, which is the only released version that allows nested domains. Possibly the other part should be back-patched further.
* Improvements to the SGML docs for TRUNCATE and CLUSTER.Neil Conway2007-05-11
|
* Support arrays of composite types, including the rowtypes of regular tablesTom Lane2007-05-11
| | | | | | | | | | | | | | | and views (but not system catalogs, nor sequences or toast tables). Get rid of the hardwired convention that a type's array type is named exactly "_type", instead using a new column pg_type.typarray to provide the linkage. (It still will be named "_type", though, except in odd corner cases such as maximum-length type names.) Along the way, make tracking of owner and schema dependencies for types more uniform: a type directly created by the user has these dependencies, while a table rowtype or auto-generated array type does not have them, but depends on its parent object instead. David Fetter, Andrew Dunstan, Tom Lane
* Added some more error logging.Michael Meskes2007-05-10
|
* - Synced parser and keyword listMichael Meskes2007-05-10
| | | | - Renamed update test so it hopefully runs on Vista
* Reserve some pg_statistic "kind" codes for use by the ESRI ST_GeometryTom Lane2007-05-08
| | | | datatype project. Per request from Ale Raza (araza at esri.com).
* Add a hash function for "numeric". Mark the equality operator forNeil Conway2007-05-08
| | | | | | | | | | | | | | | numerics as "oprcanhash", and make the corresponding system catalog updates. As a result, hash indexes, hashed aggregation, and hash joins can now be used with the numeric type. Bump the catversion. The only tricky aspect to doing this is writing a correct hash function: it's possible for two Numerics to be equal according to their equality operator, but have different in-memory bit patterns. To cope with this, the hash function doesn't consider the Numeric's "scale" or "sign", and explictly skips any leading or trailing zeros in the Numeric's digit buffer (the current implementation should suppress any such zeros, but it seems unwise to rely upon this). See discussion on pgsql-patches for more details.
* Add an explicit comment about POSIX time zone names having the reverseTom Lane2007-05-08
| | | | | | sign convention from everyplace else in Postgres. I don't suppose that this will stop people from being confused, but at least we can say that it's documented.
* The appended patch addresses the outstanding issues of the recent guc patch.Peter Eisentraut2007-05-08
| | | | | | | It makes PGCLIENTENCODING work again and uses bsearch() instead of iterating over the array of guc variables in guc_get_index(). Joachim Wieland
* Make sure we don't skip databases that are supposed to be vacuumed "exactlyAlvaro Herrera2007-05-07
| | | | | | now". This can happen if the time granularity is not very high. Per ITAGAKI Takahiro.
* Grammar correctionPeter Eisentraut2007-05-07
|
* Doc tweak: add an xref.Neil Conway2007-05-07
|
* Check return code from strxfrm on Windows since it has aMagnus Hagander2007-05-05
| | | | | non-standard way of indicating errors, so we don't try to allocate INT_MAX bytes to store a result in.
* Done:Bruce Momjian2007-05-05
| | | | | | | | | | | | | | | | | | | | | | | < Last updated: Sat May 5 10:47:39 EDT 2007 > Last updated: Sat May 5 11:39:57 EDT 2007 < * Flush cached query plans when the dependent objects change, < when the cardinality of parameters changes dramatically, or > * -Flush cached query plans when the dependent objects change or < < A more complex solution would be to save multiple plans for different < cardinality and use the appropriate plan based on the EXECUTE values. < < * Track dependencies in function bodies and recompile/invalidate < < This is particularly important for references to temporary tables < in PL/PgSQL because PL/PgSQL caches query plans. The only workaround < in PL/PgSQL is to use EXECUTE. One complexity is that a function < might itself drop and recreate dependent tables, causing it to < invalidate its own query plan. < < * Invalidate prepared queries, like INSERT, when the table definition > * -Track dependencies in function bodies and recompile/invalidate > * -Invalidate prepared queries, like INSERT, when the table definition
* Move item:Bruce Momjian2007-05-05
| | | | | | | | < * Invalidate prepared queries, like INSERT, when the table definition < is altered > > * Invalidate prepared queries, like INSERT, when the table definition > is altered
* Done:Bruce Momjian2007-05-05
| | | | > o -Allow multiple vacuums so large tables do not starve small
* Wording update to FAQ_DEV..Bruce Momjian2007-05-05
|
* Add note to FAQ_DEV that regression tests might need to be added.Bruce Momjian2007-05-05
|
* In developer's FAQ, update list API, from Tom Lane.Bruce Momjian2007-05-05
|
* Add FAQ item about how patches are reviewed.Bruce Momjian2007-05-05
|
* Done:Bruce Momjian2007-05-05
| | | | | | | | | | > * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < < Right now, if no index exists, ORDER BY ... LIMIT # requires we sort < all values to return the high/low value. Instead The idea is to do a < sequential scan to find the high/low value, thus avoiding the sort. < MIN/MAX already does this, but not for LIMIT > 1. <
* Add a line to the EXPLAIN ANALYZE output for a Sort node, showing theTom Lane2007-05-04
| | | | actual sort strategy and amount of space used. By popular demand.
* tas() support for Renesas' M32R processor. Kazuhiro InaokaTom Lane2007-05-04
|
* Make clearer how arguments and return values in pl/perl are escaped. This is ↵Andrew Dunstan2007-05-04
| | | | to clarify the situation that Theo Schlossnagle recently reported on -bugs.
* Suppress a recently-introduced 'variable might be clobbered by longjmp' warning.Tom Lane2007-05-04
|
* A few fixups in error handling: mark pg_re_throw() as noreturn for gcc,Tom Lane2007-05-04
| | | | | | | and for other compilers, insert a dummy exit() call so that they understand PG_RE_THROW() doesn't return. Insert fflush(stderr) in ExceptionalCondition, per recent buildfarm evidence that that might not happen automatically on some platforms. And const-ify ExceptionalCondition's declaration while at it.
* Teach tuplesort.c about "top N" sorting, in which only the first N tuplesTom Lane2007-05-04
| | | | | | | | | | need be returned. We keep a heap of the current best N tuples and sift-up new tuples into it as we scan the input. For M input tuples this means only about M*log(N) comparisons instead of M*log(M), not to mention a lot less workspace when N is small --- avoiding spill-to-disk for large M is actually the most attractive thing about it. Patch includes planner and executor support for invoking this facility in ORDER BY ... LIMIT queries. Greg Stark, with some editorialization by moi.
* Tweak hash index AM to use the new ReadOrZeroBuffer bufmgr API when fetchingTom Lane2007-05-03
| | | | | | | pages it intends to zero immediately. Just to show there is some use for that function besides WAL recovery :-). Along the way, fold _hash_checkpage and _hash_pageinit calls into _hash_getbuf and friends, instead of expecting callers to do that separately.
* Fix a few more double words in docs.Alvaro Herrera2007-05-03
|
* Fix some typos in the documentation. Patch from Brian Gough. BackportNeil Conway2007-05-03
| | | | the relevant fixes to 8.2 as well.
* Release builds generate different strangely formatted export namesMagnus Hagander2007-05-03
| | | | | | for local symbols, that shouldn't be exported. This patch excludes them, cutting down about 10,000 exported symbols and decreasing the binary size by 20%.
* Dept. of second thoughts: add comments cautioning against usingTom Lane2007-05-02
| | | | | | | ReadOrZeroBuffer to fetch pages from beyond physical EOF. This would usually work, but would cause problems for md.c if writes occurred beyond a segment boundary when the previous segment file hadn't been fully extended.
* During WAL recovery, when reading a page that we intend to overwrite completelyTom Lane2007-05-02
| | | | | | | | | | | | from the WAL data, don't bother to physically read it; just have bufmgr.c return a zeroed-out buffer instead. This speeds recovery significantly, and also avoids unnecessary failures when a page-to-be-overwritten has corrupt page headers on disk. This replaces a former kluge that accomplished the latter by pretending zero_damaged_pages was always ON during WAL recovery; which was OK when the kluge was put in, but is unsafe when restoring a WAL log that was written with full_page_writes off. Heikki Linnakangas
* Fix things so that when CREATE INDEX CONCURRENTLY sets pg_index.indisvalidTom Lane2007-05-02
| | | | | | | | | | | | true at the very end of its processing, the update is broadcast via a shared-cache-inval message for the index; without this, existing backends that already have relcache entries for the index might never see it become valid. Also, force a relcache inval on the index's parent table at the same time, so that any cached plans for that table are re-planned; this ensures that the newly valid index will be used if appropriate. Aside from making C.I.C. behave more reasonably, this is necessary infrastructure for some aspects of the HOT patch. Pavan Deolasee, with a little further stuff from me.
* Use the new TimestampDifferenceExceeds API instead of timestamp_cmp_internalAlvaro Herrera2007-05-02
| | | | | | and TimestampDifference, to make coding clearer. I think this should also fix the failure to start workers in platforms with low resolution timers, as reported by Itagaki Takahiro.
* Fix failure to check for INVALID worker entry in the new autovacuum code, whichAlvaro Herrera2007-05-02
| | | | | could happen when a worker took to long to start and was thus "aborted" by the launcher. Noticed by lionfish buildfarm member.
* Fix oversight in PG_RE_THROW processing: it's entirely possible that thereTom Lane2007-05-02
| | | | | | | | | | | | | | isn't any place to throw the error to. If so, we should treat the error as FATAL, just as we would have if it'd been thrown outside the PG_TRY block to begin with. Although this is clearly a *potential* source of bugs, it is not clear at the moment whether it is an *actual* source of bugs; there may not presently be any PG_TRY blocks in code that can be reached with no outer longjmp catcher. So for the moment I'm going to be conservative and not back-patch this. The change breaks ABI for users of PG_RE_THROW and hence might create compatibility problems for loadable modules, so we should not put it into released branches without proof that it's needed.
* Add wrapper script around install.pl that calls buildenv.bat before doingMagnus Hagander2007-05-01
| | | | | | the install. Dave Page
* Fix a thinko in my patch of a couple months ago for bug #3116: it did theTom Lane2007-05-01
| | | | | | | | | | wrong thing when inlining polymorphic SQL functions, because it was using the function's declared return type where it should have used the actual result type of the current call. In 8.1 and 8.2 this causes obvious failures even if you don't have assertions turned on; in 8.0 and 7.4 it would only be a problem if the inlined expression were used as an input to a function that did run-time type determination on its inputs. Add a regression test, since this is evidently an under-tested area.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-08 10:17:11 +0000