- 13 12月, 2007 5 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
per Oleg.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
psql's \d commands and other uses of printQuery(). Previously we would pass these strings through gettext() and then send them to the server as literals in the SQL query. But the code was not set up to handle doubling of quotes in the strings, causing failure if a translation attempted to use the wrong kind of quote marks, as indeed is now the case for (at least) the French translation of \dFp. Another hazard was that gettext() would translate to whatever encoding was implied by the client's LC_CTYPE setting, which might be different from the client_encoding setting, which would probably cause the server to reject the query as mis-encoded. The new arrangement is to send the untranslated ASCII strings to the server, and do the translations inside printQuery() after the query results come back. Per report from Guillaume Lelarge and subsequent discussion.
-
由 Tom Lane 提交于
faulty code in third arm of #if. Per buildfarm reports.
-
- 12 12月, 2007 9 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
< < * Allow free-behind capability for large sequential scans to avoid < kernel cache spoiling < < Posix_fadvise() can control both sequential/random file caching and < free-behind behavior, but it is unclear how the setting affects other < backends that also have the file open, and the feature is not supported < on all operating systems.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
usual 'merge join'.
-
由 Alvaro Herrera 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
useful and confuses people who think it is the same as -U. (Eventually we might want to re-introduce it as being an alias for -U, but that should not happen until the switch has actually not been there for a few releases.) Likewise in pg_dump and pg_restore. Per gripe from Robert Treat and subsequent discussion.
-
由 Magnus Hagander 提交于
better, per JD.
-
- 11 12月, 2007 8 次提交
-
-
由 Alvaro Herrera 提交于
with the logged event. CSV logs are now a first-class citizen along plain text logs in that they carry much of the same information. Per complaint from depesz on bug #3799.
-
由 Magnus Hagander 提交于
used when building addons. Dave Page
-
由 Tom Lane 提交于
hazards. Instead teach these programs to prompt for a password when necessary, just like all our other programs. I did not bother to invent -W switches for them, since the return on investment seems so low.
-
由 Tom Lane 提交于
switch optional, as is the case for every other one of our programs. I had already documented its -W as being optional, so this is bringing the code into line with the docs ...
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
psql work.
-
由 Bruce Momjian 提交于
-
- 10 12月, 2007 10 次提交
-
-
由 Bruce Momjian 提交于
Greg Smith
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
Fix lots of bad markup, bad English, bad explanations. Second round of commits. pgcrypto and pgstandby still to go...
-
由 Alvaro Herrera 提交于
wording.
-
由 Bruce Momjian 提交于
Euler Taveira de Oliveira
-
由 Bruce Momjian 提交于
Euler Taveira de Oliveira
-
由 Tom Lane 提交于
too long since freshman English :-()
-
由 Tom Lane 提交于
under copyright in the US and many other places. Substitute a little something from a poet who's more safely dead. Per gripe from Bjorn Munch.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
PQconnectionNeedsPassword function that tells the right thing for whether to prompt for a password, and improve PQconnectionUsedPassword so that it checks whether the password used by the connection was actually supplied as a connection argument, instead of coming from environment or a password file. Per bug report from Mark Cave-Ayland and subsequent discussion.
-
- 09 12月, 2007 3 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
the two join variables at both ends: not only trailing rows that need not be scanned because there cannot be a match on the other side, but initial rows that will be scanned without possibly having a match. This allows a more realistic estimate of startup cost to be made, per recent pgsql-performance discussion. In passing, fix a couple of bugs that had crept into mergejoinscansel: it was not quite up to speed for the task of estimating descending-order scans, which is a new requirement in 8.3.
-
由 Bruce Momjian 提交于
the sections below in more detail.
-
- 08 12月, 2007 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< o -Allow commenting of variables in postgresql.conf to restore them < to defaults < o -Add a GUC variable to control the tablespace for temporary objects < and sort files < Monitoring < ========== < < * -Allow server log information to be output as CSV format < * -Add ability to monitor the use of temporary sort files < * -Allow user-defined types to accept 'typmod' parameters < < http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php < http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php < http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php < < * -Add Globally/Universally Unique Identifier (GUID/UUID) < < http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php < http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php < < * -Support a data type with specific enumerated values (ENUM) < o -Add support for arrays of complex types < o -Make 64-bit version of the MONEY data type < * -Add ISO day of week format 'ID' to to_char() where Monday = 1 < * -Add a field 'isoyear' to extract(), based on the ISO week < * -Add RESET SESSION command to reset all session state < o -Make CLUSTER preserve recently-dead tuples per MVCC requirements < o -Add more logical syntax CLUSTER table USING index; < support current syntax for backward compatibility < o -Allow UPDATE/DELETE WHERE CURRENT OF cursor < o -Add support for MOVE cursors < o -Allow PL/PythonU to return boolean rather than 1/0 < o -Allow psql \pset boolean variables to set to fixed values, rather < than toggle < o -Add -f to pg_dumpall < Dependency Checking < =================== < < * -Flush cached query plans when the dependent objects change or < when new ANALYZE statistics are available < * -Track dependencies in function bodies and recompile/invalidate < * -Invalidate prepared queries, like INSERT, when the table definition < is altered < < * -Allow use of indexes to search for NULLs < * -Allow the creation of indexes with mixed ascending/descending < specifiers < * -Reduce checkpoint performance degredation by forcing data to disk < more evenly < * -Allow sequential scans to take advantage of other concurrent < sequential scans, also called "Synchronised Scanning" < * -Consider shrinking expired tuples to just their headers < * -Allow heap reuse of UPDATEd rows if no indexed columns are changed, < and old and new versions are on the same heap page < * -Reduce XID consumption of read-only queries < o -Turn on by default < o -Allow multiple vacuums so large tables do not starve small < tables < * -Allow the pg_xlog directory location to be specified during initdb < with a symlink back to the /data location < * -Allow buffered WAL writes and fsync < * -Allow ORDER BY ... LIMIT # to select high/low value without sort or < index using a sequential scan for highest/lowest values < * -Merge xmin/xmax/cmin/cmax back into three header fields < o -Support a smaller header for short variable-length fields < * -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h < * -Fix problem with excessive logging during SSL disconnection < < http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php < http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php < < o -Add long file support for binary pg_dump output
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
checkpoints.
-
由 Tom Lane 提交于
The original coding leaked memory (at least 8K per crosstab_hash call) because it allowed the hash table to be allocated as a child of TopMemoryContext and then never freed it. Fix that by putting the hash table under per_query_ctx, instead. Also get rid of use of a static variable to point to the hash table. Aside from being ugly, that would actively do the wrong thing in the case of re-entrant calls to crosstab_hash, which are at least theoretically possible since it was expecting the static variable to stay valid across a SPI_execute call.
-