- 05 4月, 2008 3 次提交
-
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
At the same time remove dblink/dblink_current_query() as it is no longer necessary *BACKWARD COMPATIBILITY ISSUE* for dblink Tomas Doran
-
- 04 4月, 2008 8 次提交
-
-
由 Magnus Hagander 提交于
a make clean...
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
xmloption GUC variables into enums..
-
由 Tom Lane 提交于
specify the cost values to use, instead of always using 1's. Volkan Yazici In passing, remove fuzzystrmatch.h, which contained a bunch of stuff that had no business being in a .h file; fold it into its only user, fuzzystrmatch.c.
-
由 Bruce Momjian 提交于
< * Allow encoding on a per-column basis optionally using the ICU library > http://wiki.postgresql.org/wiki/Todo:Collate > http://wiki.postgresql.org/wiki/Todo:ICU
-
由 Tom Lane 提交于
heap_fetch a little.
-
由 Bruce Momjian 提交于
> * Improve how ANALYZE computes in-doubt tuples > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00771.php >
-
由 Tom Lane 提交于
classed all as "dead"; also get it to count DEAD item pointers as dead rows, instead of ignoring them as before. Also improve matters so that tuples previously inserted or deleted by our own transaction are handled nicely: the stats collector's live-tuple and dead-tuple counts will end up correct after our transaction ends, regardless of whether we end in commit or abort. While there's more work that could be done to improve the counting of in-doubt tuples in both VACUUM and ANALYZE, this commit is enough to alleviate some known bad behaviors in 8.3; and the other stuff that's been discussed seems like research projects anyway. Pavan Deolasee and Tom Lane
-
- 03 4月, 2008 5 次提交
-
-
由 Magnus Hagander 提交于
Per buildfarm member mastodon.
-
由 Peter Eisentraut 提交于
-
由 Magnus Hagander 提交于
-
由 Bruce Momjian 提交于
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-patches/2008-01/msg00105.php > http://archives.postgresql.org/pgsql-patches/2008-03/msg00327.php
-
由 Tom Lane 提交于
responsible for copying the query string into the new Portal. Such copying is unnecessary in the common code path through exec_simple_query, and in this case it can be enormously expensive because the string might contain a large number of individual commands; we were copying the entire, long string for each command, resulting in O(N^2) behavior for N commands. (This is the cause of bug #4079.) A second problem with it is that PortalDefineQuery really can't risk error, because if it elog's before having set up the Portal, we will leak the plancache refcount that the caller is trying to hand off to the portal. So go back to the design in which the caller is responsible for making sure everything is copied into the portal if necessary.
-
- 02 4月, 2008 2 次提交
-
-
由 Magnus Hagander 提交于
default_transaction_isolation, session_replication_role and regex_flavor.
-
由 Bruce Momjian 提交于
< < * Prefix command-line utilities like createuser with 'pg_' < < http://archives.postgresql.org/pgsql-hackers/2007-06/msg00025.php <
-
- 01 4月, 2008 4 次提交
-
-
由 Tom Lane 提交于
Pavel Stehule, with some improvements by myself.
-
由 Tom Lane 提交于
that is commands that have out-of-line parameters but the plan is prepared assuming that the parameter values are constants. This is needed for the plpgsql EXECUTE USING patch, but will probably have use elsewhere. This commit includes the SPI functions and documentation, but no callers nor regression tests. The upcoming EXECUTE USING patch will provide regression-test coverage. I thought committing this separately made sense since it's logically a distinct feature.
-
由 Tom Lane 提交于
eval_const_expressions needs to be passed the PlannerInfo ("root") structure, because in some cases we want it to substitute values for Param nodes. (So "constant" is not so constant as all that ...) This mistake partially disabled optimization of unnamed extended-Query statements in 8.3: in particular the LIKE-to-indexscan optimization would never be applied if the LIKE pattern was passed as a parameter, and constraint exclusion depending on a parameter value didn't work either.
-
由 Tom Lane 提交于
Add some regression tests for plausible failures in this area.
-
- 31 3月, 2008 5 次提交
-
-
由 Tom Lane 提交于
while EState still contains pointers to those relations. Exposed by the CLOBBER_CACHE_ALWAYS tests that buildfarm member jaguar is running (I knew those cycles would pay off...)
-
由 Tom Lane 提交于
key files that are similar to the one for the postmaster's data directory permissions check. (I chose to standardize on that one since it's the most heavily used and presumably best-wordsmithed by now.) Also eliminate explicit tests on file ownership in these places, since the ensuing read attempt must fail anyway if it's wrong, and there seems no value in issuing the same error message for distinct problems. (But I left in the explicit ownership test in postmaster.c, since it had its own error message anyway.) Also be more specific in the documentation's descriptions of these checks. Per a gripe from Kevin Hunter.
-
由 Tom Lane 提交于
The places that did, eg, (statbuf.st_mode & S_IFMT) == S_IFDIR were correct, but there is no good reason not to use S_ISDIR() instead, especially when that's what the other 90% of our code does. The places that did, eg, (statbuf.st_mode & S_IFDIR) were flat out *wrong* and would fail in various platform-specific ways, eg a symlink could be mistaken for a regular file on most Unixen. The actual impact of this is probably small, since the problem cases seem to always involve symlinks or sockets, which are unlikely to be found in the directories that PG code might be scanning. But it's clearly trouble waiting to happen, so patch all the way back anyway. (There seem to be no occurrences of the mistake in 7.4.)
-
由 Tom Lane 提交于
database size, when available to the current user. Andrew Gilligan
-
由 Tom Lane 提交于
\d output for a table. Kenneth D'Souza, some changes by myself.
-
- 30 3月, 2008 3 次提交
-
-
由 Neil Conway 提交于
This requires a working 64-bit integer type. If such a type cannot be found, "--disable-integer-datetimes" can be used to switch back to the previous floating point-based datetime implementation.
-
由 Tom Lane 提交于
Harald Armin Massa.
-
由 Tom Lane 提交于
where the relation name was schema-qualified, for example UPDATE foo.bar SET <tab> Also support cases where the relation name was quoted unnecessarily, for example UPDATE "foo" SET <tab> Greg Sabino Mullane, slightly simplified by myself.
-
- 29 3月, 2008 1 次提交
-
-
由 Tom Lane 提交于
Whatever we do about that, this isn't the path to the solution.
-
- 28 3月, 2008 9 次提交
-
-
由 Bruce Momjian 提交于
> * -Add ability to trigger on TRUNCATE
-
由 Heikki Linnakangas 提交于
restore_command should report failure on non-existent .backup and .history files. Tidy up some related text along the way. Patch by Markus Bertheau, with some editing by Simon Riggs and myself.
-
由 Bruce Momjian 提交于
> > o Add CASE capability to language (already in SQL) > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00696.php > >
-
由 Bruce Momjian 提交于
> * Allow one transaction to see tuples using the snapshot of another > transaction > > This would assist multiple backends in working together. > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00400.php
-
由 Tom Lane 提交于
useless for an ungrouped-aggregate query holds regardless of whether optimize_minmax_aggregates succeeds. So we might as well apply the optimization in any case. I'll leave 8.3 as it was, since this version is a tad more invasive than my earlier patch.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
> > * Consider being smarter about memory and external files used during > sorts > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg01101.php > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00045.php
-
由 Bruce Momjian 提交于
* Consider allowing control of upper/lower case folding of unquoted identifiers > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00849.php
-
由 Tom Lane 提交于
the query result must be exactly one row (since we don't do this when there's any GROUP BY). Therefore any ORDER BY or DISTINCT attached to the query is useless and can be dropped. Aside from saving useless cycles, this protects us against problems with matching the hacked-up tlist entries to sort clauses, as seen in a bug report from Taiki Yamaguchi. We might need to work harder if we ever try to optimize grouped queries with this approach, but this solution will do for now.
-