| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Update TODO accordingly.
|
|
<
<
< Reporting
< =========
<
< * Show location of syntax error in query [yacc]
|
|
.< * Improve speed with indexes (perhaps recreate index instead) [vacuum]
> * Improve speed with indexes (perhaps recreate index instead)
369c369
< lock and truncate table [vacuum]
> lock and truncate table
371c371
< rather than in /contrib [vacuum]
> rather than in /contrib
|
|
< * Allow better handling of numeric constants, type conversion [typeconv]
|
|
< * Add replication of distributed databases [replication]
> * Add replication of distributed databases
|
|
< o http://gborg.postgresql.org/project/pgreplication/projdisplay.php
|
|
< * Allow persistent backends [persistent]
> * Allow persistent backends [pool]
397c397
< connection pooling
> connection pooling [pool]
|
|
< float4, numeric/decimal too [optimizer]
> float4, numeric/decimal too
422c422
< * Missing optimizer selectivities for date, r-tree, etc. [optimizer]
> * Missing optimizer selectivities for date, r-tree, etc
|
|
< * Delay fsync() when other backends are about to commit too [fsync]
> * Delay fsync() when other backends are about to commit too
|
|
< * Add MATCH PARTIAL referential integrity [foreign]
> * Add MATCH PARTIAL referential integrity
|
|
|
|
> * Allow cross-db queries with transaction sematics
|
|
< * Allow queries across multiple databases [crossdb]
|
|
On Mon, 2004-01-26 at 21:28, Peter Eisentraut wrote:
> Christophe Combelles wrote:
> > At the bottom of this doc file :
> > file:///usr/share/doc/postgresql-doc/html/tutorial-createdb.html
> > "and it also happens that that user always has permission"
> > ---- x2
> The first "that" serves as a conjuction, the second one serves as an
> article. Looks correct to me.
A better workaround for the sentence would be something like:
"and it also happens that the user always has permission"
Looks easier to read, I think.
Enver ALTIN (a.k.a. skyblue)
|
|
<
> * Allow substring/replace() to get/set bit values
|
|
for already empty buffers because their buffer tag was not cleard out
when the buffers have been invalidated before.
Also removed the misnamed BM_FREE bufhdr flag and replaced the checks,
which effectively ask if the buffer is unpinned, with checks against the
refcount field.
Jan
|
|
< o Allow Java server-side programming, http://pljava.sourceforge.net
< [java]
> o Allow Java server-side programming [java]
|
|
TABLE. Per recent discussion.
|
|
the view pg_stat_activity is missing, as per Bruces suggestion.
Jan
|
|
wit: Add a header record to each WAL segment file so that it can be reliably
identified. Avoid splitting WAL records across segment files (this is not
strictly necessary, but makes it simpler to incorporate the header records).
Make WAL entries for file creation, deletion, and truncation (as foreseen but
never implemented by Vadim). Also, add support for making XLOG_SEG_SIZE
configurable at compile time, similarly to BLCKSZ. Fix a couple bugs I
introduced in WAL replay during recent smgr API changes. initdb is forced
due to changes in pg_control contents.
|
|
allow the bgwriter to start before the startup subprocess has finished
... it tends to crash otherwise. (The same problem may have existed for
the checkpointer, I'm not entirely sure.) Remove some code that was
redundant because the bgwriter is handled as a member of the backend list.
|
|
> o Disallow dropping of an inherited constraint
|
|
variable.
Remove thread locking for non-thread-safe functions, instead throw a
compile error.
Platforms will have to re-run tools/thread to record their thread
safety.
|
|
Without this patch, no thread locking or *_r functions were being used.
|
|
< * Make blind writes go through the file descriptor cache
|
|
|
|
|
|
snprintf format for uint64 items.
|
|
|
|
|
|
|
|
|
|
subroutine in src/port/pgsleep.c. Remove platform dependencies from
miscadmin.h and put them in port.h where they belong. Extend recent
vacuum cost-based-delay patch to apply to VACUUM FULL, ANALYZE, and
non-btree index vacuuming.
By the way, where is the documentation for the cost-based-delay patch?
|
|
the relcache, and so the notion of 'blind write' is gone. This should
improve efficiency in bgwriter and background checkpoint processes.
Internal restructuring in md.c to remove the not-very-useful array of
MdfdVec objects --- might as well just use pointers.
Also remove the long-dead 'persistent main memory' storage manager (mm.c),
since it seems quite unlikely to ever get resurrected.
|
|
Natoli and Bruce Momjian (and some cosmetic fixes from Neil Conway).
Changes:
- remove duplicate signal definitions from pqsignal.h
- replace pqkill() with kill() and redefine kill() in Win32
- use ereport() in place of fprintf() in some error handling in
pqsignal.c
- export pg_queue_signal() and make use of it where necessary
- add a console control handler for Ctrl-C and similar handling
on Win32
- do WaitForSingleObjectEx() in CHECK_FOR_INTERRUPTS() on Win32;
query cancelling should now work on Win32
- various other fixes and cleanups
|
|
|
|
|
|
< * Point-in-time data recovery using backup and write-ahead log
< * Create native Win32 port, http://momjian.postgresql.org/main/writings/pgsql/win32.html
> * Point-in-time data recovery using backup and write-ahead log,
> http://momjian.postgresql.org/main/writings/pgsql/project/pitr.html
> * Create native Win32 port, http://momjian.postgresql.org/main/writings/pgsql/project/win32.html
|
|
|
|
Jan
|
|
|
|
Jan
|
|
is asked to assign a variable to itself, it will result in doing a
memcpy() on an entirely-overlapping memory range, which results in
undefined behavior according to ANSI C. That said, it is unlikely to
actually do anything bad on any sane libc, but this keeps valgrind quiet.
|
|
|
|
Make btree index creation and initial validation of foreign-key constraints
use maintenance_work_mem rather than work_mem as their memory limit.
Add some code to guc.c to allow these variables to be referenced by their
old names in SHOW and SET commands, for backwards compatibility.
|
|
> * Make pg_restore continue after errors, so it acts more like pg_dump scripts
|
|
a series of numbers, optionally using an explicit step size other
than the default value (one). Use function in the information_schema
to replace hard-wired knowledge of INDEX_MAX_KEYS. initdb forced due
to pg_proc change. Documentation update still needed -- will be
committed separately.
|
|
|
