aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Install .mo files for NLS as <program>-<version>.mo when building with MSVCMagnus Hagander2009-01-21
| | | | | | as well. Same change as made earlier for autoconf builds. Per Hiroshi Inoue.
* Add a new option to RestoreBkpBlocks() to indicate if a cleanup lock shouldHeikki Linnakangas2009-01-20
| | | | | | | | | be used instead of the normal exclusive lock, and make WAL redo functions responsible for calling RestoreBkpBlocks(). They know better what kind of a lock they need. At the moment, this just moves things around with no functional change, but makes the hot standby patch that's under review cleaner.
* Do not msgmerge against /dev/null; merge against the pot file itselfPeter Eisentraut2009-01-20
| | | | instead.
* Revise the permission checking on user mapping DDL commands.Peter Eisentraut2009-01-20
| | | | | | | | | | | | | | | CREATE/ALTER/DROP USER MAPPING are now allowed either by the server owner or by a user with USAGE privileges for his own user name. This is more or less what the SQL standard wants anyway (plus "implementation-defined") Hide information_schema.user_mapping_options.option_value, unless the current user is the one associated with the user mapping, or is the server owner and the mapping is for PUBLIC, or is a superuser. This is to protect passwords. Also, fix a bug in information_schema._pg_foreign_servers, which hid servers using wrappers where the current user did not have privileges on the wrapper. The correct behavior is to hide servers where the current user has no privileges on the server.
* Make psql \d and \dt consistent for system tables, i.e prevent \d fromBruce Momjian2009-01-20
| | | | | | showing system tables, make \dS pattern show system table details, and have \dtS show system and _user_ tables, to be consistent with other \d* commands.
* Document RELKIND_SPECIAL reference in psql, from <= 8.1.X.Bruce Momjian2009-01-19
|
* Fix accidental (I suppose) introduction of non-ASCII quote marks.Tom Lane2009-01-19
|
* Use the new text domain names ("postgres-8.4" instead of "postgres")Magnus Hagander2009-01-19
| | | | Hiroshi Inoue
* Avoid regression test cases that fail in locales that sort "v" and "w"Peter Eisentraut2009-01-19
| | | | | | | equally (in glibc: et_EE, sv_SE, tk_TM). It turns out that this was already taken care of previously by select_1.out, which I had forgotten to update for an unrelated change. But might as well avoid the issue altogether.
* Alter regression test cases that rely on the sort order of "aa". SomePeter Eisentraut2009-01-19
| | | | locales (da_DK, fo_FO, kl_GL, nb_NO, nn_NO in glibc) sort "aa" after "z".
* Alter the regression test cases that rely on the sort order of "ch" betweenPeter Eisentraut2009-01-19
| | | | | "cg" and "ci". This eliminates a test failure on the following glibc locales: br_FR, cs_CZ, cy_GB, es_EC, es_US, hsb_DE, ig_NG, ik_CA, sk_SK.
* Message wordsmithingPeter Eisentraut2009-01-19
|
* Fix a pg_dump output ordering problem introduced in 8.3 by the addition ofTom Lane2009-01-18
| | | | | | | | | | | | | | | | | array types for composite types. Although pg_dump understood it wasn't supposed to dump these array types as separate objects, it must include them in the dependency ordering analysis, and it was improperly assigning them the same relatively-high sort priority as regular types. This resulted in effectively moving composite types and tables up to that same high priority, which broke any ordering requirements that weren't explicitly enforced by dependencies. In particular user-defined operator classes, which should come out before tables, failed to do so. Per report from Brendan Jurd. In passing, also fix an ill-considered decision to give text search objects the same sort priority as functions and operators --- the sort result looks a lot nicer if different object types are kept separate. The recent foreign-data patch had copied that decision, making the sort ordering even messier :-(
* Manual attempt to update this file.Peter Eisentraut2009-01-16
|
* plpython_error.out is for Python 2.4, plpython_error_3.out is for Python 2.5,Peter Eisentraut2009-01-16
| | | | as it was previously.
* Add vacuum_freeze_table_age GUC option, to control when VACUUM shouldHeikki Linnakangas2009-01-16
| | | | | ignore the visibility map and scan the whole table, to advance relfrozenxid.
* WordsmithingPeter Eisentraut2009-01-16
|
* Remove period from primary error message.Peter Eisentraut2009-01-15
|
* Fix URL generation in headline. Only tag lexeme will be replaced by space.Teodor Sigaev2009-01-15
| | | | Per http://archives.postgresql.org/pgsql-bugs/2008-12/msg00013.php
* Fix generation too long headline with ShortWords.Teodor Sigaev2009-01-15
| | | | Per http://archives.postgresql.org/pgsql-hackers/2008-09/msg01088.php
* Cleanup pass over PL/Python NLS. Add translation support to PLy_elog andPeter Eisentraut2009-01-15
| | | | PLy_exception_set, and clarify some error messages.
* Remove unneeded GETTEXT_TRIGGERS.Peter Eisentraut2009-01-15
|
* NLS cleanup in ecpglibPeter Eisentraut2009-01-15
| | | | | | | | | | | | | | | | | Replace leftover instances of _() by ecpg_gettext(), the latter being the correct way to refer to the library's message catalog, instead of the one of the program using the library. Drop NLS support for ecpg_log(), which is a debugging instrument similar to elog() in the backend. We cannot support NLS in the ecpg compatlib, because that requires ecpg_gettext, which is in ecpglib, which is not a dependency of compatlib. It doesn't seem worthwhile to worry about this, since the only translatable string is "out of memory", and gettext probably won't be able to do much without memory either. Adjust messages to project style.
* Build needed things in src/test/regress/ first. And some build rulesPeter Eisentraut2009-01-15
| | | | normalization.
* Make .pot files depend on the makefiles, so that they are updated when thePeter Eisentraut2009-01-15
| | | | file or trigger function lists are changed.
* Make 'find' syntax consistent; add .git exclusion to make_ctags.Bruce Momjian2009-01-14
|
* Avoid version-control system directories when creating TAGS. BesidesPeter Eisentraut2009-01-14
| | | | | being wasteful, this can collide with repostory metadata on case-insensitive file sytems.
* Remove empty #ifdef block.Bruce Momjian2009-01-14
|
* Make the columns is_insertable_into and is_updatable behave uniformlyPeter Eisentraut2009-01-14
| | | | | correctly. They are supposed to examine which kinds of rules are present, which they did in some of the info schema views but not in others.
* Make error messages match backend style.Peter Eisentraut2009-01-14
|
* misc.o depends on pg_config_paths.h when --enable-nls is used.Peter Eisentraut2009-01-14
|
* Remove broken Assertions that failed if a statement executed in PL/pgSQL isHeikki Linnakangas2009-01-14
| | | | | | | | | | rewritten into another kind of statement, for example if an INSERT is rewritten into an UPDATE. Back-patch to 8.3 and 8.2. For HEAD, Tom suggested inventing a new SPI_OK_REWRITTEN return code, but that's not a backportable solution. I'll do that as a separate patch, this patch will do as a stopgap measure for HEAD too in the meanwhile.
* Remove useless (and insecure) temp file handling.Peter Eisentraut2009-01-13
|
* Throw an error when using -C and -1 at the same time in pg_restore.Magnus Hagander2009-01-13
| | | | | | | It's not possible to do CREATE DATABASE inside a transaction, so previously we just got a server error instead. Backpatch to 8.2, which is where the -1 feature appeared.
* Remove special-handling of usernames with Kerberos authentication. We willMagnus Hagander2009-01-13
| | | | | | | | | now always use the system username as the default, and not try to pick it up from the kerberos ticket. This fixes the spurious error messages that show up on kerberos-enabled builds when not actually using kerberos, and puts it in line with how other authentication methods work.
* Simplify the writing of amoptions routines by introducing a convenienceAlvaro Herrera2009-01-12
| | | | | | | | | | | | fillRelOptions routine that stores the parsed values in the struct using a table-based approach. Per Tom suggestion. Also remove the "continue" in HANDLE_*_RELOPTION macros, which were useless and in spirit they were assuming too much of how the macros were going to be used. (Note that these macros are now unused, but the intention is to introduce some usage in a future autovacuum patch, which is why they weren't completely removed.) Also, do not call the string validation routine when not validating. It seems less error-prone this way, per commentary on the amoptions SGML docs.
* Tweak order of operations in BitmapHeapNext() to avoid the case of prefetchingTom Lane2009-01-12
| | | | | the same page we are nanoseconds away from reading for real. There should be something left to do on the current page before we consider issuing a prefetch.
* Use qualified_name instead of relation_expr for commands that have noPeter Eisentraut2009-01-12
| | | | | | | | business with inheritance recursion: ALTER INDEX, ALTER SEQUENCE, ALTER TRIGGER, ALTER VIEW. They would just silently ignore the ONLY. ALTER TABLE has mixed behavior and cannot be dealt with this way because of the resulting shift/reduce conflicts.
* Add ONLY support to LOCK and TRUNCATE. By default, these commands are nowPeter Eisentraut2009-01-12
| | | | | | recursive. => Note this incompatibility in the release notes.
* Implement prefetching via posix_fadvise() for bitmap index scans. A newTom Lane2009-01-12
| | | | | | | | | | GUC variable effective_io_concurrency controls how many concurrent block prefetch requests will be issued. (The best way to handle this for plain index scans is still under debate, so that part is not applied yet --- tgl) Greg Stark
* Re-enable the old code in xlog.c that tried to use posix_fadvise(), so thatTom Lane2009-01-11
| | | | | | | we can get some buildfarm feedback about whether that function is still problematic. (Note that the planned async-preread patch will not really prove anything one way or the other in buildfarm testing, since it will be inactive with default GUC settings.)
* Make tests pass with or without locale.Peter Eisentraut2009-01-11
|
* Revise the TIDBitmap API to support multiple concurrent iterations over aTom Lane2009-01-10
| | | | | | bitmap. This is extracted from Greg Stark's posix_fadvise patch; it seems worth committing separately, since it's potentially useful independently of posix_fadvise.
* Fix libpq so that it reports PGRES_EMPTY_QUERY not PGRES_COMMAND_OK when anTom Lane2009-01-09
| | | | | | | | | | | | empty query string is passed to PQexecParams and related functions. Its handling of the NoData response to Describe messages was subtly incorrect. Per my report of yesterday. Although I consider this a bug, it's a behavioral change that might affect applications, so not back-patched. In passing fix a second issue in the same code: it didn't react well to an out-of-memory failure while trying to make the PGresult object.
* Arrange for function default arguments to be processed properly in expressionsTom Lane2009-01-09
| | | | | | | that are set up for execution with ExecPrepareExpr rather than going through the full planner process. By introducing an explicit notion of "expression planning", this patch also lays a bit of groundwork for maybe someday allowing sub-selects in standalone expressions.
* Remove fairly useless mixed-case identifier test that causes localePeter Eisentraut2009-01-09
| | | | dependencies.
* Code review of strftime patch, per comments from Tom:Magnus Hagander2009-01-09
| | | | | * Use correct buffer size MAX_L10N_DATA * Use strlcpy instead of StrNCpy
* Fix strftime usage on Win32 when trying to fetch the locale-awareMagnus Hagander2009-01-09
| | | | | | | parts of a time string so it properly handles different encodings. Original patch by Hiroshi Saito, heavily reworked by me and ITAGAKI Takahiro.
* More portable use of "find".Peter Eisentraut2009-01-09
|
* Rewrite update-po target, so that it works less like a shell script and morePeter Eisentraut2009-01-09
| | | | | | | | | | | like a makefile with real dependencies. Instead of overwriting the old po file, write the new one to .po.new. This is less annoying and integrates better with the NLS web site. Also, we can now merge languages that don't have a po file yet, by merging against all other po files of that language, to pick up recurring translations automatically. This previously only worked when a po file already existed.