aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Remove outdated join_1.out regression test comparison file. This hasTom Lane2009-02-26
| | | | | | been broken for more than a month, so evidently it's not needed, at least not for any configuration in the buildfarm. We can correct it and replace it later if we find something that still needs it.
* Final removal of -q options, which haven't done anything since 8.3 andPeter Eisentraut2009-02-26
| | | | were marked for removal in 8.4.
* Add a -w/--no-password option that prevents all password prompts to allPeter Eisentraut2009-02-26
| | | | | | programs that have a -W/--password option. In passing, remove the ancient PSQL_ALWAYS_GET_PASSWORDS compile option.
* Fix an old problem in decompilation of CASE constructs: the ruleutils.c codeTom Lane2009-02-25
| | | | | | | | | | | looks for a CaseTestExpr to figure out what the parser did, but it failed to consider the possibility that an implicit coercion might be inserted above the CaseTestExpr. This could result in an Assert failure in some cases (but correct results if Asserts weren't enabled), or an "unexpected CASE WHEN clause" error in other cases. Per report from Alan Li. Back-patch to 8.1; problem doesn't exist before that because CASE was implemented differently.
* Remove references to foreign data wrapper libraries, since they haveMagnus Hagander2009-02-25
| | | | been removed. This should unbreak the msvc build again.
* Use the same style in the help synopsis that other programs are using.Peter Eisentraut2009-02-25
|
* Clean up help (-?) output.Peter Eisentraut2009-02-25
|
* Remove feof(stdin) calls related to when to prompt for a password,Peter Eisentraut2009-02-25
| | | | leftovers from when the password was read from stdin.
* Sort the output of --help mostly alphabetical, make it align better, makePeter Eisentraut2009-02-25
| | | | help of pg_dump and pg_dumpall more similar.
* Put back a "continue" that went missing in the changes to start backgroundHeikki Linnakangas2009-02-25
| | | | writer in WAL recovery.
* Get rid of the rather fuzzily defined FlattenedSubLink node type in favor ofTom Lane2009-02-25
| | | | | | | | | making pull_up_sublinks() construct a full-blown JoinExpr tree representation of IN/EXISTS SubLinks that it is able to convert to semi or anti joins. This makes pull_up_sublinks() a shade more complex, but the gain in semantic clarity is worth it. I still have more to do in this area to address the previously-discussed problems, but this commit in itself fixes at least one bug in HEAD, as shown by added regression test case.
* Don't append epoch to log_filename if no format specifier is given.Peter Eisentraut2009-02-24
| | | | Robert Haas
* Add the possibility to specify an explicit validator function for foreign-dataPeter Eisentraut2009-02-24
| | | | | | wrappers (similar to procedural languages). This way we don't need to retain the nearly empty libraries, and we are more free in how to implement the wrapper API in the future.
* Repair a longstanding bug in CLUSTER and the rewriting variants of ALTERTom Lane2009-02-24
| | | | | | | | | | | | | | | | | | TABLE: if the command is executed by someone other than the table owner (eg, a superuser) and the table has a toast table, the toast table's pg_type row ends up with the wrong typowner, ie, the command issuer not the table owner. This is quite harmless for most purposes, since no interesting permissions checks consult the pg_type row. However, it could lead to unexpected failures if one later tries to drop the role that issued the command (in 8.1 or 8.2), or strange warnings from pg_dump afterwards (in 8.3 and up, which will allow the DROP ROLE because we don't create a "redundant" owner dependency for table rowtypes). Problem identified by Cott Lang. Back-patch to 8.1. The problem is actually far older --- the CLUSTER variant can be demonstrated in 7.0 --- but it's mostly cosmetic before 8.1 because we didn't track ownership dependencies before 8.1. Also, fixing it before 8.1 would require changing the call signature of heap_create_with_catalog(), which seems to carry a nontrivial risk of breaking add-on modules.
* Fix psql's \dD to show only one row per domain, even when the domain hasTom Lane2009-02-23
| | | | multiple check constraints.
* Add quotes to messagePeter Eisentraut2009-02-23
|
* Change the signaling of end-of-recovery. Startup process now indicates endHeikki Linnakangas2009-02-23
| | | | | of recovery by exiting with exit code 0, like in previous releases. Per Tom's suggestion.
* Add note that inlined SQL functions aren't tracked by track_functions.Tom Lane2009-02-22
|
* another small message tweakPeter Eisentraut2009-02-20
|
* Reconnect to the right database when using parallel restore with -C. Fixes ↵Andrew Dunstan2009-02-20
| | | | bug reported by Olivier Prenant
* Simplify overcomplicated (and overly restrictive) test to see whether anTom Lane2009-02-20
| | | | | | | | | | | | | | IS NULL condition is rendered redundant by detection of an antijoin. If we know that a join is an antijoin, then *any* Var coming out of its righthand side must be NULL, not only the joining column(s). Also, it's still gonna be null after being passed up through higher joins, whether they're outer joins or not. I was misled by a faulty analogy to reduce_outer_joins() in the original coding. But consider select * from a left join b on a.x = b.y where b.y is null and b.z is null; The first IS NULL condition justifies deciding that the join is an antijoin (if the = is strict) and then the second one is just plain redundant.
* Improve comments about semijoin implementation strategy, per a questionTom Lane2009-02-19
| | | | from Robert Haas.
* Fix bogus comment, from the patch to start bgwriter during archiveHeikki Linnakangas2009-02-19
| | | | recovery.
* Wordsmithing for PL/Perl messagesPeter Eisentraut2009-02-19
|
* Add an implicit rule %.c -> %.i for running the C preprocessor.Peter Eisentraut2009-02-19
| | | | | I occasionally use this for debugging, and it seems wasteful to have to reinvent this all the time.
* Remove croak and Perl_croak from gettext triggers. While we couldPeter Eisentraut2009-02-19
| | | | | | | | | | | | | selectively mark up their arguments for translation, the Perl xsubpp tool generates a bunch of additional Perl_croak calls that we cannot control, so we'd be creating a confusing mix of translated and untranslated messages of a similar kind. This is something that might deserve a more comprehensive solution later. Also remove _ from gettext triggers, because it wasn't used. Use SPI.c instead of SPI.xs as source file for xgettext, because the .xs format isn't really supported in xgettext.
* Increase NUM_AUXILIARY_PROCS, now that the startup process can co-existHeikki Linnakangas2009-02-19
| | | | | with other auxiliary processes for a short period. As witnessed by buildfarm member dungbeetle.
* Remove the special cases to prevent minus-zero results in float4 and float8Tom Lane2009-02-18
| | | | | | | | | | | | | | unary minus operators. We weren't attempting to prevent minus zero anywhere else; in view of our gradual trend to make the float datatypes more IEEE standard compliant, we should allow minus zero here rather than disallow it elsewhere. We don't, however, expect that all platforms will produce minus zero, so we need to adjust the one affected regression test to allow both results. Per discussion of bug #4660. (In passing, clean up a couple other minor infelicities in float.c.)
* Start background writer during archive recovery. Background writer now performsHeikki Linnakangas2009-02-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | its usual buffer cleaning duties during archive recovery, and it's responsible for performing restartpoints. This requires some changes in postmaster. When the startup process has done all the initialization and is ready to start WAL redo, it signals the postmaster to launch the background writer. The postmaster is signaled again when the point in recovery is reached where we know that the database is in consistent state. Postmaster isn't interested in that at the moment, but that's the point where we could let other backends in to perform read-only queries. The postmaster is signaled third time when the recovery has ended, so that postmaster knows that it's safe to start accepting connections. The startup process now traps SIGTERM, and performs a "clean" shutdown. If you do a fast shutdown during recovery, a shutdown restartpoint is performed, like a shutdown checkpoint, and postmaster kills the processes cleanly. You still have to continue the recovery at next startup, though. Currently, the background writer is only launched during archive recovery. We could launch it during crash recovery as well, but it seems better to keep that codepath as simple as possible, for the sake of robustness. And it couldn't do any restartpoints during crash recovery anyway, so it wouldn't be that useful. log_restartpoints is gone. Use log_checkpoints instead. This is yet to be documented. This whole operation is a pre-requisite for Hot Standby, but has some value of its own whether the hot standby patch makes 8.4 or not. Simon Riggs, with lots of modifications by me.
* Add --freeze option to vacuumdb.Bruce Momjian2009-02-18
|
* Have pg_dump/pg_dumpall --binary-upgrade restore frozenids for relationsBruce Momjian2009-02-18
| | | | and databases.
* Message wordsmithingPeter Eisentraut2009-02-18
|
* Add missing newline.Bruce Momjian2009-02-17
|
* Add pg_dump --binary-upgrade flag to be used by binary upgradeBruce Momjian2009-02-17
| | | | | | | utilities. The new code allows transfer of dropped column information to the upgraded server.
* Add _() calls for the argument of plpgsql_yyerror() so it actually getsPeter Eisentraut2009-02-17
| | | | translated somehow.
* Add plpgsql_yyerror to gettext triggersPeter Eisentraut2009-02-17
|
* Mark 3rd argument of validate_tupdesc_compat() for translation, instead ofPeter Eisentraut2009-02-17
| | | | marking up each instance separately.
* Redefine _() to dgettext() instead of gettext() so that it uses the plpgsqlPeter Eisentraut2009-02-17
| | | | text domain, instead of the postgres one (or whatever the default may be).
* Remove gettext trigger write_stderr(), which isn't used by PLs.Peter Eisentraut2009-02-17
|
* Wrap some long queries.Bruce Momjian2009-02-16
|
* Uppercase keywords in pg_dump.cBruce Momjian2009-02-16
|
* Teach the planner to treat a partial unique index as proving a variable isTom Lane2009-02-15
| | | | | | | unique for a particular query, if the index predicate is satisfied. This requires a bit of reordering of operations so that we check the predicates before doing any selectivity estimates, but shouldn't really cause any noticeable slowdown. Per a comment from Michal Politowski.
* Minor wordsmithing.Tom Lane2009-02-15
|
* Loop calling CallNamedPipe() several times in case it fails,Magnus Hagander2009-02-15
| | | | | | | since it can be transient failures, causing kill() to not properly send signals. Original patch from Steve Marshall, modified by me.
* A couple of marginal performance hacks for the information_schema views:Tom Lane2009-02-14
| | | | | | | | | replace the old recursive-SQL-function implementation of _pg_keysequal() with use of the built-in array containment operators, and change table_constraints' UNION to UNION ALL. Per discussion with Octavio Alvarez. initdb not forced since this doesn't affect results, but you'd need to initdb or reload the information_schema to see the new definitions.
* Fix UNLISTEN to fall out quickly if the current backend has never executedTom Lane2009-02-13
| | | | | | | | | | | | any LISTEN command. This is more important than it used to be because DISCARD ALL invokes UNLISTEN. Connection-pooled applications making heavy use of DISCARD ALL were seeing significant contention for pg_listener, as reported by Matteo Beccati. It seems unlikely that clients using LISTEN would use pooled connections, so this simple tweak seems sufficient, especially since the pg_listener implementation is slated to go away soon anyway. Back-patch to 8.3, where DISCARD ALL was introduced.
* do not use unsetenv.c on mingwAndrew Dunstan2009-02-12
|
* The Czech (cs_CZ) and Slovak (sk_SK) locales sort numbers after letters,Peter Eisentraut2009-02-12
| | | | | | instead of vice versa. Update the regression test expectations to support that. In the plpgsql test, adjust the test data so that this isn't an issue. In the char and varchar tests, add new expected files.
* Unset language-related locale settings in any case, otherwise psql willPeter Eisentraut2009-02-12
| | | | speak in tongues and mess up the regression test diffs.
* Remove tabs from SGML.Bruce Momjian2009-02-12
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 21:14:11 +0000