aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Create AVG() aggregates for int8 and NUMERIC which do not compute X^2,Bruce Momjian2007-02-17
| | | | | | as a performance enhancement. Mark Kirkwood
* Teach find_nonnullable_rels to handle OR cases: if every arm of an ORTom Lane2007-02-16
| | | | | | forces a particular relation nonnullable, then we can say that the OR does. This is worth a little extra trouble since it may allow reduction of outer joins to plain joins.
* Fix new RI operator selection code to do the right thing when working withTom Lane2007-02-16
| | | | | | | an opclass for a generic type such as ANYARRAY. The original coding failed to check that PK and FK columns were of the same array type. Per discussion with Tom Dunstan. Also, make the code a shade more readable by not trying to economize on variables.
* Reduce the amount of memory "clobbered" for every process title change,Bruce Momjian2007-02-16
| | | | | on platforms that need this. This is done by only writing past the previously stored message, if it was longer.
* Adjust the definition of is_pushed_down so that it's always true for INNERTom Lane2007-02-16
| | | | | | | | | JOIN quals, just like WHERE quals, even if they reference every one of the join's relations. Now that we can reorder outer and inner joins, it's possible for such a qual to end up being assigned to an outer join plan node, and we mustn't have it treated as a join qual rather than a filter qual for the node. (If it were, the join could produce null-extended rows that it shouldn't.) Per bug report from Pelle Johansson.
* Better fix for determining minimum and maximum int64 values that doesn'tPeter Eisentraut2007-02-16
| | | | require stdint.h and works for "busted" int64.
* Install a more correct fix in the timestamp and timestamptz regression tests:Alvaro Herrera2007-02-16
| | | | | remove duplicated tests in timestamp, and complete timestamptz with the tests that were missing to more closely mirror timestamp.
* Code review for SSLKEY patch.Tom Lane2007-02-16
|
* Fix the timestamptz test problem, by moving the tests that use theAlvaro Herrera2007-02-16
| | | | | timestamp_tbl table into the timestamp test. Also, restore a test that used to exist as a valid test in the timestamptz test.
* Fix // commentPeter Eisentraut2007-02-16
|
* Add stdint.h includePeter Eisentraut2007-02-16
|
* Functions for mapping table data and table schemas to XML (a.k.a. XML export)Peter Eisentraut2007-02-16
|
* Fix another problem in 8.2 changes that allowed "one-time" qual conditions toTom Lane2007-02-16
| | | | | | | be checked at plan levels below the top; namely, we have to allow for Result nodes inserted just above a nestloop inner indexscan. Should think about using the general Param mechanism to pass down outer-relation variables, but for the moment we need a back-patchable solution. Per report from Phil Frost.
* Add two new format fields for use with to_char(), to_date() andBruce Momjian2007-02-16
| | | | | | | | | | | | | | to_timestamp(): - ID for day-of-week - IDDD for day-of-year This makes it possible to convert ISO week dates to and from text fully represented in either week ('IYYY-IW-ID') or day-of-year ('IYYY-IDDD') format. I have also added an 'isoyear' field for use with extract / date_part. Brendan Jurd
* SSL improvements:Bruce Momjian2007-02-16
| | | | | | | | o read global SSL configuration file o add GUC "ssl_ciphers" to control allowed ciphers o add libpq environment variable PGSSLKEY to control SSL hardware keys Victor B. Wagner
* Remove useless database name from bootstrap argument processing (includingAlvaro Herrera2007-02-16
| | | | startup and bgwriter processes), and the -y flag. It's not used anywhere.
* Restructure code that is responsible for ensuring that clauseless joins areTom Lane2007-02-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | considered when it is necessary to do so because of a join-order restriction (that is, an outer-join or IN-subselect construct). The former coding was a bit ad-hoc and inconsistent, and it missed some cases, as exposed by Mario Weilguni's recent bug report. His specific problem was that an IN could be turned into a "clauseless" join due to constant-propagation removing the IN's joinclause, and if the IN's subselect involved more than one relation and there was more than one such IN linking to the same upper relation, then the only valid join orders involve "bushy" plans but we would fail to consider the specific paths needed to get there. (See the example case added to the join regression test.) On examining the code I wonder if there weren't some other problem cases too; in particular it seems that GEQO was defending against a different set of corner cases than the main planner was. There was also an efficiency problem, in that when we did realize we needed a clauseless join because of an IN, we'd consider clauseless joins against every other relation whether this was sensible or not. It seems a better design is to use the outer-join and in-clause lists as a backup heuristic, just as the rule of joining only where there are joinclauses is a heuristic: we'll join two relations if they have a usable joinclause *or* this might be necessary to satisfy an outer-join or IN-clause join order restriction. I refactored the code to have just one place considering this instead of three, and made sure that it covered all the cases that any of them had been considering. Backpatch as far as 8.1 (which has only the IN-clause form of the disease). By rights 8.0 and 7.4 should have the bug too, but they accidentally fail to fail, because the joininfo structure used in those releases preserves some memory of there having once been a joinclause between the inner and outer sides of an IN, and so it leads the code in the right direction anyway. I'll be conservative and not touch them.
* Restructure autovacuum in two processes: a dummy process, which runsAlvaro Herrera2007-02-15
| | | | | | | | | continuously, and requests vacuum runs of "autovacuum workers" to postmaster. The workers do the actual vacuum work. This allows for future improvements, like allowing multiple autovacuum jobs running in parallel. For now, the code keeps the original behavior of having a single autovac process at any time by sleeping until the previous worker has finished.
* Add ORDER BY to a query on information_schema.views, to avoid possibleTom Lane2007-02-15
| | | | platform-specific result ordering. Per buildfarm results.
* Repair oversight in 8.2 change that improved the handling of "pseudoconstant"Tom Lane2007-02-15
| | | | | | | | | WHERE clauses. createplan.c is now willing to stick a gating Result node almost anywhere in the plan tree, and in particular one can wind up directly underneath a MergeJoin node. This means it had better be willing to handle Mark/Restore. Fortunately, that's trivial in such cases, since we can just pass off the call to the input node (which the planner has previously ensured can handle Mark/Restore). Per report from Phil Frost.
* Make it possible to build with integer datetimes in msvc, and enable by default.Magnus Hagander2007-02-14
|
* Fix to_date()/to_timestamp() 'D' field for day of week, was off by one.Bruce Momjian2007-02-14
| | | | | | Converting from char using 'D' doesn't make lots of sense, of course. Report from Brendan Jurd.
* Move fsync method macro defines into /include/access/xlogdefs.h so theyBruce Momjian2007-02-14
| | | | can be used by src/tools/fsync/test_fsync.c.
* Fix capitalization and punctuation of two more GUC description strings.Neil Conway2007-02-14
|
* Fix up foreign-key mechanism so that there is a sound semantic basis for theTom Lane2007-02-14
| | | | | | | | | | | | | | | | | | | | | equality checks it applies, instead of a random dependence on whatever operators might be named "=". The equality operators will now be selected from the opfamily of the unique index that the FK constraint depends on to enforce uniqueness of the referenced columns; therefore they are certain to be consistent with that index's notion of equality. Among other things this should fix the problem noted awhile back that pg_dump may fail for foreign-key constraints on user-defined types when the required operators aren't in the search path. This also means that the former warning condition about "foreign key constraint will require costly sequential scans" is gone: if the comparison condition isn't indexable then we'll reject the constraint entirely. All per past discussions. Along the way, make the RI triggers look into pg_constraint for their information, instead of using pg_trigger.tgargs; and get rid of the always error-prone fixed-size string buffers in ri_triggers.c in favor of building up the RI queries in StringInfo buffers. initdb forced due to columns added to pg_constraint and pg_trigger.
* Disallow committing a prepared transaction unless we are in the same databaseTom Lane2007-02-13
| | | | | it was executed in. Someday it might be nice to allow cross-DB commits, but work would be needed in NOTIFY and perhaps other places. Per Heikki.
* Improve postmaster's behavior if an accept() call fails. Because the serverTom Lane2007-02-13
| | | | | | | socket is still read-ready, the code was a tight loop, wasting lots of CPU. We can't do anything to clear the failure, other than wait, but we should give other processes more chance to finish and release FDs; so insert a small sleep. Also, avoid bogus "close(-1)" in this case. Per report from Jim Nasby.
* Add code so database scans are done in an order consistent withBruce Momjian2007-02-13
| | | | pg_dumpall.
* Add ORDER BY to vacummdb so databases are scaned in the same order asBruce Momjian2007-02-13
| | | | pg_dumpall.
* Un-break build on ANSI compilers (like msvc) by moving Assert to positionMagnus Hagander2007-02-13
| | | | after variable declarations.
* Add script to run regression tests under vc++ without mingw. UpdateMagnus Hagander2007-02-13
| | | | clean script to properly clean up the result of it.
* One more fix for makefile := to : change.Magnus Hagander2007-02-13
|
* Properly parse Makefile after change from := to =.Magnus Hagander2007-02-13
|
* Repair bug in 8.2's new logic for planning outer joins: we have to allow joinsTom Lane2007-02-13
| | | | | | | | that overlap an outer join's min_righthand but aren't fully contained in it, to support joining within the RHS after having performed an outer join that can commute with this one. Aside from the direct fix in make_join_rel(), fix has_join_restriction() and GEQO's desirable_join() to consider this possibility. Per report from Ian Harding.
* Add comment to explain why O_EXCL and O_TRUNC can be ignored inBruce Momjian2007-02-13
| | | | openFlagsToCreateFileFlags() in certain cases.
* Add comment that to_char() for broken glibc pt_BR might cause a problem.Bruce Momjian2007-02-13
|
* Avoid infinite recursion when dumping new planner EquivalenceClass trees.Tom Lane2007-02-12
|
* Add support for optionally escaping periods when converting SQL identifiersPeter Eisentraut2007-02-11
| | | | to XML names, which will be required for supporting XML export.
* Fix another erroneous =-for-:= substitution.Tom Lane2007-02-11
|
* Fixed multibyte handling as reported by <harada.toshi@oss.ntt.co.jp>.Michael Meskes2007-02-11
|
* Fix for early log messages during postmaster startup getting lost whenMagnus Hagander2007-02-11
| | | | | | running as a service on Win32. Per report from Harald Armin Massa.
* Fix pg_standby to build on msvc.Magnus Hagander2007-02-10
|
* Add proper mapping of boolean type data to XML Schema.Peter Eisentraut2007-02-10
|
* StrNCpy -> strlcpy (not complete)Peter Eisentraut2007-02-10
|
* Put back some not-so-unnecessary-as-all-that := usages. Per buildfarm.Tom Lane2007-02-10
|
* Hm, seems my hack on rowtypes regression test has made its output rowTom Lane2007-02-10
| | | | | order platform-specific. Add an ORDER BY clause to stop buildfarm failures.
* Minor tweak to make rowtypes regression test run faster. We don'tTom Lane2007-02-09
| | | | | | currently have any better strategy for this query than re-running the sub-select over and over; it seems unlikely that doing so 10000 times is a more useful test than doing it a few dozen times.
* Call pgstat_drop_database during DROP DATABASE, so that any stats fileTom Lane2007-02-09
| | | | | | | | entries for the victim database go away sooner rather than later. We already did the equivalent thing at the per-relation level, not sure why it's not been done for whole databases. With this change, pgstat_vacuum_tabstat should usually not find anything to do; though we still need it as a backstop in case DROPDB or TABPURGE messages get lost under load.
* Replace useless uses of := by = in makefiles.Peter Eisentraut2007-02-09
|
* Remove blank lines in code.Bruce Momjian2007-02-09
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-15 14:11:29 +0000