- 06 5月, 2005 6 次提交
-
-
由 Tom Lane 提交于
too, but that one is in my way at the moment.)
-
由 Tom Lane 提交于
is a way to recover from disabling connections to all databases at once.
-
由 Bruce Momjian 提交于
understands arg control, so we don't need our own. In fact, it also uses macros that conflict with ours, so we _can't_ use our own.
-
由 Tom Lane 提交于
we are at it. Add release notes.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Jason Erickson
-
- 05 5月, 2005 7 次提交
-
-
由 Neil Conway 提交于
executable against the maximal set of libraries it might need. So for example, if one executable requires `libreadline', all executables are linked against it. The easiest fix is to make use of GNU ld's --as-needed flag, which ignores linker arguments that are not actually needed by the specified object files. The attached patch modifies configure to check for this flag (when using GNU ld), and if ld supports it, adds the flag to LDFLAGS (we need to do the check since only relatively recent versions of GNU ld support this capability). Currently only GNU ld is supported; I'm not aware of any other linkers that support this functionality.
-
由 Tom Lane 提交于
startup to end, rather than re-opening it in each MultiExecBitmapIndexScan call. I had foolishly thought that opening/closing wouldn't be much more expensive than a rescan call, but that was sheer brain fade. This seems to fix about half of the performance lossage reported by Sergey Koposov. I'm still not sure where the other half went.
-
由 Bruce Momjian 提交于
Rosser Schwarz
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
moment this has no particular use except to allow table rows to be passed to record_out(), but that case seems to be useful in itself per recent example from Elein. Further down the road we could look at letting PL functions be declared to accept RECORD parameters.
-
由 Tom Lane 提交于
so that restart doesn't fail when old postmaster died unbetimes.
-
由 Tom Lane 提交于
-
- 04 5月, 2005 4 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
are creating a new MultiXactId from two regular XIDs. The original coding was unnecessarily complicated and didn't save any code anyway.
-
由 Tom Lane 提交于
output area as INTERNAL not CSTRING. This is to prevent people from calling the functions by hand. This is a permanent solution for the back branches but I hope it is just a stopgap for HEAD.
-
由 Tom Lane 提交于
that return INTERNAL without also having INTERNAL arguments. Since the functions in question aren't meant to be called by hand anyway, I just redeclared them to take 'internal' instead of 'text'. Also add code to ProcedureCreate() to enforce the restriction, as I should have done to start with :-(
-
- 03 5月, 2005 4 次提交
-
-
由 Neil Conway 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< * Remove unreferenced table files created by transactions that were > * -Check for unreferenced table files created by transactions that were
-
由 Bruce Momjian 提交于
files in the server log. Heikki Linnakangas
-
- 02 5月, 2005 3 次提交
-
-
由 Neil Conway 提交于
pages. From Robert Treat.
-
由 Neil Conway 提交于
to produce when running the executor. This is consistent with the internal executor APIs (such as ExecutorRun), which also use a long for this purpose. It also allows FETCH_ALL to be passed -- since FETCH_ALL is defined as LONG_MAX, this wouldn't have worked on platforms where int and long are of different sizes. Per report from Tzahi Fadida.
-
由 Tom Lane 提交于
only one argument. (Per recent discussion, the option to accept multiple arguments is pretty useless for user-defined types, and would be a likely source of security holes if it was used.) Simplify call sites of output/send functions to not bother passing more than one argument.
-
- 01 5月, 2005 6 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Neil Conway 提交于
for a long time.
-
由 Tom Lane 提交于
argument, since that's all they are using now. Adjust type_sanity regression test so that it will complain if anyone tries to define multiple-argument output functions in future.
-
由 Tom Lane 提交于
record object itself, rather than relying on a second OID argument to be correct. This patch just changes the function behavior and not the catalogs, so it's OK to back-patch to 8.0. Will remove the now-redundant second argument in pg_proc in a separate patch in HEAD only.
-
由 Tom Lane 提交于
is contention for a tuple-level lock. This solves the problem of a would-be exclusive locker being starved out by an indefinite succession of share-lockers. Per recent discussion with Alvaro.
-
- 30 4月, 2005 5 次提交
-
-
由 Neil Conway 提交于
a warning when a variable is used as a format string for printf() and similar functions (if the variable is derived from untrusted data, it could include unexpected formatting sequences). This emits too many warnings to be enabled by default, but it does flag a few dubious constructs in the Postgres tree. This patch fixes up the obvious variants: functions that are passed a variable format string but no additional arguments. Most of these are harmless (e.g. the ruleutils stuff), but there is at least one actual bug here: if you create a trigger named "%sfoo", pg_dump will read uninitialized memory and fail to dump the trigger correctly.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Christopher Browne
-
由 Tom Lane 提交于
Essentially, we shoehorn in a lockable-object-type field by taking a byte away from the lockmethodid, which can surely fit in one byte instead of two. This allows less artificial definitions of all the other fields of LOCKTAG; we can get rid of the special pg_xactlock pseudo-relation, and also support locks on individual tuples and general database objects (including shared objects). None of those possibilities are actually exploited just yet, however. I removed pg_xactlock from pg_class, but did not force initdb for that change. At this point, relkind 's' (SPECIAL) is unused and could be removed entirely.
-
- 29 4月, 2005 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Neil Conway 提交于
incorrect -F argument: write_msg() expects its first parameter to be a "module name", not the format string.
-
由 Bruce Momjian 提交于
> * -Implement shared row locks and use them in RI triggers
-