| Age | Commit message (Collapse) | Author |
|---|
|
>
> http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php
>
< o %Have ALTER TABLE RENAME rename SERIAL sequence names
> o Have ALTER TABLE RENAME rename SERIAL sequence names
>
> http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php
>
> http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php
|
|
< * Add Oracle-style packages (Pavel)
> * Add features of Oracle-style packages (Pavel)
|
|
Original patch from Hiroshi Saito, modified by me.
|
|
|
|
ssh -L 3333:foo.com:5432 joe@foo.com
I think this should be changed to
ssh -L 3333:localhost:5432 joe@foo.com
The reason is that this assumes the postgres server on foo.com allows
connections from foo.com, which is not allowed by the default
listen_addresses setting. Add more detail explaining this.
pointed out by Faheem Mitha
Also change the example port number 3333 to 63333 so no one can complain
that we are stealing a reserved port number.
|
|
These were previously only documented in the context of date/time formats.
|
|
represented as "char ...[4]" not "int32". Since the length word is never
supposed to be accessed via this struct member anyway, this won't break
any existing code that is following the rules. The advantage is that C
compilers will no longer assume that a pointer to struct varlena is
word-aligned, which prevents incorrect optimizations in TOAST-pointer
access and perhaps other places. gcc doesn't seem to do this (at least
not at -O2), but the problem is demonstrable on some other compilers.
I changed struct inet as well, but didn't bother to touch a lot of other
struct definitions in which it wouldn't make any difference because there
were other fields forcing int alignment anyway. Hopefully none of those
struct definitions are used for accessing unaligned Datums.
|
|
|
|
- Change configure.in to use Autoconf 2.61 and update generated files.
- Update build system and documentation to support now directory variables
offered by Autoconf 2.61.
- Replace usages of PGAC_CHECK_ALIGNOF by AC_CHECK_ALIGNOF, now available
in Autoconf 2.61.
- Drop our patched version of AC_C_INLINE, as Autoconf now has the change.
|
|
<
> * -Allow AS in "SELECT col AS label" to be optional in certain cases
>
< * Allow AS in "SELECT col AS label" to be optional (not wanted)
|
|
outside the 32-bit-time_t range. Also, refer to Olson's tz database
as the 'zoneinfo' database, a name that upstream sometimes uses, not
'zic database' which they never use.
|
|
log_checkpoints in 8.3.
|
|
checkpoints.
|
|
(or RETURNING), but only when the output name is not any SQL keyword.
This seems as close as we can get to the standard's syntax without a
great deal of thrashing. Original patch by Hiroshi Saito, amended by me.
|
|
XMLPARSE (DOCUMENT '<?xml
version="1.0"?><book><title>Manual</title><chapter>...</chapter></book>')
Backpatch to 8.3.X.
|
|
major releases.
|
|
doing anything interesting, such as calling RevalidateCachedPlan(). The
necessity of this is demonstrated by an example from Willem Buitendyk:
during a replan, the planner might try to evaluate SPI-using functions,
and so we'd better be in a clean SPI context.
A small downside of this fix is that these two functions will now fail
outright if called when not inside a SPI-using procedure (ie, a
SPI_connect/SPI_finish pair). The documentation never promised or suggested
that that would work, though; and they are normally used in concert with
other functions, mainly SPI_prepare, that always have failed in such a case.
So the odds of breaking something seem pretty low.
In passing, make SPI_is_cursor_plan's error handling convention clearer,
and fix documentation's erroneous claim that SPI_cursor_open would
return NULL on error.
Before 8.3 these functions could not invoke replanning, so there is probably
no need for back-patching.
|
|
authentication.
|
|
|
|
in .bat simply did not work, and it called them in the wrong order,
some several times, and some not at all. So this unrolls all subroutine
calls.
This should fix the issues with clean deleting the wrong files reported
by Dave Page.
While at it, add the "clean dist" option to act like "make distclean",
and no longer remove the flex/bison output files by default. This shuold
fix the problem reported by Pavel Golub in bug #3909.
|
|
Also make links clickable.
|
|
|
|
to wit in the description of that variable rather than some other one.
|
|
|
|
< * Improve deadlock detection when deleting items from shared buffers
> * Improve deadlock detection when a page cleaning lock conflicts
> with a shared buffer that is pinned
|
|
|
|
<!-- If this URL chnages replace it with a URL to www.archive.org. -->
|
|
name of the needed symlink file.
|
|
Update expected release date.
|
|
buildfarm plus a narrative description of the CPU types and operating systems
on which Postgres is likely to work. Now that we've almost completely
decoupled CPU and OS considerations, the former tabular style isn't all that
enlightening anyway. Perhaps more importantly, no one seems particularly
interested in maintaining the table by hand when we have the buildfarm.
|
|
prevent anti-wraparound vacuuming, and to caution against setting unreasonably
small values of freeze_max_age. Also put in a notice that this catalog is
likely to disappear entirely in some future release. Per discussion of
bug #3898 from Steven Flatt.
|
|
spoofing when the socket file has been moved.
|
|
> * Improve deadlock detection when deleting items from shared buffers
>
> http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php
> http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php
|
|
synchronized-scanning behavior, and make pg_dump disable sync scans so that
it will reliably preserve row ordering. Per recent discussions.
|
|
|
|
|
|
< * Add anonymous transactions
> * Add autonomous transactions
|
|
> * Add anonymous transactions
>
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php
>
|
|
< o Allow the PITR process to be debugged and data examined
|
|
from Gevik Babakhani
|
|
|
|
in particular correct the obsolete claim that it can't be changed once
any plans have been cached.
|
|
of escaping bytea return value. Both cases did not handle backslash values properly.
|
|
|
|
Per discussion of bug #3877. Simon Riggs, some fixes by moi.
|
|
zero with a CASE expression. Per gripe from Russell Smith.
|
|
no-longer-maintained PgAccess. Per Erik Rijkers.
|
|
|
|
|
|
Jun Kuwamura
|
