- 02 10月, 2008 6 次提交
-
-
由 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.
-
- 29 9月, 2008 2 次提交
- 28 9月, 2008 1 次提交
-
-
由 Andrew Dunstan 提交于
-
- 26 9月, 2008 2 次提交
-
-
由 Tom Lane 提交于
Alex Hunsaker
-
由 Tom Lane 提交于
(ie, has nothing to quote), rather than silently ignoring the character as has been our historical behavior. This is required by SQL spec and should help reduce the sort of user confusion seen in bug #4436. Per discussion. This is not so much a bug fix as a definitional change, and it could break existing applications; so not back-patched. It might deserve being mentioned as an incompatibility in the 8.4 release notes.
-
- 25 9月, 2008 6 次提交
-
-
由 Tom Lane 提交于
element types. Since the backend doesn't actually pay attention to the array type's delimiter, this has no functional effect, but it seems better for the catalog entries to be consistent. Per gripe from Greg Mullane and subsequent discussion.
-
由 Bruce Momjian 提交于
Jeff Davis
-
由 Bruce Momjian 提交于
round: select interval '0:0:0.7', interval '@ 0.70 secs', interval '0.7 seconds'; Ron Mayer
-
由 Heikki Linnakangas 提交于
"datctype" columns were misspelled. Per report from Chris Browne.
-
由 Tom Lane 提交于
a SubLink expression into a rule query. We missed cases where the original query contained a sub-SELECT in a function in FROM, a multi-row VALUES list, or a RETURNING list. Per bug #4434 from Dean Rasheed and subsequent investigation. Back-patch to 8.1; older releases don't have the issue because they didn't try to be smart about setting hasSubLinks only when needed.
-
由 Bruce Momjian 提交于
-
- 24 9月, 2008 6 次提交
-
-
由 Tom Lane 提交于
buildfarm member 'bear'.
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
with situtations when the file contains an EOF maker (0x1A) on Windows. ITAGAKI Takahiro
-
由 Magnus Hagander 提交于
security level with other parts of the system. Per gripe from Tom
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 23 9月, 2008 2 次提交
-
-
由 Heikki Linnakangas 提交于
matches the encoding of the locale. LC_COLLATE is now checked in addition to LC_CTYPE.
-
由 Heikki Linnakangas 提交于
ctype are now more like encoding, stored in new datcollate and datctype columns in pg_database. This is a stripped-down version of Radek Strnad's patch, with further changes by me.
-
- 22 9月, 2008 3 次提交
-
-
由 Tom Lane 提交于
that presence of the password in the conninfo string must be checked *before* risking a connection attempt, there is no point in checking it afterwards. This makes the specification of PQconnectionUsedPassword() a bit simpler and perhaps more generally useful, too.
-
由 Tom Lane 提交于
conninfo string *before* trying to connect to the remote server, not after. As pointed out by Marko Kreen, in certain not-very-plausible situations this could result in sending a password from the postgres user's .pgpass file, or other places that non-superusers shouldn't have access to, to an untrustworthy remote server. The cleanest fix seems to be to expose libpq's conninfo-string-parsing code so that dblink can check for a password option without duplicating the parsing logic. Joe Conway, with a little cleanup by Tom Lane
-
由 Tom Lane 提交于
instead of listing all the columns returned by the underlying function. initdb not forced since this patch doesn't actually change anything about the stored form of the views. It just means there's one less place to change if someone wants to add columns to them.
-
- 20 9月, 2008 3 次提交
-
-
由 Tom Lane 提交于
sequence of operations that libpq goes through while creating a PGresult. Also, remove ill-considered "const" decoration on parameters passed to event procedures.
-
由 Tom Lane 提交于
Jan Urbanski
-
由 Tom Lane 提交于
guarantees about whether event procedures will receive DESTROY events. They no longer need to defend themselves against getting a DESTROY without a successful prior CREATE. Andrew Chernow
-
- 19 9月, 2008 1 次提交
-
-
由 Magnus Hagander 提交于
can be used from Slony functions. Per report from Hiroshi Saito.
-