- 06 10月, 2008 14 次提交
-
-
由 Tom Lane 提交于
from a query level above the current ParseState.
-
由 Heikki Linnakangas 提交于
relation forks. While the file names are not visible to users, for those that do peek into the data directory, it's nice to have more descriptive names. Per Greg Stark's suggestion.
-
由 Tom Lane 提交于
-
由 Magnus Hagander 提交于
the value a parameter has at server start and will have after RESET, respectively. Greg Smith, with some modifications by me.
-
由 Heikki Linnakangas 提交于
-
由 Tom Lane 提交于
maybe isalnum is returning a value with the low-order byte all zero?
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
well as regular tables. Per discussion, this seems necessary to meet the principle of least astonishment. In passing, simplify the error messages in warnAutoRange(). Now that we have parser error position info for these errors, it doesn't seem very useful to word the error message differently depending on whether we are inside a sub-select or not.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
machine produces zero (rather than the more usual minimum-possible-integer) for the only possible overflow case. This has been seen to occur for at least some word widths on some hardware, and it's cheap enough to check for everywhere. Per Peter's analysis of buildfarm reports. This could be back-patched, but in the absence of any gripes from the field I doubt it's worth the trouble.
-
由 Tom Lane 提交于
non-recursive term. Per an example from Dickson S. Guedes.
-
由 Tom Lane 提交于
recursive CTE that we're still in progress of analyzing. Add a similar guard to the similar code in expandRecordVariable(), and tweak regression tests to cover this case. Per report from Dickson S. Guedes.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
nullvalue, nonvalue. A long time ago, these were used to implement the SQL constructs IS TRUE, etc.
-
- 05 10月, 2008 4 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
int8-exp-three-digits.out update untested, might need refinement.
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
There are some unimplemented aspects: recursive queries must use UNION ALL (should allow UNION too), and we don't have SEARCH or CYCLE clauses. These might or might not get done for 8.4, but even without them it's a pretty useful feature. There are also a couple of small loose ends and definitional quibbles, which I'll send a memo about to pgsql-hackers shortly. But let's land the patch now so we can get on with other development. Yoshiyuki Asaba, with lots of help from Tatsuo Ishii and Tom Lane
-
- 04 10月, 2008 2 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
knowledge disappears again.
-
- 03 10月, 2008 5 次提交
-
-
由 Peter Eisentraut 提交于
input formats.
-
由 Peter Eisentraut 提交于
changes. Add some documenting comments.
-
由 Peter Eisentraut 提交于
builds. It is too complicated to fix in another way for now.
-
由 Heikki Linnakangas 提交于
name of a fork ('main' or 'fsm', at the moment) to pg_relation_size() to get the size of a specific fork. Defaults to 'main', if none given. While we're at it, modify pg_relation_size to take a regclass as argument, instead of separate variants taking oid and name. This change is transparent to typical use where the table name is passed as a string literal, like pg_relation_size('table'), but will break queries like pg_relation_size(namecol), where namecol is of type name. text-type input still works, and using a non-schema-qualified table name is not very reliable anyway, so this is unlikely to break anyone's queries in practice.
-
由 Bruce Momjian 提交于
code in 8.4.
-
- 02 10月, 2008 7 次提交
-
-
由 Tom Lane 提交于
when using --enable-integer-datetimes and a non-ISO datestyle. Ron Mayer
-
由 Tom Lane 提交于
-
由 Heikki Linnakangas 提交于
large enough for block numbers higher than 2^31. The old pre-FSM-rewrite pg_freespacemap implementation got this right. While we're at it, remove some unnecessary #includes.
-
由 Heikki Linnakangas 提交于
"pg_freespacemap". Reported by hubert depesz lubaczewski.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
in both input and output dir, to handle vpath builds more simply.
-
由 Tom Lane 提交于
This facility replaces the former mark/restore support but is otherwise upward-compatible with previous uses. It's expected to be needed for single evaluation of CTEs and also for window functions, so I'm committing it separately instead of waiting for either one of those patches to be finished. Per discussion with Greg Stark and Hitoshi Harada. Note: I removed nodeFunctionscan's mark/restore support, instead of bothering to update it for this change, because it was dead code anyway.
-
- 01 10月, 2008 3 次提交
-
-
由 Magnus Hagander 提交于
required by at least NetBSD. Markus Schaaf
-
由 Tom Lane 提交于
complain here, but some do)
-
由 Heikki Linnakangas 提交于
replay, because it tries to XLogInsert().
-
- 30 9月, 2008 5 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Heikki Linnakangas 提交于
changes from the main FSM commit for some reason.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
free space information is stored in a dedicated FSM relation fork, with each relation (except for hash indexes; they don't use FSM). This eliminates the max_fsm_relations and max_fsm_pages GUC options; remove any trace of them from the backend, initdb, and documentation. Rewrite contrib/pg_freespacemap to match the new FSM implementation. Also introduce a new variant of the get_raw_page(regclass, int4, int4) function in contrib/pageinspect that let's you to return pages from any relation fork, and a new fsm_page_contents() function to inspect the new FSM pages.
-