- 09 2月, 2007 7 次提交
-
-
由 Bruce Momjian 提交于
< * Consider placing all sequences in a single table, now that system < tables are full transactional > * Consider placing all sequences in a single table
-
由 Bruce Momjian 提交于
> * Consider placing all sequences in a single table, now that system > tables are full transactional
-
由 Bruce Momjian 提交于
* Add support for SQL-standard GENERATED/IDENTITY columns > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00038.php
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
get away with not (re)initializing a local variable if the variable is marked "isconst" and not "isnull". Unfortunately it makes this decision after having already freed the old value, meaning that something like for i in 1..10 loop declare c constant text := 'hi there'; leads to subsequent accesses to freed memory, and hence probably crashes. (In particular, this is why Asif Ali Rehman's bug leads to crash and not just an unexpectedly-NULL value for SQLERRM: SQLERRM is marked CONSTANT and so triggers this error.) The whole thing seems wrong on its face anyway: CONSTANT means that you can't change the variable inside the block, not that the initializer expression is guaranteed not to change value across successive block entries. Hence, remove the "optimization" instead of trying to fix it.
-
由 Tom Lane 提交于
DECLARE section needs to know about it. Formerly, everyplace besides DECLARE that created variables needed to do "plpgsql_add_initdatums(NULL)" to prevent those variables from being sucked up as part of a subsequent DECLARE block. This is obviously error-prone, and in fact the SQLSTATE/SQLERRM patch had failed to do it for those two variables, leading to the bug recently exhibited by Asif Ali Rehman: a DECLARE within an exception handler tried to reinitialize SQLERRM. Although the SQLSTATE/SQLERRM patch isn't in any pre-8.1 branches, and so I can't point to a demonstrable failure there, it seems wise to back-patch this into the older branches anyway, just to keep the logic similar to HEAD.
-
由 Bruce Momjian 提交于
trnasformed to lower or upper string. Pavel Stehule
-
- 08 2月, 2007 15 次提交
-
-
由 Bruce Momjian 提交于
ach backend to re-load all shared_preload_libraries. Korry Douglas
-
由 Bruce Momjian 提交于
Teodor Sigaev
-
由 Bruce Momjian 提交于
For win32 in general, this makes it possible to run the regression tests as an admin user by using the same restricted token method that's used by pg_ctl and initdb. For vc++, it adds building of pg_regress.exe, adds a resultmap, and fixes how it runs the install. Magnus Hagander
-
由 Bruce Momjian 提交于
pg_standby is a production-ready program that can be used to create a Warm Standby server. Other configuration is required as well, all of which is described in the main server manual. Simon Riggs
-
由 Bruce Momjian 提交于
pg_standby is a production-ready program that can be used to create a Warm Standby server. Other configuration is required as well, all of which is described in the main server manual. Simon Riggs
-
由 Alvaro Herrera 提交于
the buildfarm via Stefan Kaltenbrunner. Patch from Heikki Linnakangas.
-
由 Peter Eisentraut 提交于
where possible, and fix some sites that apparently thought that fgets() will overwrite the buffer by one byte. Also add some strlcpy() to eliminate some weird memory handling.
-
由 Bruce Momjian 提交于
> Currently, an index split writes all the data on the split page to > WAL. That's a lot of WAL traffic. The tuples that are copied to the > right page need to be WAL logged, but the tuples that stay on the > original page don't. Heikki Linnakangas
-
由 Bruce Momjian 提交于
authentication checks in the backend. Gavin Sherry
-
由 Bruce Momjian 提交于
version. Backpatch to 8.2.X.
-
由 Bruce Momjian 提交于
Backpatch to 8.2.X.
-
由 Bruce Momjian 提交于
Assume "TM" when input fields are variable-length, like month or day names. This matches Oracle behavior.
-
由 Tom Lane 提交于
already collected in the current transaction; this allows plpgsql functions to watch for stats updates even though they are confined to a single transaction. Use this instead of the previous kluge involving pg_stat_file() to wait for the stats collector to update in the stats regression test. Internally, decouple storage of stats snapshots from transaction boundaries; they'll now stick around until someone calls pgstat_clear_snapshot --- which xact.c still does at transaction end, to maintain the previous behavior. This makes the logic a lot cleaner, at the price of a couple dozen cycles per transaction exit.
-
由 Tom Lane 提交于
changes (with an upper limit of 30 seconds), and record the delay time in the postmaster log. This should give us some info about what's happening with the intermittent stats failures in buildfarm. After an idea of Andrew Dunstan's.
-
由 Tom Lane 提交于
"database system is ready to accept connections", which is issued by the postmaster when it really is ready to accept connections. Per proposal from Markus Schiltknecht and subsequent discussion.
-
- 07 2月, 2007 14 次提交
-
-
由 Alvaro Herrera 提交于
Hagander.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
strange coding practices.
-
由 Tom Lane 提交于
thought that it didn't have to reposition the underlying tuplestore if the portal is atEnd. But this is not so, because tuplestores have separate read and write cursors ... and the read cursor hasn't moved from the start. This mistake explains bug #2970 from William Zhang. Note: the coding here is pretty inefficient, but given that no one has noticed this bug until now, I'd say hardly anyone uses the case where the cursor has been advanced before being persisted. So maybe it's not worth worrying about.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
<P>USA saving time changes are included in PostgreSQL release 8.0.[4+], and all later major releases, e.g. 8.1. Canada and Western Australia changes are included in 8.0.[10+], 8.1.[6+], and all later major releases. PostgreSQL releases prior to 8.0 use the operating system's timezone database for daylight saving information.</P>
-
由 Tom Lane 提交于
out that ExecEvalVar and friends don't necessarily have access to a tuple descriptor with correct typmod: it definitely can contain -1, and possibly might contain other values that are different from the Var's value. Arguably this should be cleaned up someday, but it's not a simple change, and in any case typmod discrepancies don't pose a security hazard. Per reports from numerous people :-( I'm not entirely sure whether the failure can occur in 8.0 --- the simple test cases reported so far don't trigger it there. But back-patch the change all the way anyway.
-
由 Bruce Momjian 提交于
* -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h * Consider making NAMEDATALEN more configurable in future releases
-
由 Tom Lane 提交于
-
- 06 2月, 2007 4 次提交
-
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
used to be part of libpq's exported interface many releases ago, but now it's no longer necessary to make it accessible to clients.
-
由 Tom Lane 提交于
had stopped working for tables buried inside views or sub-selects. This is because I had gotten rid of the simplify_jointree() preprocessing step, and optimize_minmax_aggregates() wasn't smart enough to deal with a non-canonical FromExpr. Per gripe from Bill Howe.
-
由 Tom Lane 提交于
-