| Age | Commit message (Collapse) | Author |
|---|
|
value. This means that hash index lookups are always lossy and have to be
rechecked when the heap is visited; however, the gain in index compactness
outweighs this when the indexed values are wide. Also, we only need to
perform datatype comparisons when the hash codes match exactly, rather than
for every entry in the hash bucket; so it could also win for datatypes that
have expensive comparison functions. A small additional win is gained by
keeping hash index pages sorted by hash code and using binary search to reduce
the number of index tuples we have to look at.
Xiao Meng
This commit also incorporates Zdenek Kotala's patch to isolate hash metapages
and hash bitmaps a bit better from the page header datastructures.
|
|
|
|
each connection. This makes it possible to catch errors in the pg_hba
file when it's being reloaded, instead of silently reloading a broken
file and failing only when a user tries to connect.
This patch also makes the "sameuser" argument to ident authentication
optional.
|
|
|
|
|
|
per David Wheeler.
|
|
|
|
seconds
instead of by number of transactions to run. Takahiro Itagaki
|
|
erroneous input, rather than silently producing bizarre results as formerly
happened.
Brendan Jurd
|
|
and the literal syntax INTERVAL 'string' ... SECOND(n), as required by the
SQL standard. Our old syntax put (n) directly after INTERVAL, which was
a mistake, but will still be accepted for backward compatibility as well
as symmetry with the TIMESTAMP cases.
Change intervaltypmodout to show it in the spec's way, too. (This could
potentially affect clients, if there are any that analyze the typmod of an
INTERVAL in any detail.)
Also fix interval input to handle 'min:sec.frac' properly; I had overlooked
this case in my previous patch.
Document the use of the interval fields qualifier, which up to now we had
never mentioned in the docs. (I think the omission was intentional because
it didn't work per spec; but it does now, or at least close enough to be
credible.)
|
|
initdb forced due to changes in the pg_settings view.
Magnus Hagander and Alvaro Herrera.
|
|
always owner-only. The TRUNCATE privilege works identically to the DELETE
privilege so far as interactions with the rest of the system go.
Robert Haas
|
|
|
|
This isn't exhaustive but it covers some of the more common layout
mistakes I've seen in submitted patches.
|
|
Simon Riggs
|
|
for editing if no function name is specified. This seems a much cleaner way
to offer that functionality than the original patch had. In passing,
de-clutter the error displays that are given for a bogus function-name
argument, and standardize on "$function$" as the default delimiter for the
function body. (The original coding would use the shortest possible
dollar-quote delimiter, which seems to create unnecessarily high risk of
later conflicts with the user-modified function body.)
|
|
In support of that, create a backend function pg_get_functiondef().
The psql command is functional but maybe a bit rough around the edges...
Abhijit Menon-Sen
|
|
chapter.
Author: Michelle Caisse <Michelle.Caisse@Sun.COM>
|
|
David Gould
|
|
change build system to use only Bison. Simplify build rules, make file names
uniform. Don't build the token table header file where it is not needed.
|
|
Pointed out by Daniel Migowski.
|
|
changed.
|
|
the window during which backends have no statistics file to read.
|
|
|
|
"outage" of the statistics views.
This requires making the stats collector respond to SIGHUP, like the other
utility processes already did.
|
|
|
|
Simon Riggs
|
|
backpatch to 8.3.X. Also fix markup that had just one bullet.
|
|
|
|
|
|
|
|
< o -Allow an existing index to be marked as a table's primary key
> o Allow an existing index to be marked as a table's primary key
|
|
debug_print_plan to appear at LOG message level, not DEBUG1 as historically.
Make debug_pretty_print default to on. Also, cause plans generated via
EXPLAIN to be subject to debug_print_plan. This is all to make
debug_print_plan a reasonably comfortable substitute for the former behavior
of EXPLAIN VERBOSE.
|
|
! o Allow an existing index to be marked as a table's primary key
|
|
While at it, mark a couple of items completed in 8.4:
! o -Prevent long-lived temporary tables from causing frozen-xid
advancement starvation
! * -Improve performance of shared invalidation queue for multiple CPUs
Also remove a couple of obsolete assignments.
|
|
>
> * Fix all set-returning system functions so they support a wildcard
> target list
>
> SELECT * FROM pg_get_keywords() works but SELECT * FROM
> pg_show_all_settings() does not.
|
|
|
|
* Improve ability to modify views via ALTER TABLE
<
> http://archives.postgresql.org/pgsql-hackers/2008-08/msg00300.php
|
|
>
> * Prevent query cancel packets from being replayed by an attacker,
> especially when using SSL
>
> http://archives.postgresql.org/pgsql-hackers/2008-08/msg00345.php
>
|
|
corochoone@gmail.com
|
|
<LI><A href=
"http://sqlzoo.net">http://sqlzoo.net</A>
</LI>
|
|
variable stats_temp_directory, instead of requiring the admin to
mount/symlink the pg_stat_tmp directory manually.
For now the config variable is PGC_POSTMASTER. Room for further improvment
that would allow it to be changed on-the-fly.
|
|
the old JOIN_IN code, but antijoins are new functionality.) Teach the planner
to convert appropriate EXISTS and NOT EXISTS subqueries into semi and anti
joins respectively. Also, LEFT JOINs with suitable upper-level IS NULL
filters are recognized as being anti joins. Unify the InClauseInfo and
OuterJoinInfo infrastructure into "SpecialJoinInfo". With that change,
it becomes possible to associate a SpecialJoinInfo with every join attempt,
which permits some cleanup of join selectivity estimation. That needs to be
taken much further than this patch does, but the next step is to change the
API for oprjoin selectivity functions, which seems like material for a
separate patch. So for the moment the output size estimates for semi and
especially anti joins are quite bogus.
|
|
pointed out.
|
|
* Improve ability to modify views via ALTER TABLE
> http://archives.postgresql.org/pgsql-hackers/2008-07/msg01410.php
|
|
Allow XML to accept more liberal DOCTYPE specifications
Everything works correctly, per today's email to -general.
|
|
> * Add 'hostgss' pg_hba.conf option to allow GSS link-level encryption
>
> http://archives.postgresql.org/pgsql-hackers/2008-07/msg01454.php
|
|
This allows the use of a ramdrive (either through mount or symlink) for
the temporary file that's written every half second, which should
reduce I/O.
On server shutdown/startup, the file is written to the old location in
the global directory, to preserve data across restarts.
Bump catversion since the $PGDATA directory layout changed.
|
|
* Consider decreasing the I/O caused by updating tuple hint bits
> http://archives.postgresql.org/pgsql-patches/2008-07/msg00199.php
|
|
or domains). This was already effectively required because you had to own
the I/O functions, and the I/O functions pretty much have to be written in
C since we don't let PL functions take or return cstring. But given the
possible security consequences of a malicious type definition, it seems
prudent to enforce superuser requirement directly. Per recent discussion.
|
