- 16 Sep, 2005 6 commits
-
-
Bruce Momjian authored
> o Add single-step debugging of PL/PgSQL functions
-
Neil Conway authored
sake of brevity and clarity. Make pg_reload_conf(), pg_rotate_logfile(), and pg_cancel_backend() return a boolean rather than an integer to indicate success or failure. Along the way, make some minor cleanups to dbsize.c -- in particular, use elog() rather than ereport() for "shouldn't happen" error conditions, and remove some of the more flagrant violations of the Postgres indentation conventions. Catalog version bumped.
-
Neil Conway authored
-
Tom Lane authored
-
Alvaro Herrera authored
Robert Treat.
-
Tom Lane authored
bytes. This shouldn't make any difference on x86 machines, where the size happened to be 16 bytes anyway, but on 64-bit machines and machines with slock_t int or wider, it will speed array indexing and hopefully reduce SMP cache contention effects. Per recent experimentation.
-
- 15 Sep, 2005 3 commits
-
-
Neil Conway authored
-
Teodor Sigaev authored
-
Teodor Sigaev authored
2 Makefile fixes
-
- 14 Sep, 2005 3 commits
-
-
Neil Conway authored
the builtin functions (although some more entries are still needed), and remove the duplicate index entries that have been causing collateindex.pl warnings. Consistently use "int" and "bigint", rather than a mix of "int", "integer", "int4", "bigint", and "int8". Make parenthesis style in syntax examples more consistent. Various copy-editing for newly-added documentation and SGML markup fixes.
-
Neil Conway authored
in parsing cursor declarations.
-
Tom Lane authored
-
- 13 Sep, 2005 3 commits
-
-
Tom Lane authored
Roman Neuhauser. Update some obsolete comments for exec_eval_datum, too.
-
Neil Conway authored
-
Alvaro Herrera authored
-
- 12 Sep, 2005 10 commits
-
-
Tom Lane authored
-
Neil Conway authored
consistent with the other sections in this chapter.
-
Tom Lane authored
recovered. I did not see any actual leak while testing this in CVS tip, but 8.0 definitely has a problem with leaking the space temporarily palloc'd by BufferSync(). In any case this seems a good idea to forestall similar problems in future. Per report from Arjen van der Meijden.
-
Neil Conway authored
a section of the "Server Run-time Environment" chapter. Also, move the SGML for the new chapter to a separate file and fix the resulting fallout.
-
Tom Lane authored
particular the addition of bitmap scans and the relaxation of rules about when multicolumn indexes can be used. Also some minor editorial work in other parts of the chapter.
-
Neil Conway authored
-
Tom Lane authored
appears in the REINDEX ref page.
-
Michael Meskes authored
-
Neil Conway authored
-
Tom Lane authored
to drop connections unceremoniously. Also some other marginal cleanups: don't query getsockopt() repeatedly if it fails, and avoid having the apparent definition of struct Port depend on which system headers you might have included or not. Oliver Jowett and Tom Lane.
-
- 11 Sep, 2005 3 commits
-
-
Neil Conway authored
rather than "-" for the "dash" character. Correct SGML markup. Make references to the names of contributors more consistent. Rewrite a bit of prose, and make some other similar cleanups.
-
Tom Lane authored
> found in a pg_dump archive. It had problems with dollar-quote tags broken across bufferload boundaries (this may explain bug report from Rod Taylor), also with dollar-quote literals of the form $a$a$..., and was also confused about the rules for backslash in double quoted identifiers (ie, they're not special). Also put in placeholder support for E'...' literals --- this will need more work later.
-
Tom Lane authored
really the source or destination of the archive. I think this will resolve recent complaints that password prompting is broken in pg_restore on Windows. Note that password prompting and reading from stdin is an unworkable combination on Windows ... but that was true anyway.
-
- 10 Sep, 2005 1 commit
-
-
Bruce Momjian authored
-
- 09 Sep, 2005 3 commits
-
-
Tom Lane authored
is certainly no longer immutable, but must indeed be marked volatile. I wonder if it should use the value of now() (that is, transaction start time) so that it could be marked stable. But it's probably not important enough to be worth changing the code for ... indeed, I'm not even going to force an initdb for this catalog change, seeing that we just did one a few hours ago.
-
Tom Lane authored
is a non-finite timestamp, for consistency with related functions. In other words: +infinity rotated to a different timezone is still +infinity.
-
Tom Lane authored
in the zic database or zone names found in the date token table. This preserves the old ability to do AT TIME ZONE 'PST' along with the new ability to do AT TIME ZONE 'PST8PDT'. Per gripe from Bricklen Anderson. Also, fix some inconsistencies in usage of TZ_STRLEN_MAX --- the old code had the potential for one-byte buffer overruns, though given alignment considerations it's unlikely there was any real risk.
-
- 08 Sep, 2005 2 commits
- 07 Sep, 2005 1 commit
-
-
Tom Lane authored
Among other changes, this reflects the recently passed change in USA daylight savings rules.
-
- 05 Sep, 2005 5 commits
-
-
Tom Lane authored
as per my recent proposal. For now the template data is hard-wired in proclang.c --- this should be replaced later by a new shared system catalog, but we don't want to force initdb during 8.1 beta. This change lets us cleanly load existing dump files even if they contain outright wrong information about a PL's support functions, such as a wrong path to the shared library or a missing validator function. Also, we can revert the recent kluges to make pg_dump dump PL support functions that are stored in pg_catalog. While at it, I removed the code in pg_regress that replaced $libdir with a hardcoded path for temporary installations. This is no longer needed given our support for relocatable installations.
-
Tom Lane authored
when there are extra resjunk columns in the child node. I found some additional cases involving Append nodes that weren't handled by the prior patch, and it's not clear how to fix them in the same way without breaking inheritance cases. So the prudent path seems to be to narrow the scope of the optimization.
-
Tom Lane authored
-
Tom Lane authored
has to recopy the input plan node's targetlist if it removes a SubqueryScan node just below the non-projecting node. For simplicity I made it recopy always. Per bug report from Allan Wang and Michael Fuhr.
-
Andrew Dunstan authored
Suggestion by Darcy Buskermolen, reworded by me.
-