- 27 6月, 2005 3 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
with main, avoid using a SQL-defined SQLSTATE for what is most definitely not a SQL-compatible error condition, fix documentation omissions, adhere to message style guidelines, don't use two GUC_REPORT variables when one is sufficient. Nothing done about pg_dump issues.
-
由 Tom Lane 提交于
-
- 26 6月, 2005 5 次提交
-
-
由 Bruce Momjian 提交于
literally. Add GUC variables: "escape_string_warning" - warn about backslashes in non-E strings "escape_string_syntax" - supports E'' syntax? "standard_compliant_strings" - treats backslashes literally in '' Update code to use E'' when escapes are used.
-
由 Tom Lane 提交于
cosmetic at the moment, but someday Oid might be 64 bits ...
-
由 Tom Lane 提交于
CREATE DATABASE does one internally.
-
由 Tom Lane 提交于
should fix the recent reports of "index is not a btree" failures, as well as preventing a more obscure race condition involving changes to a template database just after copying it with CREATE DATABASE.
-
由 Tom Lane 提交于
was being called twice in normal operation, leading to a leak of one set of relcache subsidiary info. Per report from Jeff Gold.
-
- 25 6月, 2005 7 次提交
-
-
由 Bruce Momjian 提交于
> o Pass arrays natively instead of as text between plperl and postgres > o Add support for polymorphic arguments and return types to plperl
-
由 Bruce Momjian 提交于
< * Allow per-user, per-group quotas per-tablespace > * Allow per-tablespace quotas
-
由 Bruce Momjian 提交于
< * Allow per-user and per-tablespaces quotas > * Allow per-user, per-group quotas per-tablespace
-
由 Bruce Momjian 提交于
> * Allow per-user and per-tablespaces quotas
-
由 Bruce Momjian 提交于
> * Add NUMERIC division operator that doesn't round? > > Currently NUMERIC _rounds_ the result to the specified precision. > This means division can return a result that multiplied by the > divisor is greater than the dividend, e.g. this returns a value > 10: > > SELECT (10::numeric(2,0) / 6::numeric(2,0))::numeric(2,0) * 6; > > The positive modulus result returned by NUMERICs might be considered > inaccurate, in one sense. >
-
由 Bruce Momjian 提交于
> > Currently SIGTERM of a backend can lead to lock table corruption. >
-
由 Tom Lane 提交于
to the existing X-direction tests. An rtree class now includes 4 actual 2-D tests, 4 1-D X-direction tests, and 4 1-D Y-direction tests. This involved adding four new Y-direction test operators for each of box and polygon; I followed the PostGIS project's lead as to the names of these operators. NON BACKWARDS COMPATIBLE CHANGE: the poly_overleft (&<) and poly_overright (&>) operators now have semantics comparable to box_overleft and box_overright. This is necessary to make r-tree indexes work correctly on polygons. Also, I changed circle_left and circle_right to agree with box_left and box_right --- formerly they allowed the boundaries to touch. This isn't actually essential given the lack of any r-tree opclass for circles, but it seems best to sync all the definitions while we are at it.
-
- 24 6月, 2005 11 次提交
-
-
由 Tatsuo Ishii 提交于
-
由 Tom Lane 提交于
CURRENT_TIME, and LOCALTIME: now they just produce "timestamptz" not "timestamptz(6)", etc. This makes the behavior more consistent with our choice to not assign a specific default precision to column datatypes. It should also save a few cycles at runtime due to not having to invoke the round-to-given-precision functions. I also took the opportunity to translate CURRENT_TIMESTAMP into "now()" instead of an invocation of the timestamptz input converter --- this should save a few cycles too.
-
由 Tatsuo Ishii 提交于
performance. patches submitted by Atsushi Ogawa.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * -Fix incorrect rtree results due to wrong assumptions about "over" > operator semantics
-
由 Bruce Momjian 提交于
< * Allow REINDEX to rebuild all database indexes, remove /contrib/reindex > * -Allow REINDEX to rebuild all database indexes
-
由 Bruce Momjian 提交于
> * Add program to test if fsync has a delay compared to non-fsync
-
由 Neil Conway 提交于
-
由 Neil Conway 提交于
-
由 Tom Lane 提交于
polygon operators (<<, &<, >>, &>). Per ideas originally put forward by andrew@supernews and later rediscovered by moi. This patch just fixes the existing opclasses, and does not add any new behavior as I proposed earlier; that can be sorted out later. In principle this could be back-patched, since it changes only search behavior and not system catalog entries nor rtree index contents. I'm not currently planning to do that, though, since I think it could use more testing.
-
由 Bruce Momjian 提交于
< * Allow administrators to safely terminate individual sessions < < Right now, SIGTERM will terminate a session, but it is treated as < though the postmaster has paniced and shared memory might not be < cleaned up properly. A new signal is needed for safe termination < because backends must first do a query cancel, then exit once they < have run the query cancel cleanup routine. < > * Allow administrators to safely terminate individual sessions either > via an SQL function or SIGTERM
-
- 23 6月, 2005 6 次提交
-
-
由 Tom Lane 提交于
logical place for it since it is of no use to users. Per recent discussions on cleaning up contrib.
-
由 Tom Lane 提交于
a physically separate type. Defining 'lo' as a domain over OID works just fine and is more efficient. Improve documentation and fix up the test script. (Would like to turn test script into a proper regression test, but right now its output is not constant because of numeric OIDs; plus it makes Unix-specific assumptions about files it can import.)
-
由 Tom Lane 提交于
(There are more that will be removed once they've been copied to pgfoundry.org.)
-
由 Tom Lane 提交于
in the database. The old behavior (reindex system catalogs only) is now available as REINDEX SYSTEM. I did not add the complementary REINDEX USER case since there did not seem to be consensus for this, but it would be trivial to add later. Per recent discussions.
-
由 Tom Lane 提交于
of columns of a query result so that it can "see through" cursors and prepared statements. Per gripe a couple months back from John DeSoi.
-
由 Tom Lane 提交于
-
- 22 6月, 2005 6 次提交
-
-
由 Tom Lane 提交于
argument list contains parameter symbols ($n) declared as type VOID, discard these arguments. This allows the driver to avoid renumbering mixed IN and OUT argument placeholders (the JDBC syntax involves writing ? for both IN and OUT parameters, but on the server side we don't think that OUT parameters are arguments). This doesn't break any currently- useful cases since VOID is not used as an input argument type.
-
由 Neil Conway 提交于
we need to be careful to reset rc to PLPGSQL_RC_OK, depending on how the loop's logic is structured. If we continue a loop but it then exits without executing the loop's body again, we want to return PLPGSQL_RC_OK to our caller. Enhance the regression tests to catch this problem. Per report from Michael Fuhr.
-
由 Neil Conway 提交于
(1) The code doesn't initialize `sum', so the initial "does the checksum match?" test is wrong. (2) The loop that is intended to check for a "null block" just checks the first byte of the tar block 512 times, rather than each of the 512 bytes one time (!), which I'm guessing was the intent. It was only through sheer luck that this worked in the first place. Per Coverity static analysis performed by EnterpriseDB.
-
由 Neil Conway 提交于
is redundant after a check has already been made for "num < 0". The "set" variable can also be removed, as it is now no longer used. Per checking with Karel, this is the right fix. Per Coverity static analysis performed by EnterpriseDB.
-
由 Neil Conway 提交于
next iteration of a loop. Update documentation and add regression tests. Patch from Pavel Stehule, reviewed by Neil Conway.
-
由 Tom Lane 提交于
using the recently added lo_create() function. The restore logic in pg_restore is greatly simplified as well, since there's no need anymore to try to adjust database references to match a new set of blob OIDs.
-
- 21 6月, 2005 2 次提交
-
-
由 Tom Lane 提交于
Dave Page. Also, cause it to emit rather than ignore any ACL and datconfig options that may be set for these two databases.
-
由 Tom Lane 提交于
unlike template0 and template1 does not have any special status in terms of backend functionality. However, all external utilities such as createuser and createdb now connect to "postgres" instead of template1, and the documentation is changed to encourage people to use "postgres" instead of template1 as a play area. This should fix some longstanding gotchas involving unexpected propagation of database objects by createdb (when you used template1 without understanding the implications), as well as ameliorating the problem that CREATE DATABASE is unhappy if anyone else is connected to template1. Patch by Dave Page, minor editing by Tom Lane. All per recent pghackers discussions.
-