- 28 10月, 2015 5 次提交
-
-
由 Heikki Linnakangas 提交于
PyGreSQL-4.0 is in the git repository, it should not be ignored. The other files are legacy stuff that's not included in the repository, or built as part of the build, so remove them too.
-
由 Heikki Linnakangas 提交于
Based on patch by Raymond Barbiero
-
由 Heikki Linnakangas 提交于
It's important to pay attention to compiler warnings, but -Werror isn't buying us much at the moment. Firstly, there are a lot of warnings on modern versions of gcc. I have to pass: "-Wno-error=unused-but-set-variable -Wno-error=enum-compare -Wno-error=address -Wno-error=maybe-uninitialized" to make it compile. More important than erroring out on warnings is to make sure there are no warnings to begin with. Once we get to that state, any warnings will stick out like sore thumb anyway, and you won't need -Werror to make them more annoying. We have a long way until we are 100% warning free, but most of the warnings come from upstream code. They have been fixed in later versions of PostgreSQL, so they will go away as we merge with upstream.
-
由 Jimmy Yih 提交于
-
-
- 02 12月, 2006 13 次提交
-
-
由 PostgreSQL Daemon 提交于
v8.2.0 is now released ...
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
and penguin reported in recently enough to justify the assumption that we haven't broken ARM support in 8.2.
-
由 Tom Lane 提交于
locks that logically should not be released, because when a subtransaction overwrites XMAX all knowledge of the previous lock state is lost. It seems unlikely that we will be able to fix this before 8.3...
-
由 Tom Lane 提交于
should allow delete-pending files to actually go away, and thereby work around the various complaints we've seen about 'permission denied' errors in such cases. Should be reasonably harmless in any case...
-
- 01 12月, 2006 9 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
subtransaction are released if the subtransaction aborts --- in user-level terminology, this means either rolling back to a savepoint or escaping from a plpgsql exception block. Per recent suggestion from Simon.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Olivier Prenant, fixed by Peter.
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
StartupXLOG and ShutdownXLOG no longer need to be critical sections, because in all contexts where they are invoked, elog(ERROR) would be translated to elog(FATAL) anyway. (One change in bgwriter.c is needed to make this true: set ExitOnAnyError before trying to exit. This is a good fix anyway since the existing code would have gone into an infinite loop on elog(ERROR) during shutdown.) That avoids a misleading report of PANIC during semi-orderly failures. Modify the postmaster to include the startup process in the set of processes that get SIGTERM when a fast shutdown is requested, and also fix it to not try to restart the bgwriter if the bgwriter fails while trying to write the shutdown checkpoint. Net result is that "pg_ctl stop -m fast" does something reasonable for a system in warm standby mode, and so should Unix system shutdown (ie, universal SIGTERM). Per gripe from Stephen Harris and some corner-case testing of my own.
-
由 Teodor Sigaev 提交于
remove page on next level linked from next inner page, ginScanToDelete() wrongly sets parent page. Bug reveals when many item pointers from index was deleted ( several hundred thousands). Bug is discovered by hubert depesz lubaczewski <depesz@gmail.com> Suppose, we need rc2 before release...
-
- 30 11月, 2006 3 次提交
-
-
由 Alvaro Herrera 提交于
-
由 Tom Lane 提交于
standard functions. Per report from Stefan Kaltenbrunner.
-
由 Tom Lane 提交于
-
- 29 11月, 2006 4 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
switches.
-
由 Tom Lane 提交于
Australia decided to institute DST with one month's notice ... way to go, politicians.
-
由 Tom Lane 提交于
result now depends on the lc_messages setting, as noted by Bruce. Also, mark to_number() and the numeric-type variants of to_char() as stable, because their results depend on lc_numeric; this is a longstanding oversight. Also, mark to_date() and to_char(interval) as stable; although these appear not to depend on any GUC variables as of CVS HEAD, that seems a property unlikely to survive future improvements. It seems best to mark all the formatting functions stable and be done with it. catversion not bumped, because this does not seem critical enough to force a post-RC1 initdb, and anyway we cannot do so in the back branches.
-
- 28 11月, 2006 6 次提交
-
-
由 Peter Eisentraut 提交于
not destroy them. Maybe we can adjust pgindent sometime.
-
由 Peter Eisentraut 提交于
of Dennis Björklund.
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
Arguably we should do this on *all* platforms, but for the moment Ill
-
由 Andrew Dunstan 提交于
protect vfprintf from hijacking by Windows gettext just like other members of the *printf family.
-
由 Tom Lane 提交于
inherited, per Taiki Yamaguchi.
-