- 02 1月, 2009 5 次提交
-
-
由 Magnus Hagander 提交于
the postmaster. They are only used in backend processes, so it's just a matter of re-labeling the GUCs.
-
由 Tom Lane 提交于
first; otherwise backends reading the file might reject values of custom variables. Per experimentation with auto_explain.
-
由 Tom Lane 提交于
and change auto_explain's custom GUC variables to be named auto_explain.xxx not just explain.xxx. Per discussion in connection with the pg_stat_statements patch, it seems like a good idea to have the convention that custom variable classes are named the same as their defining module. Committing separately since this should happen regardless of what happens with pg_stat_statements itself.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
is available during datatype input in Bind message processing. I put the PopActiveSnapshot() or equivalent just before PortalDefineQuery, which is an unsafe spot for it (in 8.3 and later) because we are carrying a plancache refcount that hasn't yet been assigned to the portal. Any error thrown there would result in leaking the refcount. It's not exactly likely that PopActiveSnapshot would throw an elog, perhaps, but it could happen. Reorder the code and add another comment warning not to do that.
-
- 01 1月, 2009 1 次提交
-
-
由 Tom Lane 提交于
frame clause, as appears to be required by the fine print in the SQL spec. Per discussion with Pavel, not doing so risks user confusion.
-
- 31 12月, 2008 2 次提交
-
-
由 Tom Lane 提交于
so that user-defined window functions are possible. For the moment you'll have to write them in C, for lack of any interface to the WindowObject API in the available PLs, but it's better than no support at all. There was some debate about the best syntax for this. I ended up choosing the "it's an attribute" position --- the other approach will inevitably be more work, and the likely market for user-defined window functions is probably too small to justify it.
-
由 Tom Lane 提交于
patch. This includes the ability to force the frame to cover the whole partition, and the ability to make the frame end exactly on the current row rather than its last ORDER BY peer. Supporting any more of the full SQL frame-clause syntax will require nontrivial hacking on the window aggregate code, so it'll have to wait for 8.5 or beyond.
-
- 30 12月, 2008 1 次提交
-
-
由 Tom Lane 提交于
field needs to be included in equalRuleLocks() comparisons, else updates will fail to propagate into relcache entries when they have positive reference count (ie someone is using the relcache entry). Per report from Alex Hunsaker.
-
- 29 12月, 2008 1 次提交
-
-
由 Tom Lane 提交于
Hitoshi Harada, with some kibitzing from Heikki and Tom.
-
- 28 12月, 2008 1 次提交
-
-
由 Tom Lane 提交于
upcoming window-functions patch. First, tuplestore_trim is now an exported function that must be explicitly invoked by callers at appropriate times, rather than something that tuplestore tries to do behind the scenes. Second, a read pointer that is marked as allowing backward scan no longer prevents truncation. This means that a read pointer marked as having BACKWARD but not REWIND capability can only safely read backwards as far as the oldest other read pointer. (The expected use pattern for this involves having another read pointer that serves as the truncation fencepost.)
-
- 25 12月, 2008 1 次提交
-
-
由 Bruce Momjian 提交于
TRACE_POSTGRESQL_WAL_BUFFER_WRITE_DIRTY Robert Lor
-
- 21 12月, 2008 1 次提交
-
-
由 Tom Lane 提交于
-
- 20 12月, 2008 4 次提交
-
-
由 Tom Lane 提交于
etc. I think this will fix the current buildfarm issues ...
-
由 Heikki Linnakangas 提交于
because transformGenericOptions returns an array, not an Oid. I'm not sure if this fixes the crashes seen in buildfarm, but it should be fixed anyway.
-
由 Tom Lane 提交于
useful yet, but I'm tired of re-merging this aspect of the window functions patch.
-
由 Peter Eisentraut 提交于
This doesn't do any remote or external things yet, but it gives modules like plproxy and dblink a standardized and future-proof system for managing their connection information. Martin Pihlak and Peter Eisentraut
-
- 19 12月, 2008 3 次提交
-
-
由 Tom Lane 提交于
explicit cast to show the intended array type, we forgot to teach ruleutils.c to print out such constructs properly. Found by noting bogus output from recent changes in polymorphism regression test.
-
由 Tom Lane 提交于
materialize-mode set results. Since it now uses the ReturnSetInfo node to hold internal state, we need to be sure to set up the node even when the immediately called function doesn't return set (but does have a set-valued argument). Per report from Anupama Aherrao.
-
由 Tom Lane 提交于
per recent discussions. In passing this also fixes a couple of bugs in the previous variadic-parameters patch.
-
- 17 12月, 2008 3 次提交
-
-
由 Heikki Linnakangas 提交于
skipped. We could update relpages anyway, but it seems better to only update it together with reltuples, because we use the reltuples/relpages ratio in the planner. Also don't update n_live_tuples in pgstat. ANALYZE in VACUUM ANALYZE now needs to update pg_class, if the VACUUM-phase didn't do so. Added some boolean-passing to let analyze_rel know if it should update pg_class or not. I also moved the relcache invalidation (to update rd_targblock) from vac_update_relstats to where RelationTruncate is called, because vac_update_relstats is not called for partial vacuums anymore. It's more obvious to send the invalidation close to the truncation that requires it. Per report by Ned T. Crigler.
-
由 Bruce Momjian 提交于
includes a few new ones. - Fixed compilation errors on OS X for probes that use typedefs - Fixed a number of probes to pass ForkNumber per the relation forks patch - The new probes are those that were taken out from the previous submitted patch and required simple fixes. Will submit the other probes that may require more discussion in a separate patch. Robert Lor
-
由 Tom Lane 提交于
the other major heapam.c functions. The only known consequence of this omission is that UPDATE RETURNING failed to return the correct value for "tableoid", as per report from KaiGai Kohei. Back-patch to 8.2. Arguably it's wrong all the way back; but without evidence of visible breakage before RETURNING was added, I'll desist from patching the older branches.
-
- 16 12月, 2008 3 次提交
-
-
由 Tom Lane 提交于
VIEW suggests that it'd be worth spelling the error messages out in a little more detail. This seems to help with localizing the problem.
-
由 Tom Lane 提交于
result in hopefully-less-confusing error messages when the new definition isn't compatible with the old; minor other cleanup.
-
由 Tom Lane 提交于
to return NULL, instead of erroring out, if the target object is specified by OID and we can't find that OID in the catalogs. Since these functions operate internally on SnapshotNow rules, there is a race condition when using them in user queries: the query's MVCC snapshot might "see" a catalog row that's already committed dead, leading to a failure when the inquiry function is applied. Returning NULL should generally provide more convenient behavior. This issue has been complained of before, and in particular we are now seeing it in the regression tests due to another recent patch.
-
- 15 12月, 2008 4 次提交
-
-
由 Tom Lane 提交于
to 10, to compensate for the recent change in default statistics target. The original number was pulled out of the air anyway :-(, but it was picked in the context of the old default, so holding the default size of the MCELEM array constant seems the best thing. Per discussion.
-
由 Tom Lane 提交于
pg_database_encoding_max_length() predicts the maximum character length returned by wchar2char(). Per Hiroshi Inoue, MB_CUR_MAX isn't usable on Windows because we allow encoding = UTF8 when the locale says differently; and getting rid of it seems a good idea on general principles because it narrows our dependence on libc's locale API just a little bit more. Also install a check for overflow of the buffer size computation.
-
由 Tom Lane 提交于
actual argument type of ANYARRAY to match an argument declared ANYARRAY, so long as ANYELEMENT etc aren't used. I had overlooked the fact that this is a possible case while fixing bug #3852; but it is possible because pg_statistic contains columns declared ANYARRAY. Per gripe from Corey Horton.
-
由 Magnus Hagander 提交于
calling recv() and send(). This makes the calls go through the socket emulation code on Win32, making them for example properly interruptible.
-
- 14 12月, 2008 1 次提交
-
-
由 Tom Lane 提交于
and its maximum value from 1000 to 10000. ALTER TABLE SET STATISTICS similarly now allows a value up to 10000. Per discussion.
-
- 13 12月, 2008 2 次提交
-
-
由 Tom Lane 提交于
in 8.3, too, but I'm not back-patching this change since it would break any extension modules that might be calling that function.
-
由 Tom Lane 提交于
when they are invoked by the parser. We had been setting up a snapshot at plan time but really it needs to be done earlier, before parse analysis. Per report from Dmitry Koterov. Also fix two related problems discovered while poking at this one: exec_bind_message called datatype input functions without establishing a snapshot, and SET CONSTRAINTS IMMEDIATE could call trigger functions without establishing a snapshot. Backpatch to 8.2. The underlying problem goes much further back, but it is masked in 8.1 and before because we didn't attempt to invoke domain check constraints within datatype input. It would only be exposed if a C-language datatype input function used the snapshot; which evidently none do, or we'd have heard complaints sooner. Since this code has changed a lot over time, a back-patch is hardly risk-free, and so I'm disinclined to patch further than absolutely necessary.
-
- 12 12月, 2008 1 次提交
-
-
由 Tom Lane 提交于
vacuuming (it's not), say "database-wide VACUUM" instead of "full-database VACUUM" in the relevant hint messages. Also, document the permissions needed to do this. Per today's discussion.
-
- 11 12月, 2008 3 次提交
-
-
由 Peter Eisentraut 提交于
platform-specific spellings of /dev/null. But one should be enough, so settle on DEVNULL.
-
由 Peter Eisentraut 提交于
to the gettext domain name, to simplify parallel installations. Also, rename set_text_domain() to pg_bindtextdomain(), because that is what it does.
-
由 Tom Lane 提交于
right child if it doesn't need to. This saves some miniscule number of cycles, but the ulterior motive is to avoid an optimization bug known to exist in SCO's C compiler (and perhaps others?)
-
- 09 12月, 2008 2 次提交
-
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
replication patch needs a signal, but we've already used SIGUSR1 and SIGUSR2 in normal backends. This patch allows reusing SIGUSR1 for that, and for other purposes too if the need arises.
-
- 08 12月, 2008 1 次提交
-
-
由 Tom Lane 提交于
where no function stats entries exist. Partial response to Pavel's observation that small VACUUM operations are noticeably slower in CVS HEAD than 8.3.
-