- 07 4月, 2005 2 次提交
-
-
由 Tom Lane 提交于
ExecProcNode() with a NULL value, so the test couldn't do anything for us except maybe mask bugs. Removing it probably doesn't save anything much either, but then again this is a hot-spot routine.
-
由 Tom Lane 提交于
few palloc's. I also chose to eliminate the restype and restypmod fields entirely, since they are redundant with information stored in the node's contained expression; re-examining the expression at need seems simpler and more reliable than trying to keep restype/restypmod up to date. initdb forced due to change in contents of stored rules.
-
- 06 4月, 2005 4 次提交
-
-
由 Bruce Momjian 提交于
required for us to pull it into the main website. Same kind of fixes as last time, just make sure things aren't violating the HTML standard. No context changes at all. Magnus Hagander
-
由 Neil Conway 提交于
output of \dD in psql. From Greg Sabino Mullane.
-
由 Neil Conway 提交于
braces around single statements (for PG_TRY macros). This patch fixes it. Alvaro Herrera.
-
由 Tom Lane 提交于
OPENed on non-SELECT commands such as EXPLAIN or SHOW (anything that returns tuples is allowed). This flexibility already existed for bound cursors, but OPEN was artificially restricting what it would take. Per a gripe some months back.
-
- 05 4月, 2005 3 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Neil Conway 提交于
performance hack Tom introduced recently. This means we can avoid copying the transition array for each input tuple if these functions are invoked as aggregate transition functions. To test the performance improvement, I created a 1 million row table with a single int4 column. Without the patch, SELECT avg(col) FROM table took about 4.2 seconds (after the data was cached); with the patch, it took about 3.2 seconds. Naturally, the performance improvement for a less trivial query (or a table with wider rows) would be relatively smaller.
-
- 04 4月, 2005 4 次提交
-
-
由 Neil Conway 提交于
not the brand of vodka. Complete FETCH <sth> <sth> with FROM and IN, not FROM and TO (which is still pretty incomplete, but at least its the right syntax).
-
由 Neil Conway 提交于
From Robert Treat.
-
由 Neil Conway 提交于
comment. Patch from Alvaro.
-
由 Tom Lane 提交于
outer side of an outer join. Per andrew@supernews.
-
- 03 4月, 2005 1 次提交
-
-
由 Tom Lane 提交于
daemonize routine, namely forcing stdin/stdout/stderr to point to /dev/null. Per Karl Denninger.
-
- 02 4月, 2005 7 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
cases with binary-compatible relabeling. My first try was implicitly assuming that all operators scalarineqsel is used for have binary- compatible datatypes on both sides ... which is very wrong of course. Per report from Michael Fuhr.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
PL languages.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
- 01 4月, 2005 6 次提交
-
-
由 Bruce Momjian 提交于
January --- would return wrong year for 2005-01-01 and 2006-01-01. per report from Robert Creager. Backpatch to 8.0.X.
-
由 Bruce Momjian 提交于
-
由 Neil Conway 提交于
-
由 Bruce Momjian 提交于
for a function taking no arguments, per report from Michael Fuhr.
-
由 Tom Lane 提交于
exit. Without this, operations triggered during backend exit (such as temp table deletions) won't be counted ... which given heavy usage of temp tables can lead to pg_autovacuum falling way behind on the need to vacuum pg_class and pg_attribute. Per reports from Steve Crawford and others.
-
由 Tom Lane 提交于
functions with OUT parameters. The various PLs still need work, as does pg_dump. Rudimentary docs and regression tests included.
-
- 31 3月, 2005 4 次提交
-
-
由 Teodor Sigaev 提交于
2 implement gtsvector_out for use with gevel module (debug GiST indexes, http://www.sai.msu.su/~megera/postgres/gist/gevel/)
-
由 Bruce Momjian 提交于
-
由 Neil Conway 提交于
old comment in the code claimed that this was necessary. Since it is not actually necessary any more, it is clearer to remove the comment and just return NULL instead -- the return value of ExecHash() is not used.
-
由 Neil Conway 提交于
Mark Kirkwood.
-
- 30 3月, 2005 5 次提交
-
-
由 Neil Conway 提交于
platforms, and suggest using ~/.pgpass instead.
-
由 Neil Conway 提交于
-
由 Neil Conway 提交于
-
由 Tom Lane 提交于
proposal for OUT parameter support. The columns don't actually *do* anything yet, they are just left NULLs. But I thought I'd commit this part separately as a fairly pure example of the tasks needed when adding a column to pg_proc or one of the other core system tables.
-
由 Tom Lane 提交于
implement any new feature, it just pushes the 'not implemented' error message deeper into the backend. I also tweaked the grammar to accept Oracle-ish parameter syntax (parameter name first), as well as the SQL99 standard syntax (parameter mode first), since it was easy and people will doubtless try to use both anyway.
-
- 29 3月, 2005 3 次提交
-
-
由 Tom Lane 提交于
former to 100 by default. Clean up some of the less necessary dependencies on FUNC_MAX_ARGS; however, the biggie (FunctionCallInfoData) remains.
-
由 Neil Conway 提交于
-
由 Tom Lane 提交于
change saves a great deal of space in pg_proc and its primary index, and it eliminates the former requirement that INDEX_MAX_KEYS and FUNC_MAX_ARGS have the same value. INDEX_MAX_KEYS is still embedded in the on-disk representation (because it affects index tuple header size), but FUNC_MAX_ARGS is not. I believe it would now be possible to increase FUNC_MAX_ARGS at little cost, but haven't experimented yet. There are still a lot of vestigial references to FUNC_MAX_ARGS, which I will clean up in a separate pass. However, getting rid of it altogether would require changing the FunctionCallInfoData struct, and I'm not sure I want to buy into that.
-
- 28 3月, 2005 1 次提交
-
-
由 Tom Lane 提交于
transaction rollback via UNDO but I think that's highly unlikely to happen, so we may as well remove the stubs. (Someday we ought to rip out the stub xxx_undo routines, too.) Per Alvaro.
-