- 26 1月, 2010 2 次提交
-
-
由 Tom Lane 提交于
and implement OVERLAY() for bit strings and bytea. In passing also convert text OVERLAY() to a true built-in, instead of relying on a SQL function. Leonardo F, reviewed by Kevin Grittner
-
由 Heikki Linnakangas 提交于
regular applications. Also add a comment pointing out that tab-complition for PREPARE TRANSACTION is missing on purpose.
-
- 25 1月, 2010 3 次提交
-
-
由 Tom Lane 提交于
You might think this is unnecessary since that interpreter is never used to run code --- but it turns out that's wrong. As of Tcl 8.5, the "clock" command (alone among builtin Tcl commands) is partially implemented by loaded-on-demand Tcl code, which means that it fails if there's not unknown-command support, and also that it's impossible to run it directly in a safe interpreter. The way they get around the latter is that Tcl_CreateSlave() automatically sets up an alias command that forwards any execution of "clock" in a safe slave interpreter to its parent interpreter. Thus, when attempting to execute "clock" in trusted pltcl, the command actually executes in the "hold" interpreter, where it will fail if unknown-command support hasn't been introduced by sourcing the standard init.tcl script, which is done by Tcl_Init(). (This is a pretty dubious design decision on the Tcl boys' part, if you ask me ... but they didn't.) Back-patch all the way. It's not clear that anyone would try to use ancient versions of pltcl with a recent Tcl, but it's not clear they wouldn't, either. Also add a regression test using "clock", in branches that have regression test support for pltcl. Per recent trouble report from Kyle Bateman.
-
由 Joe Conway 提交于
(SFRM_Materialize mode) to return tuples. Since we don't return from the dblink function in tuplestore mode, release the PGresult with a PG_CATCH block on error. Also rearrange to share the same code to materialize the tuplestore. Patch by Takahiro Itagaki.
-
由 Tom Lane 提交于
AbortTransaction or AbortSubTransaction, when trying to clean up after an error that prevented (sub)transaction start from completing: * access to TopTransactionResourceOwner that might not exist * assert failure in AtEOXact_GUC, if AtStart_GUC not called yet * assert failure or core dump in AfterTriggerEndSubXact, if AfterTriggerBeginSubXact not called yet Per testing by injecting elog(ERROR) at successive steps in StartTransaction and StartSubTransaction. It's not clear whether all of these cases could really occur in the field, but at least one of them is easily exposed by simple stress testing, as per my accidental discovery yesterday.
-
- 24 1月, 2010 4 次提交
-
-
由 Magnus Hagander 提交于
-
由 Tom Lane 提交于
the various disk-size-reporting functions will respond to query cancel reasonably promptly even in very large databases. Per report from Kevin Grittner.
-
由 Simon Riggs 提交于
with errdetail(). Add errhint() to suggest retry in certain cases.
-
由 Simon Riggs 提交于
woken by alarm we send SIGUSR1 to all backends requesting that they check to see if they are blocking Startup process. If so, they throw ERROR/FATAL as for other conflict resolutions. Deadlock stop gap removed. max_standby_delay = -1 option removed to prevent deadlock.
-
- 23 1月, 2010 4 次提交
-
-
由 Bruce Momjian 提交于
Now require gmake 3.79.1 or later to build source/sgml.
-
由 Robert Haas 提交于
Thanks to Devrim Gunduz for the report.
-
由 Robert Haas 提交于
I failed to 'cvs add' the new files and also neglected to bump catversion.
-
由 Robert Haas 提交于
Attributes can now have options, just as relations and tablespaces do, and the reloptions code is used to parse, validate, and store them. For simplicity and because these options are not performance critical, we store them in a separate cache rather than the main relcache. Thanks to Alex Hunsaker for the review.
-
- 22 1月, 2010 5 次提交
-
-
由 Bruce Momjian 提交于
documentation.
-
由 Peter Eisentraut 提交于
Also cleaned up some redundancies between the primary error messages and the error context in PL/Python. Hannu Valtonen
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
Applied patch by Boszormenyi Zoltan <zb@cybertec.at> to fix problem in auto-prepare mode if the connection is closed and re-opened and the previously prepared query is issued again.
-
由 Robert Haas 提交于
-
- 21 1月, 2010 10 次提交
-
-
由 Robert Haas 提交于
PQescapeLiteral is similar to PQescapeStringConn, but it relieves the caller of the need to know how large the output buffer should be, and it provides the appropriate quoting (in addition to escaping special characers within the string). PQescapeIdentifier provides similar functionality for escaping identifiers. Per recent discussion with Tom Lane.
-
由 Simon Riggs 提交于
-
由 Heikki Linnakangas 提交于
-
由 Itagaki Takahiro 提交于
from description of triggers with WHEN clause. Thanks to Brad T. Sliger for the review.
-
由 Simon Riggs 提交于
Discuss the reasons for the lock type we hold on ProcArrayLock while deriving the conflict list. Cover the idea of false positive conflicts and seemingly strange effects on snapshot derivation.
-
由 Tom Lane 提交于
we *must* generate probes.o or the dtrace probes don't work. Revert our workaround for their previous bug. Details at https://bugzilla.redhat.com/show_bug.cgi?id=557266
-
由 Peter Eisentraut 提交于
This extends the existing pg_service.conf facility to first look for a service definition file in the user's home directory.
-
由 Heikki Linnakangas 提交于
moving files around.
-
由 Heikki Linnakangas 提交于
that would've been WAL-logged if archiving was enabled. If we encounter such records in archive recovery anyway, we know that some data is missing from the log. A WARNING is emitted in that case. Original patch by Fujii Masao, with changes by me.
-
由 Heikki Linnakangas 提交于
binary, revert PGDLLIMPORT decoration of global variables. I'm not sure if there's any real harm from unnecessary PGDLLIMPORTs, but these are all internal variables that external modules really shouldn't be messing with. ThisTimeLineID still needs PGDLLIMPORT.
-
- 20 1月, 2010 12 次提交
-
-
由 Heikki Linnakangas 提交于
Fujii Masao
-
由 Heikki Linnakangas 提交于
has been renamed.
-
由 Heikki Linnakangas 提交于
has been renamed.
-
由 Heikki Linnakangas 提交于
walreceiver as whole into a dynamically loaded module, split the libpq-specific parts of it into dynamically loaded module and keep the rest in the main backend binary. Although Tom fixed the Windows compilation problems with the old walreceiver module already, this is a cleaner division of labour and makes the code more readable. There's also the prospect of adding new transport methods as pluggable modules in the future, which this patch makes easier, though for now the API between libpqwalreceiver and walreceiver process should be considered private. The libpq-specific module is now in src/backend/replication/libpqwalreceiver, and the part linked with postgres binary is in src/backend/replication/walreceiver.c.
-
由 Peter Eisentraut 提交于
name already exists, so we'd get an error message about a "type" instead of about a "relation", because the composite type code shares code with relation creation.
-
由 Andrew Dunstan 提交于
-
由 Andrew Dunstan 提交于
-
由 Robert Haas 提交于
-
由 Andrew Dunstan 提交于
quote_literal, quote_nullable, quote_ident, encode_bytea, decode_bytea, looks_like_number, encode_array_literal, encode_array_constructor. Split SPI.xs into two - SPI.xs now contains only SPI functions. Remainder are in new Util.xs. Some more code and documentation cleanup along the way, as well as adding some CVS markers to files missing them. Original patch from Tim Bunce, with a little editing from me.
-
由 Robert Haas 提交于
Modify the "Escaping Strings for Inclusion in SQL Commands" section to use a <variablelist> as the preceding and following sections do, and merge the "Escaping Binary Strings for Inclusion in SQL Commands" section into it. This changes only the formatting of these sections, not the content. It is intended to lay the groundwork for a follow-on patch to add some new escaping functions, but it makes sense to commit this first, for clarity.
-
由 Tom Lane 提交于
dump IDs, because the array we're using is sized according to the highest dump ID actually defined in the archive file. In a partial dump there could be references to higher dump IDs that weren't dumped. Treat these the same as references to in-range IDs that weren't dumped. (The whole thing is a bit scary because the missing objects might have been part of dependency chains, which we won't know about. Not much we can do though --- throwing an error is probably overreaction.) Also, reject parallel restore with pre-1.8 archive version (made by pre-8.0 pg_dump). In these old versions the dependency entries are OIDs, not dump IDs, and we don't have enough information to interpret them. Per bug #5288 from Jon Erdman.
-
由 Tom Lane 提交于
when the planner splits apart a ROW(...) IS NULL test, the argisrow values of the component tests have to be determined from the component field types, not copied from the original NullTest (in which argisrow is surely true).
-