aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Add server side lo_import(filename, oid) function.Tatsuo Ishii2008-03-22
|
* Add URL for:Bruce Momjian2008-03-22
| | | | | | * Simplify ability to create partitioned tables > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00387.php
* Add URL for:Bruce Momjian2008-03-22
| | | | | | * Simplify ability to create partitioned tables > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00248.php
* Add TODO:Bruce Momjian2008-03-22
| | | | | | | > > * Improve performance of shared invalidation queue for multiple CPUs > > http://archives.postgresql.org/pgsql-performance/2008-01/msg00023.php
* Add URLs for:Bruce Momjian2008-03-22
| | | | | | | | | | | | * Simplify ability to create partitioned tables This would allow creation of partitioned tables without requiring creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints for rapid partition selection. Options could include range and hash partition selection. > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00028.php > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00413.php
* Remove TypeName struct's timezone flag, which has been write-only storageTom Lane2008-03-21
| | | | | for a very long time --- in current usage it's entirely redundant with the name field.
* Give an explicit error for serial[], rather than silently ignoringTom Lane2008-03-21
| | | | the array decoration as the code had been doing.
* Report the current queries of all backends involved in a deadlockTom Lane2008-03-21
| | | | | | | | | | | | | | | (if they'd be visible to the current user in pg_stat_activity). This might look like it's subject to race conditions, but it's actually pretty safe because at the time DeadLockReport() is constructing the report, we haven't yet aborted our transaction and so we can expect that everyone else involved in the deadlock is still blocked on some lock. (There are corner cases where that might not be true, such as a statement timeout triggering in another backend before we finish reporting; but at worst we'd report a misleading activity string, so it seems acceptable considering the usefulness of reporting the queries.) Original patch by Itagaki Takahiro, heavily modified by me.
* Add:Bruce Momjian2008-03-21
| | | | | | | | > > * Convert single quotes to apostrophes in the PDF documentation > > http://archives.postgresql.org/pgsql-docs/2007-12/msg00059.php >
* Add:Bruce Momjian2008-03-21
| | | | | | | > > * Fix inconsistent precedence of =, >, and < compared to <>, >=, and <= > > http://archives.postgresql.org/pgsql-bugs/2007-12/msg00145.php
* Add:Bruce Momjian2008-03-21
| | | | | | | | > > o Prevent SSL from sending network packets to avoid interference > with Win32 signal emulation > > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00455.php
* Corrected version number.Michael Meskes2008-03-21
|
* Document that soft-mounting NFS is not recommended.Bruce Momjian2008-03-21
|
* More README src cleanups.Bruce Momjian2008-03-21
|
* Adjust pgstatindex() to give correct answers for indexes larger thanTom Lane2008-03-21
| | | | | 2^31 blocks. Also fix pg_relpages() for the same case. Tatsuhito Kasahara
* Generate dummy probes.h for MSVC builds.Andrew Dunstan2008-03-21
|
* Get rid of a bunch of #ifdef HAVE_INT64_TIMESTAMP conditionals by inventingTom Lane2008-03-21
| | | | | | | | | | a new typedef TimeOffset to represent an intermediate time value. It's either int64 or double as appropriate, and in most usages will be measured in microseconds or seconds the same as Timestamp. We don't call it Timestamp, though, since the value doesn't necessarily represent an absolute time instant. Warren Turkal
* Arrange for an explicit cast applied to an ARRAY[] constructor to be appliedTom Lane2008-03-20
| | | | | | | | | | directly to all the member expressions, instead of the previous implementation where the ARRAY[] constructor would infer a common element type and then we'd coerce the finished array after the fact. This has a number of benefits, one being that we can allow an empty ARRAY[] construct so long as its element type is specified by such a cast. Brendan Jurd, minor fixes by me.
* Add a couple of missing FreeQueryDesc calls. Noticed while testing aAlvaro Herrera2008-03-20
| | | | framework to keep track of snapshots in use.
* Make source code READMEs more consistent. Add CVS tags to all README files.Bruce Momjian2008-03-20
|
* Dept of second thoughts: --no-tablespaces had better also preventTom Lane2008-03-20
| | | | pg_dumpall from attaching TABLESPACE options to CREATE DATABASE commands.
* Support a --no-tablespaces option in pg_dump/pg_dumpall/pg_restore, so thatTom Lane2008-03-20
| | | | | | | | dumps can be loaded into databases without the same tablespaces that the source had. The option acts by suppressing all "SET default_tablespace" commands, and also CREATE TABLESPACE commands in pg_dumpall's case. Gavin Roy, with documentation and minor fixes by me.
* Added ECPGget_PGconn() function to ecpglib, courtesy of Mike Aubury.Michael Meskes2008-03-20
| | | | Removed one include file from connect-test1.
* Changed statement escaping to not escape continuation line markers.Michael Meskes2008-03-20
|
* Add the missing cyrillic "Yo" characters ('e' and 'E' with two dots) to theHeikki Linnakangas2008-03-20
| | | | | | | | | | | | | | | ISO_8859-5 <-> MULE_INTERNAL conversion tables. This was discovered when trying to convert a string containing those characters from ISO_8859-5 to Windows-1251, because we use MULE_INTERNAL/KOI8R as an intermediate encoding between those two. While the missing "Yo" was just an omission in the conversion tables, there are a few other characters like the "Numero" sign ("No" as a single character) that exists in all the other cyrillic encodings (win1251, ISO_8859-5 and cp866), but not in KOI8R. Added comments about that. Patch by Sergey Burladyan. Back-patch to 7.4.
* Remove another useless snapshot creation.Alvaro Herrera2008-03-19
|
* Support ALTER TYPE RENAME. Petr JelinekTom Lane2008-03-19
|
* We no longer need a snapshot set after opening the finishing transaction: thisAlvaro Herrera2008-03-19
| | | | | is redundant because autovacuum now always analyzes a single table per transaction.
* Add -M (query mode) option per ITAGAKI TakahiroTatsuo Ishii2008-03-19
|
* Fix regexp substring matching (substring(string from pattern)) for the cornerTom Lane2008-03-19
| | | | | | | | | | | | case where there is a match to the pattern overall but the user has specified a parenthesized subexpression and that subexpression hasn't got a match. An example is substring('foo' from 'foo(bar)?'). This should return NULL, since (bar) isn't matched, but it was mistakenly returning the whole-pattern match instead (ie, 'foo'). Per bug #4044 from Rui Martins. This has been broken since the beginning; patch in all supported versions. The old behavior was sufficiently inconsistent that it's impossible to believe anyone is depending on it.
* Add libpq new API lo_import_with_oid() which is similar to lo_import()Tatsuo Ishii2008-03-19
| | | | except that lob's oid can be specified.
* Fix tps calculation when -C supplied. Per Yoshiyuki Asaba.Tatsuo Ishii2008-03-19
| | | | | Change Copyright owner from mine to PostgreSQL Global Development Group Fix minor message typo
* Spit items:Bruce Momjian2008-03-18
| | | | | | | | | | | | | | | * Experiment with multi-threaded backend better I/O utilization This would allow a single query to make use of multiple I/O channels simultaneously. One idea is to create a background reader that can pre-fetch sequential and index scan pages needed by other backends. This could be expanded to allow concurrent reads from multiple devices in a partitioned table. * Experiment with multi-threaded backend better CPU utilization This would allow several CPUs to be used for a single query, such as for sorting or query execution.
* Update TODO description:Bruce Momjian2008-03-18
| | | | | | | | * Speed WAL recovery by allowing more than one page to be prefetched This should be done utilizing the same infrastructure used for prefetching in general to avoid introducing complex error-prone code in WAL replay.
* Add find_typedef comments for Linux.Bruce Momjian2008-03-18
|
* Add find_typedef comment.Bruce Momjian2008-03-18
|
* Add Linux support to find_typedefs, with help from Alvaro.Bruce Momjian2008-03-18
|
* Arrange to "inline" SQL functions that appear in a query's FROM clause,Tom Lane2008-03-18
| | | | | | | are declared to return set, and consist of just a single SELECT. We can replace the FROM-item with a sub-SELECT and then optimize much as if we were dealing with a view. Patch from Richard Rowell, cleaned up by me.
* Add to TODO:Bruce Momjian2008-03-18
| | | | | | | | | | > > * Consider not storing a NULL bitmap on disk if all the NULLs are > trailing > > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00624.php > http://archives.postgresql.org/pgsql-patches/2007-12/msg00109.php >
* Don't need -Wno-error anymore, because flex is no longer producing warnings.Peter Eisentraut2008-03-18
|
* Catch all errors in for and while loops in makefiles. Don't ignore anyPeter Eisentraut2008-03-18
| | | | | | errors in any commands, including in various clean targets that have so far been handled inconsistently. make -i is available to ignore all errors in a consistent and official way.
* cvsweb lives on anoncvs.postgresql.org these days.Magnus Hagander2008-03-18
|
* Wiki page about cvs now lives in the main wiki, the oneMagnus Hagander2008-03-18
| | | | on developer.postgresql.org is going away.
* Add TODO URLs for:Bruce Momjian2008-03-18
| | | | | | | o Allow UPDATE tab SET ROW (col, ...) = (SELECT...) > http://archives.postgresql.org/pgsql-patches/2007-04/msg00315.php > http://archives.postgresql.org/pgsql-patches/2008-03/msg00237.php
* Move elog(DEBUG4) call outside the locked area, per suggestion from Tom Lane.Alvaro Herrera2008-03-18
|
* Add URLs for :Bruce Momjian2008-03-18
| | | | | | | | | | | * Speed WAL recovery by allowing more than one page to be prefetched This involves having a separate process that can be told which pages the recovery process will need in the near future. > http://archives.postgresql.org/pgsql-general/2007-12/msg00683.php > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00497.php <
* Advance multiple array keys rightmost-first instead of leftmost-firstTom Lane2008-03-18
| | | | | | during a bitmap index scan. This cannot affect the query results (since we're just dumping the TIDs into a bitmap) but it might offer some advantage in locality of access to the index. Per Greg Stark.
* Add TODO:Bruce Momjian2008-03-18
| | | | | | | > o Recreate pg_xlog/archive_status/ if it doesn't exist after > restoring from a PITR backup > > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00487.php
* Fix our printf implementation to follow spec: if a star parameterTom Lane2008-03-18
| | | | | | | | | | | value for a precision is negative, act as though precision weren't specified at all, that is the whole .* part of the format spec should be ignored. Our previous coding took it as .0 which is certainly wrong. Per report from Kris Jurka and local testing. Possibly this should be back-patched, but it would be good to get some more testing first; in any case there are no known cases where there's really a problem on the backend side.
* Add to TODO:Bruce Momjian2008-03-18
| | | | | | | | > > * Consider Cartesian joins when both relations are needed to form an > indexscan qualification for a third relation > > http://archives.postgresql.org/pgsql-performance/2007-12/msg00090.php
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-07 08:04:16 +0000