aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Clarify documentation references to pg_stat_get_blocks_fetched andBruce Momjian2009-04-09
| | | | pg_stat_get_blocks_hit, per suggestion from Robert Haas.
* No more need to update FAQs.Bruce Momjian2009-04-09
|
* Add URL for config.guess/sub updatesPeter Eisentraut2009-04-09
|
* Update config.guess and config.subPeter Eisentraut2009-04-09
|
* Update time zone data files to tzdata release 2009e: DST law changes inTom Lane2009-04-09
| | | | | Argentina/San_Luis, Cuba, Jordan (historical correction only), Morocco, Palestine, Syria, Tunisia.
* Translation updates for 8.4 betaPeter Eisentraut2009-04-09
|
* Update GIN limitations documentation to match current reality.Tom Lane2009-04-09
|
* Remove SQL-compatibility function cardinality(). It is not exactly clearTom Lane2009-04-09
| | | | | | | how this ought to behave for multi-dimensional arrays. Per discussion, not having it at all seems better than having it with what might prove to be the wrong behavior. We can always add it later when we have consensus on the correct behavior.
* Improve documentation about how checkpoint spreads I/O activity.Bruce Momjian2009-04-09
|
* Treat EOF like \n for line-counting purposes in ParseConfigFile,Tom Lane2009-04-09
| | | | per bug #4752. Fujii Masao
* Fix the plpgsql memory leak exhibited in bug #4677. That leak was introducedTom Lane2009-04-09
| | | | | | | | | | | | | | | | | | | | | | by my patch of 2007-01-28 to use per-subtransaction ExprContexts/EStates: since we re-prepared any expression tree when the current subtransaction ID changed, we'd accumulate more and more leaked expression state trees in the outermost subtransaction if the same function was executed at multiple levels of subtransaction nesting. To fix, go back to the previous scheme where there was only one EState per transaction for simple plpgsql expressions. We really only need an ExprContext per subtransaction, not a whole EState, so it's possible to keep prepared expression state trees in the one EState throughout the transaction. This should be more efficient as well as not leaking memory for cases involving lots of subtransactions. The added regression test is the case that inspired the 2007-01-28 patch in the first place, just to make sure we didn't go backwards. The current memory leak complaint is unfortunately hard to test for in the regression test framework, though manual testing shows it's fixed. Although this is a pre-existing bug, I'm not back-patching because I'd like to see this method get some field testing first. Consider back-patching if it gets through 8.4beta unscathed.
* Remove psql's ancient hack that suppressed functions taking or returningTom Lane2009-04-08
| | | | | | | | cstring from the output of \df. Now that the default behavior is to exclude all system functions, the de-cluttering rationale for this behavior seems pretty weak; and it was always quite confusing/unhelpful if you were actually looking for I/O functions. (Not to mention if you were looking for encoding converters or other cases that might take or return cstring.)
* Allow leading and trailing spaces around NaN in numeric_in.Tom Lane2009-04-08
| | | | Sam Mason, rewritten a bit by Tom.
* XMLATTRIBUTES() should send the attribute values throughPeter Eisentraut2009-04-08
| | | | | map_sql_value_to_xml_value() instead of directly through the data type output function. This is per SQL standard, and consistent with XMLELEMENT().
* Quote string literals correctly in the new CREATE SERVER statementsHeikki Linnakangas2009-04-08
| | | | and binary upgrade UPDATE statements.
* Oops, mustn't call textdomain() when compiling without --enable-nlsHeikki Linnakangas2009-04-08
|
* Tell gettext which codeset to use by calling bind_textdomain_codeset(). WeHeikki Linnakangas2009-04-08
| | | | | | | | | already did that on Windows, but it's needed on other platforms too when LC_CTYPE=C. With other locales, we enforce (or trust) that the codeset of the locale matches the server encoding so we don't need to bind it explicitly. It should do no harm in that case either, but I don't have full faith in the PG encoding -> OS codeset mapping table yet. Per recent discussion on pgsql-hackers.
* Improve tab completion for \ef.Bruce Momjian2009-04-08
| | | | Andrew Gierth
* Revert addition of units to GUC descriptions; doesn't affectBruce Momjian2009-04-07
| | | | postgresql.conf.
* Disable effective_io_concurrency on Solaris because posix_fadvise() isBruce Momjian2009-04-07
| | | | no-op on that platform.
* More GUC units doc updates.Bruce Momjian2009-04-07
| | | | Euler Taveira de Oliveira
* Add attribution for:Bruce Momjian2009-04-07
| | | | Add Japanese message translations (Japan PostgreSQL Users Group)
* Add release note item:Bruce Momjian2009-04-07
| | | | Add Japanese message translations
* Remove FAQ and FAQ_DEV ASCII and HTML files from CVS; now on the wiki.Bruce Momjian2009-04-07
| | | | Per-language files kept for transator usage.
* Support Perl 5.10 and TCL 8.5 in MSVC builds.Magnus Hagander2009-04-07
| | | | | | | | We should probably have a better way to do this (meaning something not hardcoded) eventually, but this fixes the problem for 8.4. Dave Page
* Remove useless (leftover?) extern declaration.Tom Lane2009-04-07
|
* Defend against non-ASCII letters in fuzzystrmatch code. The functionsTom Lane2009-04-07
| | | | | still don't behave very sanely for multibyte encodings, but at least they won't be indexing off the ends of static arrays.
* Add doc link to section about how to compile triggers.Bruce Momjian2009-04-07
|
* Add an optional parameter to pg_start_backup() that specifies whether to doTom Lane2009-04-07
| | | | | | the checkpoint in immediate or lazy mode. This is to address complaints that pg_start_backup() takes a long time even when there's no need to minimize its I/O consumption.
* Add unit documentation for various postgresql.conf settings.Bruce Momjian2009-04-06
|
* Add entry in the encoding number to OS name table for KOI8-U.Peter Eisentraut2009-04-06
|
* Properly align equals signs in new postgresql.conf units comments.Bruce Momjian2009-04-06
|
* Document in postgresql.conf that the default units forBruce Momjian2009-04-06
| | | | log_min_duration_statement is milliseconds.
* Display postgresql.conf unit options in an easier-to-understand,Bruce Momjian2009-04-06
| | | | 2-column format.
* Doc change in new patch, stand-alone -> standaloneBruce Momjian2009-04-06
|
* Add documentation mention of 'check_postgres.pl' in Routine DatabaseBruce Momjian2009-04-06
| | | | Maintenance Tasks section.
* Adjust psql tab completion for new \d 'S' flag behavior; adjust code toBruce Momjian2009-04-06
| | | | be more flexible about additional modifiers for \d commands.
* Document the fact that fuzzystrmatch doesn't work in multibyte encodings.Tom Lane2009-04-06
|
* Correct keywords table for status of COLLATE vsTom Lane2009-04-06
| | | | LC_COLLATE.
* Fix 'all at one page bug' in picksplit method of R-tree emulation. Add defenseTeodor Sigaev2009-04-06
| | | | from buggy user-defined picksplit to GiST.
* Rename the new CREATE DATABASE options to set collation and ctype intoHeikki Linnakangas2009-04-06
| | | | LC_COLLATE and LC_CTYPE, per discussion on pgsql-hackers.
* Change cardinality() into a C-code function, instead of a SQL-languageTom Lane2009-04-05
| | | | | | | alias for array_length(v,1). The efficiency gain here is doubtless negligible --- what I'm interested in is making sure that if we have second thoughts about the definition, we will not have to force a post-beta initdb to change the implementation.
* Make ExecInitExpr build the list of SubPlans found in a plan tree in orderTom Lane2009-04-05
| | | | | | | | of discovery, rather than reverse order. This doesn't matter functionally (I suppose the previous coding dates from the time when lcons was markedly cheaper than lappend). However now that EXPLAIN is labeling subplans with IDs that are based on order of creation, this may help produce a slightly less surprising printout.
* Change EXPLAIN output so that subplans and initplans (particularly CTEs)Tom Lane2009-04-05
| | | | | | | | | | | are individually labeled, rather than just grouped under an "InitPlan" or "SubPlan" heading. This in turn makes it possible for decompilation of a subplan reference to usefully identify which subplan it's referencing. I also made InitPlans identify which parameter symbol(s) they compute, so that references to those parameters elsewhere in the plan tree can be connected to the initplan that will be executed. Per a gripe from Robert Haas about EXPLAIN output of a WITH query being inadequate, plus some longstanding pet peeves of my own.
* Fix infinite loop while checking of partial match in pending list.Teodor Sigaev2009-04-05
| | | | | Improve comments. Now GIN-indexable operators should be strict. Per Tom's questions/suggestions.
* Remove a boatload of useless definitions of 'int optreset'. If weTom Lane2009-04-05
| | | | | | are using our own ports of getopt or getopt_long, those will define the variable for themselves; and if not, we don't need these, because we never touch the variable anyway.
* I had always wondered why pg_config.h.win32 claimed that WindowsTom Lane2009-04-05
| | | | | | provides optreset. Current mastodon results prove that in fact it does not; it was only because getopt.c defined the variable anyway that things failed to fall over.
* Remove contrib/intarray's definitions of the <@ and @> operators, so that theyTom Lane2009-04-05
| | | | | | | | | | | | don't cause confusion with the built-in anyarray versions of those operators. Adjust the module's index opclasses to support the built-in operators in place of the private ones. The private implementations are still available under their historical names @ and ~, so no functionality is lost. Some quick testing suggests that they offer no real benefit over the core operators, however. Per a complaint from Rusty Conover.
* Hmm, baiji thinks we need explicit 'extern' here.Tom Lane2009-04-04
|
* Make an attempt at fixing our current Solaris 11 breakage: add a configureTom Lane2009-04-04
| | | | | probe for opterr (exactly like the one for optreset) and have getopt.c define the variables only if configure doesn't find them in libc.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 14:54:02 +0000