| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
Jun Kuwamura
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
extra newline
|
|
|
|
|
|
|
|
|
|
|
|
| |
"make all", and then reference them there during the actual tests. This
makes the handling of these files more parallel to that of regress.so,
and in particular simplifies use of the regression tests outside the
original build tree. The PGDG and Red Hat RPMs have been doing this via
patches for a very long time. Inclusion of the change in core was requested
by Jørgen Austvik of Sun, and I can't see any reason not to.
I attempted to fix the MSVC scripts for this too, but they may need
further tweaking ...
|
|
|
|
|
|
|
|
| |
* Add deferred trigger queue file
< This item involves dumping large queues into files.
> This item involves dumping large queues into files, or doing some
> kind of join to process all the triggers, or some bulk operation.
|
|
|
|
|
|
| |
* Add deferred trigger queue file
> http://archives.postgresql.org/pgsql-hackers/2008-05/msg00876.php
|
|
|
|
|
|
| |
require SELECT privilege as well, since you normally need to read existing
column values within such commands. This behavior is according to spec,
but we'd never documented it before. Per gripe from Volkan Yazici.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the associated datatype as their equality member. This means that these
opclasses can now support plain equality comparisons along with LIKE tests,
thus avoiding the need for an extra index in some applications. This
optimization was not possible when the pattern opclasses were first introduced,
because we didn't insist that text equality meant bitwise equality; but we
do now, so there is no semantic difference between regular and pattern
equality operators.
I removed the name_pattern_ops opclass altogether, since it's really useless:
name's regular comparisons are just strcmp() and are unlikely to become
something different. Instead teach indxpath.c that btree name_ops can be
used for LIKE whether or not the locale is C. This might lead to a useful
speedup in LIKE queries on the system catalogs in non-C locales.
The ~=~ and ~<>~ operators are gone altogether. (It would have been nice to
keep them for backward compatibility's sake, but since the pg_amop structure
doesn't allow multiple equality operators per opclass, there's no way.)
A not-immediately-obvious incompatibility is that the sort order within
bpchar_pattern_ops indexes changes --- it had been identical to plain
strcmp, but is now trailing-blank-insensitive. This will impact
in-place upgrades, if those ever happen.
Per discussions a couple months ago.
|
|
|
|
|
| |
< o Use LC_TIME for localized weekday/month names, rather than
> o -Use LC_TIME for localized weekday/month names, rather than
|
|
|
|
| |
Euler Taveira de Oliveira
|
|
|
|
|
|
| |
IDENTITY to be more explicit about the possible hazards. Per gripe from Neil
and subsequent discussion. Eventually we may be able to get rid of this
warning, but for now it had better be there.
|
|
|
|
|
| |
sequence. This seems an obvious extension to the recent patch, and it
makes the code noticeably cleaner and more orthogonal.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sequence to be reset to its original starting value. This requires adding the
original start value to the set of parameters (columns) of a sequence object,
which is a user-visible change with potential compatibility implications;
it also forces initdb.
Also add hopefully-SQL-compatible RESTART/CONTINUE IDENTITY options to
TRUNCATE TABLE. RESTART IDENTITY executes ALTER SEQUENCE RESTART for all
sequences "owned by" any of the truncated relations. CONTINUE IDENTITY is
a no-op option.
Zoltan Boszormenyi
|
|
|
|
|
|
|
|
|
|
| |
Add a few "help" entries.
Move \g help entry into "General".
Update psql version mismatch warning text.
Joshua D. Drake
|
|
|
|
| |
> o -Have \l+ show database size, if permissions allow
|
|
|
|
|
| |
detection for wrapped lines or lines with newlines that need pager to
display.
|
|
|
|
|
|
| |
prefix matching using this facility.
Teodor Sigaev and Oleg Bartunov
|
|
|
|
|
|
| |
PL/pgSQL
> o -Add CASE capability to language (already in SQL)
|
|
|
|
| |
Pavel Stehule
|
|
|
|
|
|
|
|
|
|
| |
functions.
Note that because this patch changes FmgrInfo, any external C functions
you might be testing with 8.4 will need to be recompiled.
Patch by Martin Pihlak, some editorialization by me (principally, removing
tracking of getrusage() numbers)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
HINT fields to a user-thrown error message, and to specify the SQLSTATE
error code to use. The syntax has also been tweaked so that the
Oracle-compatible case "RAISE exception_name" works (though you won't get a
very nice error message if you just write that much). Lastly, support
the Oracle-compatible syntax "RAISE" with no parameters to re-throw
the current error from within an EXCEPTION block.
In passing, allow the syntax SQLSTATE 'nnnnn' within EXCEPTION lists,
so that there is a way to trap errors with custom SQLSTATE codes.
Pavel Stehule and Tom Lane
|
|
|
|
| |
> * -Improve dead row detection during multi-statement transactions usage
|
| |
|
|
|
|
|
|
| |
o Allow an existing index to be marked as a table's primary key
>
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg00500.php
|
|
|
|
| |
> o Allow an existing index to be marked as a table's primary key
|
|
|
|
|
|
|
|
| |
* Add column to pg_stat_activity that shows the progress of long-running
commands like CREATE INDEX and VACUUM
>
> http://archives.postgresql.org/pgsql-patches/2008-04/msg00203.php
>
|
|
|
|
|
|
| |
> o Clear table counters on TRUNCATE
>
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg00169.php
|
|
|
|
|
| |
> o -Prevent parent tables from altering or dropping constraints
> o -Prevent child tables from altering or dropping constraints
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
as those for inherited columns; that is, it's no longer allowed for a child
table to not have a check constraint matching one that exists on a parent.
This satisfies the principle of least surprise (rows selected from the parent
will always appear to meet its check constraints) and eliminates some
longstanding bogosity in pg_dump, which formerly had to guess about whether
check constraints were really inherited or not.
The implementation involves adding conislocal and coninhcount columns to
pg_constraint (paralleling attislocal and attinhcount in pg_attribute)
and refactoring various ALTER TABLE actions to be more like those for
columns.
Alex Hunsaker, Nikhil Sontakke, Tom Lane
|
|
|
|
|
|
|
| |
>
> * Improve the /contrib installation experience
>
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg00132.php
|
|
|
|
|
|
| |
file/pipe output too if \pset columns' is set.
Bryce Nesbitt
|
|
|
|
| |
auto-configure properly for libxslt present or not.
|
|
|
|
|
|
|
|
|
| |
< * Improve detection of shared memory segments being used by other
< FreeBSD jails
> * Improve detection of shared memory segments being used by others
> by checking the SysV shared memory field 'nattch'
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg00673.php
|
|
|
|
|
|
| |
>
> o Add CREATE SCHEMA ... LIKE that copies a schema
>
|
|
|
|
|
|
| |
> * Add database and transaction-level triggers
>
> http://archives.postgresql.org/pgsql-hackers/2008-03/msg00451.php
|
| |
|
| |
|
|
|
|
| |
Scott Marlowe
|
|
|
|
|
|
|
| |
instead of calling a bunch of individual functions.
This function can also be called directly, taking a PID as an argument, to
return only the data for a single PID.
|
| |
|
|
|
|
|
| |
< * Consider increasing the number of default statistics target, and
< reduce statistics target overhead
|
|
|
|
|
|
| |
< o Allow dictionary to filter out only stop words
> o Allow dictionaries to change the token that is passed on to
> later dictionaries
|
|
|
|
|
|
|
|
| |
o Consider changing error to warning for strings larger than one
megabyte
http://archives.postgresql.org/pgsql-bugs/2008-02/msg00190.php
http://archives.postgresql.org/pgsql-patches/2008-03/msg00062.php
|